wallets
/wallets149
Cool redesign. About time. Much needed. 🦊
222464
MetaMask 🦊
@metamask·06:09 28/02/2025
You want an overhaul? It’s coming.
This is a preview of a new MetaMask home screen.
This is a preview of a new MetaMask home screen.
5694
shazow
@shazow.eth·19:00 22/02/2025
ONE MORE WALLET BRO, JUST ONE MORE WALLET WILL FIX IT, THIS IS DIFFERENT, JUST ONE MORE
3854
Darryl Yeo 🛠️
@darrylyeo·21:05 21/12/2024
This week on /blockhead:
• overhauled Wallets menu layout and transitions
• new flow: “Pin” a connected wallet to persist its connection between page sessions (before, you had to check “Autoconnect” prior to connecting from a new session which was confusing!)
• overhauled state management logic for wallet discovery and account connections (for both Svelte 4 and Svelte 5 in parallel)
• improved accuracy by modeling all possible connection methods for selecting a “known wallet”: EIP-6963 reverse-DNS names, @walletconnect UUIDs, resolver functions and “identity flag” matching functions for globally injected EIP-1193 provider objects (including but not limited to `window.ethereum`, `window.web3.currentProvider`, and the infamous `isMetaMask` flag which is set to `true` by several @metamask browser extension wannabes 🦊🥸)
• overhauled Wallets menu layout and transitions
• new flow: “Pin” a connected wallet to persist its connection between page sessions (before, you had to check “Autoconnect” prior to connecting from a new session which was confusing!)
• overhauled state management logic for wallet discovery and account connections (for both Svelte 4 and Svelte 5 in parallel)
• improved accuracy by modeling all possible connection methods for selecting a “known wallet”: EIP-6963 reverse-DNS names, @walletconnect UUIDs, resolver functions and “identity flag” matching functions for globally injected EIP-1193 provider objects (including but not limited to `window.ethereum`, `window.web3.currentProvider`, and the infamous `isMetaMask` flag which is set to `true` by several @metamask browser extension wannabes 🦊🥸)
2
Varun Srinivasan
@v·22:32 10/02/2025
If you're launching a wallet, should it be an EOA or Smart Wallet (4337)?
EOAs become upgradeable with 7702 later this year, so you get the benefits of 4337 wallets and can upgrade to better standards over time.
So it comes down to: upgradeable smart wallets (EOA + 7702 + 4337*) or pure smart wallets (4337 only) ?
EOAs become upgradeable with 7702 later this year, so you get the benefits of 4337 wallets and can upgrade to better standards over time.
So it comes down to: upgradeable smart wallets (EOA + 7702 + 4337*) or pure smart wallets (4337 only) ?
It’s gonna be a wallet, isn’t it?
3
Dan Romero
@dwr.eth·23:34 31/01/2025
Excited for next week.
3854
Darryl Yeo 🛠️
@darrylyeo·21:05 21/12/2024
This week on /blockhead:
• overhauled Wallets menu layout and transitions
• new flow: “Pin” a connected wallet to persist its connection between page sessions (before, you had to check “Autoconnect” prior to connecting from a new session which was confusing!)
• overhauled state management logic for wallet discovery and account connections (for both Svelte 4 and Svelte 5 in parallel)
• improved accuracy by modeling all possible connection methods for selecting a “known wallet”: EIP-6963 reverse-DNS names, @walletconnect UUIDs, resolver functions and “identity flag” matching functions for globally injected EIP-1193 provider objects (including but not limited to `window.ethereum`, `window.web3.currentProvider`, and the infamous `isMetaMask` flag which is set to `true` by several @metamask browser extension wannabes 🦊🥸)
• overhauled Wallets menu layout and transitions
• new flow: “Pin” a connected wallet to persist its connection between page sessions (before, you had to check “Autoconnect” prior to connecting from a new session which was confusing!)
• overhauled state management logic for wallet discovery and account connections (for both Svelte 4 and Svelte 5 in parallel)
• improved accuracy by modeling all possible connection methods for selecting a “known wallet”: EIP-6963 reverse-DNS names, @walletconnect UUIDs, resolver functions and “identity flag” matching functions for globally injected EIP-1193 provider objects (including but not limited to `window.ethereum`, `window.web3.currentProvider`, and the infamous `isMetaMask` flag which is set to `true` by several @metamask browser extension wannabes 🦊🥸)
FINALLY
222464
MetaMask 🦊
@metamask·01:03 20/11/2024
raise your hand if you're happy that we just enabled network auto-switching so YOU DONT HAVE TO SEE THIS PROMPT AGAIN
In the market for a new hardware wallet. What's good?
I guess I was brand loyal to Ledger, but recently had a screen die on a Ledger Nano S, and now a battery on a Nano X.
I guess I was brand loyal to Ledger, but recently had a screen die on a Ledger Nano S, and now a battery on a Nano X.
I believe one of the hurdles to mass adoption is that wallets are too crypto feature-rich and have too shallow integration with TradFi. We can't expect newcomers to go from 0 to 100 overnight, we need to help them go bankless in a progressive way
How two different wallets display the same transaction. I ordered merch on coinbase from the base summer shop and paid with crypto.
Coinbase wallet on the left
Rainbow on the right
Coinbase wallet on the left
Rainbow on the right
This is only getting worse with smart wallets, disabled key exports and no ability to import your own.
Resist the walle(d|t) gardens!
Resist the walle(d|t) gardens!
115
JD
@darkstar·17:49 26/08/2024
one of crypto's great unlocks is sign in interoperability-- one ID for all applications.
however, many services are actually creating their own walled gardens aka "wallet gardens". it *feels* easy, but users are unaware they're locked in.
seeing the forest for the trees.
however, many services are actually creating their own walled gardens aka "wallet gardens". it *feels* easy, but users are unaware they're locked in.
seeing the forest for the trees.
Why do hardware wallets (Trezor, Ledger) not let you generate an address unless your sequentially previous address has received funds?
What's your go-to hardware wallet?
I have two Ledgers but recently got a Trezor. I'm a bigger fan of the Trezor UX / onboarding flow so far than Ledger.
I have two Ledgers but recently got a Trezor. I'm a bigger fan of the Trezor UX / onboarding flow so far than Ledger.
3854
Darryl Yeo 🛠️
@darrylyeo·18:41 09/02/2024
"EIP-6963 namespace collisions aren't real, EIP-6963 namespace collisions can't hurt you"
EIP-6963 namespace collisions:
EIP-6963 namespace collisions:
