ethui started because MetaMask broke our local workflow. Nonces desynced. Miguel dug into MetaMask, but there was no fix. Tried a browser extension. Then Gabriel said, "Why not a desktop app?" Tauri. Rust. That was it. The full story:

🔗 Hardhat + ethui: full local workflow 1. hardhat compile, /artifacts ready 2. hardhat node, ethui detects it 3. Deploy, explorer loads No setup. No imports. ethui.dev/blog/ethui-1.27-hardhat-support

Testing whale behavior requires a whale's private key. Not on anvil. ethui's impersonator wallet lets you become any address: DAO multisig, treasury, anything. No key needed. ethui.dev/docs/wallets/impersonator

ethui wasn't always called ethui. The project started as Iron. Then a cease-and-desist landed. The rebrand was quick. The name fits better anyway — "eth" plus "ui." It says exactly what it is. Full story: content.subvisual.com/case-study/e...

🔐 Authenticated RPC URLs for ethui stacks Your stack. Your team. Controlled access. Works with any RPC tool: wagmi, viem, hardhat, foundry. stacks.ethui.dev

🔄 Honest question for Ethereum devs: when your local node restarts mid-session, what costs you the most time? a) Re-funding test accounts b) Nonce desync with your wallet c) Lost contract addresses and ABIs d) Replaying transactions to get back to the right state Reply 👇

Fresh anvil session. Accounts already funded. ethui's default wallet shares anvil's mnemonic. Same accounts, pre-funded every time. No faucet step. ethui.dev/docs/wallets/plaintext

🎭 Before you submit, see exactly what the transaction will do. Decoded logs. State changes. Gas. Built as a PoC at ETH Lisbon. Running locally inside your wallet. ethui.dev/docs/features/simulations

Multiple wallet types. One window. Mnemonic, private key, plaintext, impersonator, keystore, Ledger, all side by side. No browser profiles. No juggling. ethui.dev/docs/wallets

⚡ Extension-first onboarding in v1.27 Old: download app, install extension. New: install extension, download app. Fewer steps to your first transaction. ethui.dev

Restart anvil. Your transaction history is gone. Most wallets cache tx data locally. Chain resets, orphaned history. ethui re-syncs from chain state after every restart. Always accurate. ethui.dev/docs/features/anvil

1/ Your wallet doesn't know you're a developer. That gap is exactly what @ethui.bsky.social was built to close. ↓

🐛 Hardhat artifacts don't auto-connect to your wallet. Most wallets have no idea what you deployed after compile. ethui scans /artifacts, matches bytecode, contract explorer ready. No imports. No manual setup. ethui.dev/blog/ethui-1.27-hardhat-support

ethui was designed and built by @subvisual.bsky.social Full story, problem, architecture, what shipping a desktop Ethereum dev tool looks like, is live. content.subvisual.com/case-study/e...

🔧 The missing piece in your Web3 dev stack forge handles contracts. anvil runs the chain. ethui connects them to your browser: ✅ Reads ABIs automatically ✅ Bridges browser to anvil ✅ Manages test wallets The glue layer is handled.

🌐 Multi-chain development, in practice Testing cross-chain behavior? → Chrome connected to your mainnet fork → Firefox connected to your local L2 anvil instance → Both browsers are active simultaneously → Different websites on different chains One wallet manager. No profile switching.

⚡ Create a stack. Add it to your wallet. Start building. 1. Name your stack 2. Optionally fork a live network 3. Create 4. Add directly to your ethui wallet 5. Start building No manual RPC config. No copy-pasting endpoints.

💬 Honest question for Ethereum devs: What's the biggest time sink in your local development workflow? a) Wallet friction (confirmations, nonces, restarts) b) Contract setup and ABI management c) Test data and wallet funding d) Switching chains or environments Reply 👇

🔍 How ethui identifies contracts: bytecode matching After deployment, ethui compares on-chain bytecode against ABIs in your /out directory. Match found → contract explorer appears, pre-labeled with your contract names. No address lookup. No manual setup.

