is anyone working on a "data wallet"? the space needs one badly: - encrypted storage of user data - give custom permissions to each dapp, limited by namespace - secure enclave for performing hashing, proofs, etc - encrypted cloud backups, syncing to different devices

0 reply

0 recast

2 reactions

Spent the day refactoring Rabby's network traffic data to use the new wallet network traffic analysis tool. Tedious work, but important. Since my last post on the subject, the structure of their RPCs has changed, but let's just say the data being sent to DeBank has not, and now it also sends all data to Hyperliquid.

3 replies

5 recasts

18 reactions

I would not have been able to get Walletbeat off the ground without Farcaster. For that, I will be eternally grateful. https://farcaster.xyz/darrylyeo/0x4bdf6054

0 reply

3 recasts

17 reactions

One of the reasons why the wallet data collection CLI tool (helping to classify wallets' HTTP requests and their privacy implications) is a CLI.

0 reply

1 recast

8 reactions

Last call for discussion on the wallet security benchmark: https://github.com/walletbeat/walletbeat/discussions/407 Planning to start incorporating these into Walletbeat's methodology at the end of this week. Walletbeat's security methodology will never be set in stone, but does get harder to change over time, so speak up now if you have opinions!

0 reply

3 recasts

9 reactions

Had fun in shipping this: Wallet Testing Playground now live 🟢 Your Walletbeat tool to test wallet signatures, transactions, EIP support ALL IN ONE PLACE ⚒️ Run your wallet through the playground!

0 reply

1 recast

10 reactions

What's this? Something's brewing in this flask... @0xmattmatt has been working on this feature for a long time, and it's not complete yet, but you can already pace your wallet through a lot of automated tests :) Test your wallet at: https://beta.walletbeat.eth.limo/test/

0 reply

1 recast

6 reactions

For wallets, transaction simulation is essential to prevent users from shooting themselves in the foot. But when outcomes depend on execution state, users can still get scammed. So how do wallets protect users from this?

0 reply

0 recast

3 reactions

Hey @polymutex.eth @darrylyeo @walletbeat.base.eth you should measure ERC-5630 support in wallets 😁 In other news I launched this site this morning: ddrp.io

1 reply

0 recast

4 reactions

Which wallet will be the first to achieve a perfect 🍀🍀🍀🍀🍀 rating on /walletbeat? It’s still anyone’s game! https://x.com/ambire/status/2018683791729209676

0 reply

3 recasts

7 reactions

Happy to see @safe thinking about this. Multisigs can't have censorship resistance without a censorship-resistant way to distribute transaction proposals. Reminds me of how wallets don't really provide L2 censorship resistance if they don't support force-inclusion transactions. https://x.com/safe/status/2018262373673705919

1 reply

0 recast

4 reactions

Proposing two significant changes to /walletbeat's methodology and display today: - Introduce "verifiability" as a separate dimension from the rating itself; issue #503 - Move non-stage-zero wallets to a separate "Others" tab similar to L2BEAT; issue #504 Some thoughts below 🧐

1 reply

2 recasts

11 reactions

New "good first issue" just dropped For first time contributors looking to contribute, this issue might be for you PRs welcome!

1 reply

1 recast

6 reactions

Wrapping up the January Update for Walletbeat. Needless to say, January was a good month :) Let's continue this energy throughout 2026 🫡

1 reply

1 recast

5 reactions

Crypto will either: 1. Fail because it'll die out from attrition 2. Succeed, but only at building a dystopian panopticon-casino 3. Succeed by actually delivering on its values #3 is the best outcome. #1 would be OK too. What matters is avoiding #2. Hence staying, doing the work to make sure that #2 doesn't happen.

4 replies

2 recasts

21 reactions