←
polymutex 🌸3,621 posts
polymutex 🌸 avatar

polymutex 🌸

@polymutex

Working on @Walletbeat 🌸 Who watches the wallets?

◷ Joined January 2022▧ 245 Photos and videos
polymutex 🌸 avatar
polymutex 🌸@polymutex·10h

Charts are for the casino

@ambire 1. Enable only Ethereum on install. Use your own RPC if you wish 2. Opt out of all third party requests on install. UX becomes worse, but big improvements are coming 3. Click on "Create new account" and you're done. EIP-7702 accounts without the technical hurdle, so you get the best UX on Ethereum 4. Import your Safe account. Creation of a Safe vault is coming next week 5. No casino, no bs and no beautiful value charts - charts are for the casino

Post attachmentPost attachmentPost attachmentPost attachment
thedao.fund avatar
⟳ polymutex 🌸 retweeted
thedao.fund@thedaofund·22h

Voting is LIVE in the ETHSecurity Initiatives Round! If your favorite initiative hasn't qualified yet, pledge or donate by November 25 to get them on the ballot. Here's how it all works ↓ paragraph.com/@thedao.fund/v…

Walletbeat 🌸 avatar
⟳ polymutex 🌸 retweeted
Walletbeat 🌸@walletbeat·19h

Walletbeat is participating in @thedaofund’s new round, focused on Ethereum security. Get to know our initiative: Clear signing ratings, fixes and ecosystem adoption for hardware and software wallets. 🧵👇

Post attachment
kassandra.gwei avatar
⟳ polymutex 🌸 retweeted
kassandra.gwei@kassandraETH·Nov 17

the big AI labs are toying with the world and essentially playing god by deciding who gets access to the best models with which "guardrails" on/off we've ALREADY entered an era of techno-feudalism... we need visions of the future that avoid "corpo hell" we need open models!

Open models are essential to protecting our privacy and sovereignty online. Otherwise AI will remain in corpo hell forever. They will control it and by extension us. The data that make up a model are information. Publication of that information is protected speech. p2p.coincenter.org/p/publish…

polymutex 🌸 avatar
polymutex 🌸@polymutex·Nov 17

Some said L2s were sticky because liquidity, while wallets should be non-sticky as account import is trivial. In reality it's the opposite: L2s get flighty mercenary capital, while wallets are very sticky and feel little competitive pressure. Gotta turn up the heat 🌸

It's honestly insane that I was able to build a fresh wallet @WalletChan_ from scratch that does such batching but even today existing wallets & apps don't do so 7702beat.eth.sh/#wall-of-sha…

Post attachment
Walletbeat 🌸 avatar
⟳ polymutex 🌸 retweeted
Walletbeat 🌸@walletbeat·Nov 16

Walletbeat monthly update is here! 🌸 Check out what happened across Walletbeat and the wallet ecosystem through October 👇

Post attachment
polymutex 🌸 avatar
polymutex 🌸@polymutex·Nov 17

Not a moment too soon

Danny @Dantoshi Nov 16 Article Anonymous Pickup is live: Buy a Trezor in the EU without telling us who you are A long time in the making. Breach after breach across our industry has shown why it matters. From today, in the EU, you can buy a Trezor with only a nickname and an email address. No name, no home

polymutex 🌸 avatar
polymutex 🌸@polymutex·Nov 16

We'll see how long I get to keep this up!

from here it probably makes more sense for most of us who want to build hardline decentralized tech to work outside crypto and be like gentlemen cypherpunk weekend warriors in the past this would've been way too slow, now with AI you can build very meaningful things as long as you have a real job to keep buying the other kind of tokens

The Anon Project avatar
⟳ polymutex 🌸 retweeted
The Anon Project@anondotinc·Nov 13

Great point, so we built it. Live now in Anon extension 0.13.0: A wallet shouldn't need to ask a server what a request means or whether a site is a known phishing site. Anon looks both up on your device. How it works and where it stops:

