Tired of slow feedback loops and clunky wallet workflows in web3 dev?
ethui bundles Foundry/Anvil integration, contract exploration, and multi-wallet support into one desktop tool.
We're in Gitcoin. Donate to keep it open-source → https://t.co/jcE8TlxCX8
$1+ helps. Closes Oct 28.
#EthereumDev #Web3 #Ethereum #DevTools
🐛 Hardhat artifacts don't auto-connect to your wallet.
Most wallets have no idea what contracts you deployed after hardhat compile.
ethui scans artifacts in real time and matches deployed bytecode.
Contract explorer appears automatically. No imports, no address lookups.
https://t.co/doLk551zVi
ethui was designed and built by @subvisual.
The full story, the problem, the architecture, and what shipping a desktop Ethereum dev tool actually looks like, is now live.
https://t.co/dDJuCZ811m
Every Ethereum developer has hit the same wall.
MetaMask doesn't know you just compiled a contract. Your wallet has no idea what you deployed 10 seconds ago.
@naps62 built ethui to fix that. A desktop-native, Foundry-aware Ethereum toolkit, built in Rust.
Case study → link in bio
#ethereum #developertools #foundry #opensource
🔧 The missing piece in your Web3 dev stack
You have forged contracts. anvil for the local chain.
But what connects them to your dApp's frontend?
ethui sits between your local chain and your browser:
✅ Reads ABIs automatically
✅ Bridges the browser to anvil
✅ Manages your test wallets
The glue layer is handled.
🌐 Multi-chain development, in practice
Testing cross-chain behavior?
→ Open Chrome, connect to your mainnet fork
→ Open Firefox, connect to your local L2 anvil instance
→ Both active simultaneously in ethui
→ Different sites on different chains
One wallet manager. Multiple browsers. Multiple chains.
⚡ Create a stack. Add it to your wallet. Start building.
That's the entire setup flow.
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 configuration. 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 between chains or environments
Reply 👇
🔍 How ethui identifies deployed contracts
It matches on-chain bytecode.
After you deploy, ethui compares what's on-chain against ABIs in your forge /out directory.
Match found → contract explorer appears, labeled with your contract names.
No address lookup needed. No manual labeling.
🔗 How forge + anvil + ethui fit together
1. forge compiles → artifacts in /out
2. ethui watches /out → reads ABIs in real-time
3. anvil runs → ethui detects it via anvil_nodeInfo
4. ethui matches bytecode to ABIs → contract explorer ready
One workflow. Zero glue code.
🛠️ Override code at any address on anvil
Most devs know about overriding ETH balances for testing.
But anvil also lets you override CODE at any address.
Replace the bytecode deployed at any address — not possible on production chains.
ethui gives you this full anvil environment.
🏗️ ethui stacks for staging environments
Not just local dev or user interviews.
A stack gives your team a shared environment:
✅ Fork any live network for real protocol state
✅ Private API key — only your team has access
✅ Persistent between sessions
✅ Full anvil speed and cheatcodes
Team staging, simplified.
🔐 ethui for smart contract auditors
Need to test from a specific address without holding the private key?
ethui's impersonator wallet lets you become any address on anvil. Pair it with the built-in contract explorer for direct interaction.
No external tools. No keys. Just audit.
💬 Ethereum devs: Foundry or Hardhat?
ethui natively supports Foundry — auto-detects forge projects, reads ABIs, and syncs the contract explorer in real time.
Curious about the community split. Which framework do you primarily build with?
a) Foundry
b) Hardhat
c) Both, depending on the project
Reply 👇
⚡ Fast mode: skip dialogs AND private key decryption
Most devs know fast mode skips transaction confirmations.
Lesser-known: it also skips private-key decryption. ethui submits unsigned transactions directly to the chain.
Only possible on anvil. Toggle it from the sidebar.
🔄 Real-time ABI sync with forge build --watch
ethui watches your forge project's /out directory in real-time.
Run forge build --watch → ethui updates the contract explorer as your contracts change.
Compile once or continuously. ethui stays in sync either way.
Zero manual steps.
🔍 "Think Etherscan, but for your local development setup."
That's exactly what ethui's contract explorer is.
It matches on-chain bytecode against ABIs from your forge /out directory, then generates a UI to interact with those contracts.
No manual setup. No address lookup. Just build.
📊 April at ethui — a recap
This month:
→ ethui vs MetaMask: different tools, different jobs
→ How the extension + desktop app architecture works
→ Anvil-aware syncing engine deep dive
→ ethui stacks: private API keys + subgraph support in dev
May: more technical deep dives.
What would you like us to cover?
🔢 A small detail that saves hours of debugging
Most wallets cache transaction nonces locally.
Problem: anvil reverts and your cache is now wrong. Transactions fail. Debugging begins.
ethui calculates nonces directly from chain state on every transaction.
More computation. Always accurate. No stale state.
💡 Replace MetaMask in your dev workflow
ethui is a drop-in replacement for MetaMask and Rabby during development.
Same wallet connect flow. Same browser extension experience.
But built for dev:
✅ Anvil-aware syncing
✅ Test-focused wallets
✅ Built-in contract explorer
✅ Fast mode (skip confirmations)
✅ Transaction simulations
🛠️ What we're building next for ethui stacks: subgraph support
A subgraph needs:
• PostgreSQL database
• IPFS node
• Indexer node
We're working to manage all of this inside a stack automatically.
The tricky part: handling anvil reverts correctly across all components.
Building in the open. Feedback welcome.