Brave is, at the end of the day, in the same boat as Google: they make money on ads. They also happen to be an ad blocker, so, of course, they won't implement WEI... but, as they also themselves present ads and need to make sure people don't block their ads while claiming to have seen them--which is trivial to do currently, btw--their product managers and even Brendan Eich himself had often laid out a roadmap that involves trusted computing technology with the same ad fraud justification Google is using, whether for their SDK or the browser itself.

https://www.reddit.com/r/BATProject/comments/bw6sek/

https://www.reddit.com/r/BATProject/comments/b7rwbx/

> 1/ native C++/Rust code, no JS tags on page that have zero integrity. That means ability to use SGX/TrustZone to check integrity and develop private user score from all sensor inputs in the enclave; ...

> We already have to deal w/ fraud. That is inherent in any system with users and revenue shares or grants. We do it better via C++ and (under way) SGX or TrustZone integrity checking + OS sensor APIs, vs today’s antifraud scripts that are routinely fooled.

> What Brave offers that's far better than today's joke of an antifraud system for ads is as follows: 1/ integrity-checked open source native code, which cannot be fooled by other JS on page; ... (1) requires SGX or ARM equivalent, widespread on mobile.

https://www.reddit.com/r/BATProject/comments/9yys6b/

https://www.reddit.com/r/BATProject/comments/97trex/comment/...

> Part of the roadmap (details in update) is a BAT SDK. Obviously it would be open source, but more: we would require Secure Remote Attestation (Intel SGX broken but ARM TrustZone as used by Trustonic may be ok) to prove integrity of the SDK code in app.