polymutex

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!

My headliner tier list, Hegota edition. Same ordering principle as last time: Do the maximally-cypherpunk things upfront, in order to minimize that the risk of capture in the future prevents them from ever taking place.

Case in point below. I'm not a fan of US culture, and the US doesn't hold cultural supremacy over the world. But the point here is to highlight the reflexive nature of the audience's reaction in a situation of sitting together in a social setting, being exposed to things they did not fully pre-vet being exposed to. It's a situation that commands a quick, socially-expected reaction. It's in this type of setting that you get to see what each person in the video either viscerally feels, either feels a need to emulate in order to socially fit in. Either way, it's corrosive.

Pre-nuclear steel Pre-payouts social Pre-slop web Pre-musk tweets

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/

> more people would be able to contribute to crypto if they didn't have to go 'full crypto'. [...] something like Google's 20% time There's a staggering amount of quality-of-talent that *could* do this but won't, which crypto is losing out on just because of the reputation problem.

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

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 🧐

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.

The dangers of "custodial-first, export-later" wallets: need to check the export function actually exists. Also: assume the service still has your private key after you export it.

I remain convinced that reputation is by far the biggest hurdle against crypto adoption. If we fail, crypto risks being relegated to just being a boring backend corposlop infrastructure tech, with none of the self-sovereignty benefits reaching the masses. This very problem is what I was hoping @ethereumfilm would fix, and a large part as to why I am among the many who funded it. It is ironic that the problem it could fix is also the very problem preventing it from making headway. https://x.com/EthereumFilm/status/2015930673065033761

gm

This is probably the first miniapp I've used that doesn't require a mobile login. Great UX.

Really looking forward to this as the /walletbeat existence proof that RPC-level privacy is not an unreasonable objective for wallets to provide.

I believe the Ethereum Foundation blog subscriber emails database has been leaked. How do I know? I use unique emails for all my subscriptions, and in the last few days I have started receiving phishing emails on the address I used exclusively on the EF blog. Can anyone confirm?

How many people does it take to safely verify and sign a Uniswap transaction on a hardware wallet? Took the three of us (@0xMattmatt, @PatrickAlphaC and I) over an hour, and in the end the transaction reverted 🫠 https://x.com/0xMattmatt/status/2013695256584421744

After FC's pivot to wallet development, Bluesky showcases their finance community. https://bsky.social/about/blog/01-19-2026-the-smart-money-is-on-bluesky

Zeus Wallet added to Walletbeat's software wallet ratings! Zeus describes itself as a truly seedless and decentralized self-custodial Ethereum wallet. See Zeus's full ratings breakdown on Walletbeat: https://beta.walletbeat.eth.limo/zeus/ Special thanks to greekfetacheese on GitHub for the contribution.

🫡

What I would build with this kind of money/computing power: A pure-JavaScript (or Rust-to-WASM) implementation of TLS. Why? Because it could be used as a Tor-like Oblivious HTTP polyfill that browser wallets could use to improve their network-level privacy. JavaScript → TCP proxy 1 → TCP proxy 2 → HTTPS endpoint