walletbeat

walletbeat

The L2Beat of Ethereum wallets. Who watches the wallets?

polymutex pfp

🚢 Walletbeat worklog 2025-10-31 1. Add *.svelte linting, fix some of what it found. Messed up import groupings though, I'll fix that! With apologies to @darrylyeo 🙇 2. Add test to protect against hallucinated URLs in wallet references. Remove 2 such URLs that slipped in before this test. Issue #307. 3. [...]

1 reply

0 recast

1 reaction

polymutex pfp

🚢 Walletbeat worklog 2025-10-30 1. Really happy to see @darrylyeo's PR merged which ports the site to Astro/Svelte and does a visual refresh. This was a months-long effort. Go check it out! 2. Some follow-up lint fixes post-merge. 3. Review @0xmattmatt's first PR #308. 4-5. [next cast]

1 reply

1 recast

3 reactions

polymutex pfp

... And merged! @darrylyeo You might want to do an announcement post with screenshots so I don't steal your thunder here... but I will say, Walletbeat looks different today 👀

0 reply

1 recast

5 reactions

Darryl Yeo 🛠️ pfp

Darryl Yeo 🛠️

A passing Astro / Svelte build of /walletbeat has been achieved internally ✅

4 replies

1 recast

7 reactions

polymutex pfp

🚢 Walletbeat worklog 2025-10-29 1. Meet with @0xmattmatt to go over Walletbeat codebase in general, and potential first issues to tackle. 2. Merge PR #301 adding Safe Wallet (as its own entry) and Safe account support (for non-Safe wallets) as new wallet data. 3-5. [next cast]

1 reply

0 recast

2 reactions

polymutex pfp

🚢 Walletbeat worklog 2025-10-28 1. Welcome @0xmattmatt who will be helping out on hardware-wallet-related tasks! :) 2. Review PR #300 adding imToken Wallet to the site. 3. Review PR #301 adding Safe Wallet (as its own entry) and Safe account support (for non-Safe wallets) as new wallet data. 4. [next cast]

1 reply

1 recast

4 reactions

polymutex pfp

900000 wallets and this is current state

0 reply

0 recast

4 reactions

polymutex pfp

🚢 Walletbeat worklog 2025-10-25 1. Progress on Account Recovery attribute. Rating logic implemented, rated Ambire & MM 🦊. Some UI work remains, which is bespoke as it must display the outcome of possibly-many scenarios ("What if X gets compromised?"/"What if Y gets lost?"/etc.). (cc @darrylyeo) 2. [...]

1 reply

0 recast

4 reactions

polymutex pfp

🚢 Walletbeat worklog 2025-10-24 1. Some progress on Account Recovery attribute: Guardian-based recovery will be evaluated based on the set of outcomes from hypothetical scenarios. Examples: [next cast]

1 reply

0 recast

4 reactions

polymutex pfp

Some further thoughts on 𝗰𝗹𝗲𝗮𝗿 𝘀𝗶𝗴𝗻𝗶𝗻𝗴. 🔏 /walletbeat's goal isn't to prescribe how hardware wallet manufacturers run their business. But it 𝘪𝘴 to protect users' safety, and to maintain wallet ecosystem health through open competition and interoperability.

1 reply

1 recast

7 reactions

polymutex pfp

Wallets charging for clear signing feels like browsers charging for CSS support https://x.com/pcaversaccio/status/1981623813180637673

1 reply

2 recasts

7 reactions

Francesco | andreolf.ethᵍᵐ pfp

Francesco | andreolf.ethᵍᵐ

I'm getting a 404 on the wallet beat pages. you getting the same?

1 reply

0 recast

1 reaction

polymutex pfp

🚢 Walletbeat worklog 2025-10-23 1. Merge Mt Pelerin (Bridge Wallet) PR, add some fixes to account for feature type changes since. 2. Merge IPFS link test PR. 3. Fix build process to rebuild until SRI hashes are stable. 4. Merge hardware wallet refactor PR. 5-8 [...]

1 reply

0 recast

1 reaction

polymutex pfp

🚢 Walletbeat worklog 2025-10-22 Large refactor of hardware wallet support attributes for software wallets: - Split "hardware support" attribute in 2: * "Hw wallet support" in "Security" group * "Support hw wallets from a plurality of hw wallet manufacturers" in "Ecosystem" group (for interoperability). [...]

1 reply

0 recast

3 reactions

polymutex pfp

🚢 Walletbeat worklog 2025-10-21 1. Discuss splitting the hardware wallet support attribute into 2: Support vs interoperability. The former covers the security benefits of HW wallet support, the latter ensures no HW manufacturer lock-in. 2. Start working on the implementation of that. Issue #291. 3. [next cast]

1 reply

1 recast

7 reactions