debugging blockchains https://xitter.cf/t.co/qfcmNxwFTA
Ethereum
Joined April 2021
- Tweets964
- Following1
- Followers2.1K
- Likes2.1K
Walnut retweeted
This is extremely cool! Try it
Introducing Miden Foundry
@0xMiden devs can now preview transactions before they hit the chain.
Walnut is building Miden Foundry in partnership with Miden. The first tool, miden call, ships in midenup v1.0.1.
Thread time 🧵
Walnut retweeted
Ethereum has cast call: dry-run a contract call without sending a tx.
@0xMiden now has miden call from @walnut_dev.
Same job — run a procedure, see what it returns — plus the Miden-shaped extras: notes, storage maps, vault diffs. Runs on your laptop. Nothing hits the network.
First brick of Foundry-like tooling, not the whole toolkit. walnut.dev/blog/introducing-…
Walnut retweeted
Round Two of @thedaofund is live and it's never been easier to support Ethereum security!
Go check out all initiatives and consider contributing 🫡
Onchain security is everyone’s problem and nobody’s job.
ETHSecurity Initiatives is how we are changing that.
Propose the work. Fund the work. Build the work.
initiatives.thedao.fund/
Walnut retweeted
Awesome analysis on permissioned vs public chains and the ability for actors to comply
A new paper by Rebecca Rettig, Omid Malekan, and Michael Mosier takes aim at the assumption that regulated financial institutions must use permissioned networks.
They argue that existing law makes no such demand and that privacy and compliance can work on open networks too.
@btschiller explains why the paper matters for privacy and permissionless networks in this week’s Privacy Dispatch.
privacydispatch.beehiiv.com/…
Walnut retweeted
Quietly strong quarter from @0xMiden. @walnut_dev just dropped the Q2 2026 update and the more I read, the more it’s clear the team has been heads down shipping real developer experience improvements.
The biggest one for me: full end to end transaction debugging is live now. You can step through entire ZK transactions, kernel calls included, using real accounts and notes.
It feels almost like debugging normal Rust code, which is genuinely wild when you remember this is zero knowledge tooling. Anyone who’s tried to debug ZK stuff before knows how much of a black box it usually is, so this is a big deal.
They also shipped DAP support for VS Code, with Zed coming soon, plus flamegraphs for digging into performance bottlenecks. Little things, but they add up to an environment that actually feels usable.
miden call is shaping up really nicely too. You can run procedures locally and inspect the results and state changes without the usual headache of guessing what happened under the hood.
On top of that: → a cleaner testing framework covering notes, failures, storage and auth flows → improvements to miden verify → contract verification is now a shared service, so explorers, wallets and the Playground all tap into the same thing instead of duplicating the same work over and over
And the Miden Playground got a solid refresh better testnet alignment, GitHub imports, local project support, and automatic verification baked in.
Been keeping an eye on these guys for a while, and the trajectory here is hard to ignore.
The dev experience is going from “promising” to genuinely good, and they’re doing it without much noise. No hype cycles, no empty roadmaps just consistent shipping quarter after quarter.
That’s usually the kind of team worth paying attention to early.
If you’re building in ZK, go read the full Q2 update from @walnut_dev and if you’ve already tried the new debugging flow, I want to hear how it felt.
gMiden 🧡
🤖 Made with AI
Walnut retweeted
Looking for a UX design contractor who can help our product designer with our next product.
Please send me a message if you
- have 5-10y experience in UX design
- can prove you have worked on a fintech consumer facing product (like a wallet)
- know how to set up UX processes
Walnut retweeted
Congrats @walnut_dev!
Nice side quest 😉
We teamed up with @walnut_dev to implement the @ethdebug standard inside the @solidity_lang compiler.
The 2025 Solidity Developer Survey shows the demand clearly.
This year we're tackling long-standing issues head on: alongside stack-too-deep, we're now taking on better debugging infrastructure.
Walnut retweeted
The latest Giveth newsletter is out 💜
Inside:
🛡️ @thedaofund Ethereum Security QF Round results and 638 ETH+ distributed
📊 A new dashboard to explore the round data
🤝 GIVfriend of the month: @wintermute_t
🙌 Featured project: @BitFinding
🏆 Newly verified projects: @walnut_dev, @dedaub
and much more
Walnut retweeted
Cross-border remittance corridors (e.g., US to Egypt): a multi-day process through intermediary banks and correspondents on legacy infrastructure vs. global settlement in seconds via blockchain rails
Read more: miden.xyz/blog/miden-for-neo…
Walnut retweeted
As an upcoming developer, I decided to explore Miden again today, and I found something interesting, @Walnut_dev.
If you’ve been following @0xMiden closely, then you’ve probably seen @walnut_dev around a lot.
They’re one of the teams helping improve the developer experience on Miden.
Quick breakdown 🧵
@walnut_dev is a blockchain developer infrastructure team focused on:
• debugging
• testing
• transaction simulation
• smart contract tooling
Their goal is simple:
Make blockchain development easier and more efficient.
They build tools for ecosystems like:
• Miden
• Starknet
• Arbitrum
• EVM chains
But their work on Miden has been especially important.
One of their biggest contributions is the Miden Playground.
This is a web-based environment where developers can:
• test the Miden VM
• build Rust smart contracts
• create accounts
• submit transactions
• learn through tutorials
It basically gives builders a hands-on way to explore Miden.
Walnut also built the Miden Debugger.
This tool helps developers:
• inspect transactions step-by-step
• track variables
• understand errors better
• debug Rust smart contracts easily
They also introduced contract verification infrastructure on Miden.
This allows developers to verify that deployed contracts actually match their source code.
The system is connected to MidenScan and also includes a CLI tool called "miden-verify".
Another major contribution is midenup.
Think of it like a Foundry-style toolkit for Miden developers.
It helps with:
• project setup
• local testing
• smart contract development
• running local nodes
Walnut is also working on:
• deployment infrastructure
• debugger upgrades
• testing improvements
• typed outputs
• better developer tooling overall
Beyond Miden, they also contribute to:
• Starknet tooling
• Arbitrum Stylus debugger
• Solidity debugging infrastructure
• Cairo playground tools
One of their newest projects is SolDB.
An open-source Solidity debugging system designed to improve transaction tracing and source-level debugging across the Ethereum ecosystem.
Walnut focuses heavily on open-source development and collaborates with teams across the Ethereum ecosystem.
If you’re interested in Miden development or blockchain tooling in general, @walnut_dev is definitely worth following.
Walnut retweeted
As promised. Today, we have a big announcement
We're launching registration for SpecSiege.
It's our double-check format for audits. First, an internal private audit went through the code with a full manual review. Then the community review follows. 10 days of open review on a fairly large codebase, we know, but the chance to work on an ERC-6909 European bond platform, an institutional project, doesn't come around every day.
- €15K total pot (€13K community pool, €2K fixed for the lead researcher).
- If only Lows are discovered, €5K is distributed instead.
Simply find bugs after us and get rewarded. We value your participation. We're not here just to squeeze you.
Link below ⬇️
Walnut retweeted
Soldb by @walnut_dev : an open-source Solidity debugger. Working on a debugger myself, I know how difficult and resource-intensive this work is. Every Solidity developer ever knows the pain of debugging smart contracts. This is a real chance to improve this situation.
qf.giveth.io/project/soldb-o…
Walnut retweeted
GM - Won't relitigate past EF decisions. These are not mine to callout. Forward-looking part is.
One nit: less than 10% of argot's 2025 budget went to fe (~$200k for H2). It's public info.
The real problem isn't misallocation of fe vs vyper or why Fe sits under Argot while Vyper is working on generating revenue (shoutout to @nachortti for helping Vyper here), despite its adoption.
The real problem is across the entire compiler stack. Fe with Sonatina, Vyper with Venom, Plank with its new IR, solx with LLVM, even Solidity is rewriting (core-sol with SAIL). They are all rebuilding the entire compiler. So many overlapping efforts inside one ecosystem, many trying to do the same thing. Yul has tech debt, sure but the answer cannot be N teams forking N IRs in isolation, all N looking for funding, taking years to be safe while the production compiler securing 500B+ across 20+ EVM chains passes the hat.
Two asides:
1. genuinely glad I'm not on the solc team. Any minor change there touches that entire 500B $ surface. Huge shoutout to @solidity_lang engs. Legends.
2. shoutout to @real_philogy for collaborating with fe and core-sol toward a shared IR. Building a language is hard enough but share what is possible, especially if things take years to be safe.
Anyway, what I'm doing about it:
- call with argot - learning about Fe's past.
- double down with @nachortti on Odin - ideally all language, compiler teams should have a sustainable path for revenue.
- from my seat at the EF, working on devex. A short-term fix for stack-too-deep is in sight, while solar, solx and the solidity team work on the real long-term solution
- funding languages going forward with a strategy that links the ecosystem instead of fragmenting it further
8 years in and developer pain points haven't moved enough. Time to solve them!
argot was spun out of ethereum foundation with a mandate to maintain ethereum's core programming languages and developer tooling.
then it immediately begins to launder research as if it was core infrastructure maintenance.
if you read their blog, they spend a lot of resources on fe, a language that has been "emerging" for over 5 years. they have long plans for fe, while the language itself has seen zero adoption and zero production use. their long term goal is "non-trivial contracts in production-like setting".
meanwhile vyper is actual production infrastructure. it secures real protocols, with real users and tvl, and real audit surface. curve, lido, yearn, frax, velodrome all use vyper.
yet vyper lives grant-to-grant, while argot started with a $16.6m check, about as much as ethereum started with.
argot doesn't disclose how much time and energy it spends on the fe fantasy versus solidity, sourcify, hevm, or other genuinely core tooling. but clearly this pet project abuses and stretches the mandate. even though it's a programming language, by no serious measure it's "core". it should spin out and try to survive and prove demand independently.
production compiler maintenance should get baseline funding before speculative language incubation gets considererd.
vyper is in good shape today despite the ecosystem, not because of it. and it still does not sit right with me that resources keep getting misallocated away from the compiler people actually use.
ethereum keeps saying "public goods", then funds the toy compiler like infrastructure and makes the production compiler pass the hat. that is not stewardship.
Walnut retweeted
Your agent can now debug Rust smart contracts on Miden. One year ago it took a good engineer one month to build something … with Claude, the compiler and this debugger it’s only one day for a prototype deployed
It's been a week since end-to-end transaction debugging landed for @0xMiden
Time for a proper walkthrough, so here's what changed for anyone building in the ecosystem today 🧵
Walnut retweeted
I built an AI dev toolkit for @0xMiden.
gave it to 11 people, most with zero Miden experience.
what they shipped in ONE DAY:
→ sealed-bid auctions with private bids
→ corporate wallets with cryptographic spending caps
→ time-locked capsules where nobody sees inside until unlock
→ oracle pools, on-chain games, battleship
the agent wrote the contracts.
the agent wrote the tests.
the agent wrote the frontend.
they just said what to build.
building on Miden just went from weeks → hours.
Walnut retweeted
Among crypto projects, two that I really like and respect are both in the area of ZK-STARKs:
1. The @0xMiden project (led by @bobbinth)
Many years ago, when I first spoke to Bobbin, he told me he was really interested in ZK-STARKs.
He basically started from his garage to build everything related to them: a whole compiler and virtual machine.
I found that very inspiring, and today he is leading one of the most interesting projects using ZK-STARKs.
2. The @RiscZero team
In a similar way, @BruestleJeremy and his team fell in love with the beauty, the post-quantum security, and the math of ZK-STARKs. They just started implementing it and have built a very impressive company and project.
It is interesting because these two projects are competitors of StarkWare in some way, but I view them very highly. I really hope each one of them succeeds in their own way, and maybe somewhere down the line we can collaborate rather than compete.
Walnut retweeted
HUGE: Bitcoin meets privacy!
Starknet enables:
1. Unlocking the Bitcoin economy with BTCFi
2. Delivering privacy using ZK-STARKs
Now combine them:
We're delivering privacy for the Bitcoin economy!
BTCFi’s benefits, with privacy, without friction.
BULLISH!
Link to join >>
Walnut retweeted
Bitcoin + Privacy + ZK
It took 5 years but the thesis is finally shipping.
I'm incredibly excited
