Walnut

debugging blockchains

[Walnut @walnut_dev]

We're partnering with @argotorg to implement the @ethdebug standard inside the official @solidity_lang compiler.

solc will emit the debug metadata it's been missing.

https://t.co/0EvUmfKwx1

[Argot Collective @argotorg]

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 @walnut_dev]

https://t.co/pNqQmtJtTR

[Walnut @walnut_dev]

@0xMiden helps the future of finance handle privacy. As mainnet approaches, we've kept working with the team on developer tooling. This post covers what we shipped in the Miden ecosystem in Q3 2026.

[Walnut @walnut_dev]

https://t.co/okQHkOPE2a

[Walnut @walnut_dev]

Headlines said Robinhood Chain halted for 14 minutes on Sept 4. Block timestamps say it never stopped, and @arbitrum said the same.

What users actually hit: 40 minutes of dropped transactions, ~80% rejected at the peak. We traced it from public data. @RobinhoodCrypto

Full deep dive in the comment 👇

[Arbitrum @arbitrum]

Robinhood Chain experienced no downtime.

Earlier today, Robinhood Chain experienced batch posting delays due to L1 market blob behavior. Direct user transactions experienced no delays.

Some infrastructure providers that rely on Robinhood Chain’s data stream experienced a brief performance impact due to a high number of feed subscribers.

Robinhood Chain remains operational.

[Dominik Schmid @schmiddominik1]

This is extremely cool! Try it

[Walnut @walnut_dev]

5/ Our goal is simple: give Miden developers the same fast feedback loop Foundry gives Ethereum developers.

Try miden call with midenup v1.0.1: https://t.co/Zxu026Ziwl

[Walnut @walnut_dev]

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 @walnut_dev]

4/ Next, miden send will prove and submit transactions, while --trace will expose the call hierarchy, arguments, and results.

We’re also planning a local package registry, fuzz testing, and chain forking—especially important as Miden developers navigate private state.

[BRIAN SΞONG @BrianSeong]

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. https://t.co/CSGJXPNQGo

[Argot Collective @argotorg]

Round Two of @thedaofund is live and it's never been easier to support Ethereum security!

Go check out all initiatives and consider contributing 🫡

[Walnut @walnut_dev]

Let's make @ethereum more secure.

Only a handful of teams made @thedaofund's shortlist for their new Security Fund. Walnut is one of them.

Thank you @argotorg for the collab!

Read on below 👇

[thedao.fund @thedaofund]

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.

https://t.co/3uj1FmFLNb

[Walnut @walnut_dev]

Try Bread, its good for you 👇

@0xMiden making moves, exciting times ahead!

[Bread @joinbread]

Privacy made simple.

Early access 👉 https://t.co/gqEtLDaY3o

[Walnut @walnut_dev]

@schmiddominik1 🍞

[Walnut @walnut_dev]

@zkGaylord 🍞

[Dominik Schmid @schmiddominik1]

Awesome analysis on permissioned vs public chains and the ability for actors to comply

[Walnut @walnut_dev]

centaur's been core to how we operate at @walnut_dev - excited to get 2.0 into the mix. will share more on our setup soon.

[Georgios Konstantopoulos @gakonst]

Announcing Centaur 2.0!

Centaur is frontier, agentic infrastructure that you own. Centaur is like Claude Tag, but open source and on steroids.

Centaur 2.0 can connect to everything you have access to, and can reason over it next to where you work, either in Slack, Discord, Teams or in your local Codex or Claude Code via an MCP.

But context isn't useful if it can be accessed by anyone, so we rebuilt Centaur from the ground up for security. Centaur obviously doesn't have access to secrets because we're leveraging egress proxies.

Centaur 2.0 takes that a step further enabling administrators to configure who can access what from where. This means that Centaur can have access to private information that you normally wouldn't feel comfortable giving it access to (e.g. DMs or sensitive channels and docs) but only expose it to authorized principals.

It also means you can add Centaur to external channels and leverage it as a virtual colleague that doesn't live only in your Slack, for example, but also your Slack Connect channels! This is extremely powerful as we start moving to a world where agents cross organizational boundaries.

Also in case anyone's wondering, yes we rewrote it in Rust! Centaur is now way way more stable at durably executing threads, and its workflow engine is now based on Absurd.

We have been operating Centaur since January, officially launched and Open Sourced it in May, and now we're full speed towards making it the #1 open source agentic infrastructure.

To succeed at that, I'm thrilled to welcome @mslipper to the @paradigm team who will be leading all our Applied AI work, while continuing to maintain and extend Iron Proxy as the leading secure secret access for agents. Welcome Matt, it's an honor after all these years of knowing you!

Read the full blogpost below, and apply to join our team!

[Vikkixbt @vikkixbt]

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 🧡