The reason we use farbling instead of a deterministic fingerprint is because it often breaks sites and causes web compatibility issues. Also, the simple fact that a user injects window.ethereum into the DOM via extension produces a highly unique fingerprint on it’s own. I think it’s something like less than 1% of Web users would include this JS.
Might I suggest an alternative based on my experience doing security and privacy in the browser and our wallet at Brave for the past 4 years? I’d suggest instead that we move away from the leaky abstraction of wallet APIs which rely on the site structuring transaction data and instead start encapsulating most of this into the wallet. This can be done by more wallets implementing the standardized interfaces of metamask snaps and then capabilities enabled in kohaku are converted into wallet snaps. Additionally, as more CROPS protocols are built they can be plugged in the same way. Then for the average web developer who wants to rely on the capabilities of wallets without thinking about if they need to use a multicall, what byte ordering they need, or what the right contract address is they can just call to a high level API that encapsulates this for them.
BTW, brave is already working in this direction of adding snaps to our wallet.
Here’s some other lessons you’ll likely find as you attempt something like this more too:
The size of this project is a multi year effort that would take a team of at least 30 engineers with deep knowledge of browsers to ship this. That sounds expensive, How are you going to fund it? Don’t forget that the code is constantly shifting under your feet too whether its built on Gecko, Chromium, Webkit, or even ladybird so you’ll need to rebase quite often too.
Most people run their wallets off mobile devices, are you planning to support both Android and iOS? If you support iOS, you’ll need a specialist team who knows how to integrate the codebase into webkit because iOS still requires the usage of Webkit.
On that note, do you expect the average user will accept the usability constraints of running everything off TOR?
In the case where a user doesn’t have enough hardware to run something like a lightclient is there an acceptable downgraded model of relying on RPCs for it?
When it comes to reliance on API calls, how are you planning to handle fingerprinting based on assets such as coins or NFTs held that are looked up by balances or to acquire the USD value (or another currency because yes, unfortunately most users expect these basic features) as @scburgel showed was possible, how do you plan to farble these?
Should the wallet API leak the wallet address to the site causing a unique fingerprint?
That’s just the start of the questions. There’s likely many more that exist beyond simple web3 related concerns that would run very deep just on the browser side of things which are going to encounter major usability tradeoffs. This then reduces the total number of users who might use it and a lot of costs to change and maintain features like this. In saying all that, I do recognize there’s some useful capabilities in here which I’ll take back and see what we can get added to Brave Wallet. And if you find a way to fund and pull something as ambitious as this off I’m keen to watch and see what we can learn from it to improve Brave too.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Repurposing FOCIL as an L2 forced transaction mechanism | 0 | 0 | 19-06-2026 |
| 2 | A native zkEVM scales bandwidth, not just execution | 0 | 0 | 22-06-2026 |
| 3 | A Criticism of LUCID and Encryption-Scheme-Agnostic Encrypted Mempool Designs | 0 | 0 | 22-06-2026 |
| 4 | Exploring ownership fragmentation as a privacy primitive for the post-Pectra EVM | 0 | 0 | 23-06-2026 |
| 5 | Relationship-Anchored Money: Separating Symbolization from Securitization | 0 | 0 | 22-06-2026 |
| 6 | Validator Redirected Revenue | 0 | 0 | 23-06-2026 |
| 7 | Building index-tracking assets on top of options instead of debt | 0 | 0 | 19-06-2026 |
| 8 | Cooperative Capitalism Is the Last Coherent Economic Path Crypto Has Left | 0 | 0 | 23-06-2026 |
| 9 | Futarchy is insecure without a trusted gatekeeper | 0 | 0 | 21-06-2026 |
| 10 | ETH needs a supply cap at 128 million | 0 | 0 | 21-06-2026 |