We keep forgetting the privacy lessons of web2. Your browser checks if the domain you're on is on a known-scam list without revealing it to anyone else. Your wallet should check the clear signing manifest of the contract you're using without revealing it to anyone else.

Post attachment
superKalo.eth avatar
⟳ polymutex 🌸 retweeted
superKalo.eth@0xSuperKalo·Nov 12

Just confirmed that @Ledger is REMOVING the EIP-7702 implementation from its Ethereum app. Everyone deep in Ethereum knows how bad this is 🤦‍♂️ My PR adding 5 EF-recognized delegators to the app's whitelist waited 9 months for a reply, then got closed. For Ledger users on @ambire, this means no batching, no gas sponsorship and no paying gas in stablecoins - things the same people have had with a hot wallet for 18 months now, since Pectra. And when the hardware wallet with the biggest market share drops 7702, the signal is "7702 is unsafe". Its reputation already suffers from misunderstanding - the "7702 drainers" all started with leaked private keys, not with 7702 itself. @ethereumfndn, this is the last thing 7702 needs right now. Can we channel some energy into getting @Ledger to reconsider? 💪 github.com/LedgerHQ/app-ethe…

polymutex 🌸 avatar
polymutex 🌸@polymutex·Nov 11

It's not rocket science, no need for fancy Private Information Retrieval or any new cryptography. Just need the will, the privacy mindset, and a set of values that places user security (helping users not fall into scams) above extracting value out of such features.

Post attachment
polymutex 🌸 avatar
polymutex 🌸@polymutex·Nov 11

We keep forgetting the privacy lessons of web2. Your browser checks if the domain you're on is on a known-scam list without revealing it to anyone else. Your wallet should check the clear signing manifest of the contract you're using without revealing it to anyone else.

Post attachment

This is part of how Clear Signing works. ERC-7730 descriptors, which turn raw calldata into readable fields, are too large to fit on a Ledger signer, and most integrators don’t want to bundle the full metadata set. So the default context module in our signing kit resolves them from Ledger’s servers at signing time. That requires sending the transaction details needed to find the right descriptor. Ledger doesn’t store that data. It runs in the developer library that wallet apps use to talk to a Ledger signer, not in device firmware. Integrators control it and can supply their own context module to resolve metadata themselves: developers.ledger.com/docs/d… How the context module works: developers.ledger.com/docs/c… The descriptor registry is public: github.com/ethereum/clear-si…

superKalo.eth avatar
⟳ polymutex 🌸 retweeted
superKalo.eth@0xSuperKalo·Nov 11

This is simply not true: blind-signing.api.ledger.com has nothing to do with resolving ERC-7730 descriptors. 1/ Descriptors are fetched in the BuildContexts step, BEFORE the user signs. The report is a separate DetectBlindSigning step that runs only AFTER the device returns a signature. It even runs when the user rejects on the device. At that point there's nothing left to resolve: github.com/LedgerHQ/device-s… 2/ It's a fire-and-forget POST to /ingest/v1/blind-signing-events with responseType: "void". The response is thrown away, so it can't be feeding any descriptor lookup: github.com/LedgerHQ/device-s… 3/ Payload: chainId, contract/recipient address, device model, firmware version, Ethereum app version, isBlindSign + reason. Firmware and app versions don't help anyone find a descriptor: github.com/LedgerHQ/device-s… 4/ It fires even when NO descriptor was found. That's literally what isBlindSign: true means. And it fires without an originToken, which your own docs say is required for Clear Signing. 5/ Your own PRs call it a "blind signing reporter" (#1389) and "Multichain blind-sign tracking" (#1966), not descriptor resolution: github.com/LedgerHQ/device-s… github.com/LedgerHQ/device-s… Since context-module 2.7.0 there's even a second (v2) report per signature, and the builder has no setter to swap it out. "Integrators control it" only helps if they know it exists. It's on by default, and neither of the two docs pages you linked mentions it. Privacy should be opt-in, not opt-out!