🔗 forge + anvil + ethui: how they fit together 1. forge compiles → /out artifacts 2. ethui watches /out → ABIs in real-time 3. anvil runs → ethui detects via anvil_nodeInfo 4. bytecode matched → contract explorer ready One workflow. Zero glue code.

🛠️ Override code at any address on anvil Not just ETH balances. Code too. Replace the bytecode at any deployed address — something not possible on production chains. ethui gives you the full anvil development environment.

🏗️ ethui stacks for staging environments A shared, persistent chain for your team: ✅ Fork any live network ✅ Private API key for access control ✅ Persistent between sessions ✅ Full anvil speed and cheatcodes Not just local dev. Real team staging.

🔐 ethui for smart contract auditors Need to test from a specific address without a private key? Impersonator wallet → become any address on anvil. Contract explorer → interact with deployed contracts directly. No external tools needed.

💬 Ethereum devs: Foundry or Hardhat? ethui natively supports Foundry — auto-detects forge projects, reads ABIs, and syncs the contract explorer in real-time. Which do you primarily build with? a) Foundry b) Hardhat c) Both, depending on the project Reply 👇

⚡ Fast mode: skip dialogs AND private key decryption Fast mode doesn't just skip confirmation popups. It also skips private key decryption, submitting unsigned transactions directly to anvil. Only available on anvil-based chains. Toggle from the sidebar.

🔄 Real-time ABI sync with forge build --watch ethui watches your /out directory in real-time. Run forge build --watch → the contract explorer updates as your contracts change. Zero manual steps. Always in sync.

🔍 "Think Etherscan, but for your local development setup." ethui matches on-chain bytecode against ABIs in your forge /out directory, then generates a UI to interact with them. No address lookup needed. No manual setup. ethui.dev/docs/feature...

📊 April at ethui — a recap This month: → ethui vs MetaMask: different jobs → Extension + desktop architecture → Anvil-aware syncing engine → Stacks: private API keys + subgraph support in dev What would you like to see in May? ethui.dev stacks.ethui.dev

🔢 Nonce caching: the silent killer of local dev Most wallets cache transaction nonces locally. anvil reverts → your cache is stale → transactions fail mysteriously. ethui recalculates nonces from chain state on every transaction. Always accurate. ethui.dev/docs/feature...

🛠️ Next for ethui stacks: subgraph support A subgraph needs PostgreSQL, IPFS, and an indexer node. We're working to manage all of it inside a stack automatically. The tricky part: handling anvil reverts correctly across all components. github.com/ethui/stacks stacks.ethui.dev

💬 Question for ethui stacks users: What's your primary use case? a) Internal QA testing b) User testing (fresh wallet problem) c) Protocol integration (mainnet fork) d) Something else We want to understand how teams use it. Reply below 👇

🔧 Hot take: using MetaMask for development is the wrong tool MetaMask is excellent for consumers. It's designed for production chains: state never reverts, nonces always increment, maximum safety guardrails. None of that applies during development. Developer tooling should fit developer workflows.

🔄 Anvil-aware sync engine ethui detects anvil via anvil_nodeInfo, then switches to a dedicated sync process: ✅ Tracks chain head continuously ✅ Handles reverts + full restarts ✅ Re-syncs tx history and contracts in real-time ✅ Nonces recalculated from chain state

🎬 ethui stacks in 30 seconds Private, persistent development chains for staging, user interviews, and more. Same speed as Hardhat/Anvil. Fork live networks. Free, open source, self-hostable. Create a stack, add it to your wallet, start building. stacks.ethui.dev

💬 Quick question for Ethereum devs: When testing locally with anvil, what breaks your flow most? a) Nonce issues after restarts b) Setting up / switching test wallets c) Distributing gas to test accounts d) Slow deploy → test cycles Asking because we build around these problems. Reply 👇

