walletbeat
The L2Beat of Ethereum wallets. Who watches the wallets?
Darryl Yeo 🛠️ pfp

@darrylyeo

Introducing the newly redesigned Walletbeat! • 24+ independent reviews of software + hardware wallet brands in a compact table format for quick comparison • color-coded pie charts, tooltips, hierarchical columns and rows that collapse and expand to reveal details • filters and sorts for variants, hardware models, attribute ratings, categories, stages and more • dynamically generated wallet report cards with detailed explanations of rating criteria, sources and research methodologies
1 reply
7 recasts
34 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-17 1. GitHub account restored (though my PRs are still invisible on GitHub). Got the word back out on the security benchmark proposal. 2. Review PR #408 adding PillarX wallet entry to the site (with empty data though). 3-6. [...]
1 reply
0 recast
2 reactions

polymutex pfp

@polymutex.eth

Today in GitHub shenanigans: The mysterious case of the disappearing PRs.
1 reply
0 recast
4 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-16 1. Wrote and polished wallet security benchmark proposal for 1TS. Link to document (but probably will not work, see next cast): https://github.com/walletbeat/walletbeat/discussions/407 2. [...]
2 replies
0 recast
3 reactions

polymutex pfp

@polymutex.eth

This has happened again today. My GitHub profile is gone once more. Doesn't seem like GitHub can get its act together.
5 replies
4 recasts
6 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-15 1. Assist with setting up a Walletbeat development environment on Windows. 2. Merge Account Recovery & Account Unruggability attributes, PR #288. 3. Upload Trustless conference slides on Walletbeat to the repository; video: https://www.youtube.com/watch?v=sU3Q5aLwHSY 4. [next cast]
1 reply
0 recast
3 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-12 1. Merged wallet data contribution guide. 2. Started working on methodology contribution guide, explaining the wallet feature data and attribute structure. [...] 3. [...]
1 reply
0 recast
3 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-11 1. PRs #399, #400: Retest & update MetaMask data. The 🦊 wallet now appears to do non-user-data carrying RPCs (`eth_blockNumber` and `net_version`) prior to letting the user change endpoints. Credits hanniabu.eth for making me realize and re-test this. 2-3. [...]
1 reply
0 recast
3 reactions

polymutex pfp

@polymutex.eth

Walletbeat yet again safe from the latest web2 modern webdev's Stack Failure du Jour™, previous episodes being Cloudflare outages. Why safe? - Not using React (thanks @darrylyeo) - Fully static site, so no server components.
4 replies
3 recasts
16 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-10 1. Write 📖 illustrated contributor guide for editing wallet data. Walks through adding a wallet, populating its data, shows ratings change live! https://github.com/walletbeat/walletbeat/blob/contribution-guide-wallet-data/resources/docs/contribute/wallet-data.md 2-3. [next cast]
2 replies
1 recast
8 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-09 1. Push on PR #288, implementing both the 🛟 Account Recovery and 🪚 Account Unruggability attributes. Subsumes previous "Key Handling" attribute. Pending review. 2. Schedule first Walletbeat contributor sync meeting next week.
0 reply
0 recast
2 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-12-08 Back from vacation. 1. Establish week priorities: https://farcaster.xyz/polymutex.eth/0x3c2f636e 2. File issue for Duress Resistance attribute (#389) to help protect users against wrench attacks. 3. Review @0xmattmatt PRs #378, #379, #381, #383, #385, #387, #388. 4-5. [...]
1 reply
0 recast
4 reactions

polymutex pfp

@polymutex.eth

Tracking "Duress resistance" in Walletbeat issue #389: https://github.com/walletbeat/walletbeat/issues/389
0 reply
1 recast
6 reactions

polymutex pfp

@polymutex.eth

Back to work on Walletbeat starting today. A note on my immediate priorities. Attending @devcon taught me that the highest-leverage move to do for the project at this point is to enable others to contribute more easily, rather than directly contributing myself. For this reason, this week I will be mostly working on writing contribution guides, explicitly writing down code conventions, and lowering the contribution effort bar for initial wallet data entry. This comes at the expense of finishing up wallet methodology which had been my top priority and remains imperative for launch, and is the next milestone for the Ethereum Foundation grant Walletbeat has received. So the grant milesone will have to wait in line. That said, I already have the Account Recovery attribute almost finished and it's been in the works for a while, so will probably finish that first thing. That also increases the set of data Walletbeat collects about wallets, so important to get done before asking for wallets to contribute data.
1 reply
2 recasts
10 reactions

polymutex pfp

@polymutex.eth

🚢 Walletbeat worklog 2025-11-28 Nothing much Walletbeat-related; preparing to leave for vacation today. Expect reduced throughput until 2025-12-08. That said I did work for Ethereum today: upgraded my node for Fusaka. Also wrote PR #376 to document all Walletbeat treasury operations publicly for transparency.
1 reply
0 recast
5 reactions