🏗️ ethui architecture: two pieces, one flow 1️⃣ Desktop app — all interactions happen here 2️⃣ Browser extension (Chrome/Firefox) — passive, just connects browser to the app Logic stays in the desktop. The extension is a bridge. This is what enables multi-browser support.

🖥️ ethui: macOS and Linux support 4 steps to get started: 1. Download binary 2. Run onboarding 3. Install extension (Chrome or Firefox) 4. Connect to a web3 app The extension and the desktop app communicate. All interactions happen in the desktop UI. buff.ly/Ej7X94t

🐛 MetaMask breaks when anvil restarts MetaMask tracks nonces locally. When anvil reverts, those nonces no longer match the chain → MetaMask fails to sign valid transactions. ethui calculates nonces from chain state every time. Restart anvil freely.

MetaMask is built for consumers. ethui is built for developers. At the surface, ethui replaces MetaMask. Underneath, it handles what MetaMask can't: ✅ Survives anvil restarts ✅ Nonce from chain state, not cache ✅ Test wallets (plaintext, impersonator) ✅ Built-in contract explorer

🎯 Developer-first wallet ethui is built specifically for Ethereum developers, not consumers: ✅ Local-first (anvil integration) ✅ Forge/Hardhat native support ✅ Multi-wallet/chain testing ✅ Desktop app architecture Not competing with MetaMask. Different problems. ethui.dev

🏠 Self-host ethui stacks Prefer to run it yourself? ethui stacks is open source: ✅ Deploy on your infrastructure ✅ Full data control ✅ No vendor lock-in ✅ Same features Free hosted OR self-host. github.com/ethui/stacks stacks.ethui.dev

⚙️ Open source development ethui is fully open source: ✅ Transparent development ✅ Community contributions ✅ Self-hostable ✅ Auditable code ✅ Extensible No vendor lock-in. Built in the open. github.com/ethui/ethui ethui.dev

📋 Automatic ABI indexing ethui scans compilation artifacts automatically: ✅ Forge/Hardhat ABIs detected ✅ No manual imports ✅ Auto-updates on recompile ✅ Instant contract UI Compile → interact. Zero config. ethui.dev/docs/feature...

🛡️ Auto-impersonation with safety ethui auto-impersonates addresses when needed, but ONLY on anvil: ✅ Auto-unlock addresses for testing ✅ No manual cheatcode calls ✅ Local anvil only (safety) ❌ Disabled on mainnet/testnets Convenience with safety. ethui.dev/docs/feature...

🎭 Impersonator wallet type Test from any address without private keys. ethui impersonator wallets: ✅ Become any address ✅ Test whale interactions ✅ Simulate DAO multisigs ✅ Works with anvil_impersonateAccount Test scenarios impossible to reproduce normally. ethui.dev/docs/wallets...

🔑 Private key wallet import Import raw private keys directly into ethui: ✅ From hex string ✅ scrypt encryption ✅ Password protected ✅ Quick setup For known test keys or quick access scenarios. Different wallet types for different needs. ethui.dev/docs/wallets...

📁 Import keystore wallets Have existing keystore JSON files? Import them directly into ethui. Standard Geth/MEW keystore format: ✅ Import existing wallets ✅ Password encrypted ✅ No recreation needed Bring your wallets over. ethui.dev/docs/wallets...

🔐 Ledger hardware wallet support ethui integrates with Ledger devices. Ready to test beyond local anvil? ✅ Connect Ledger ✅ Hardware-secured signing ✅ Production-grade security Plaintext wallets for local dev. Ledger for serious testing. ethui.dev/docs/wallets...

💻 Desktop app architecture ethui is native desktop software (not a browser extension): ✅ Multi-browser support ✅ Survives browser restarts ✅ Better security isolation ✅ Persistent state Built for developer workflows. ethui.dev

🔗 Per-website chain connections Each website connects to its own chain simultaneously: localhost:3000 → anvil app.uniswap.org → mainnet fork testdapp.io → sepolia All at once. Zero manual switching. Test multi-chain scenarios properly. ethui.dev/docs/feature...