Pinned Tweet
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.
walnut.dev/blog/argot-announ…
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
I was recently affected by the layoffs at @0xMiden, and I’m looking for my next Product Manager role in the Bay Area.
I’d love to keep building in payments, especially stablecoins and agentic payments.
Over the past few years at @0xMiden and @0xPolygon, I’ve:
• Led a crypto wallet from scoping through launch to reach 20k user registrations, coordinating a seven-person team across engineering, design, and QA.
• Worked with roughly 12 external ecosystem partners, translating their requirements, feedback, and integration blockers into roadmap and release priorities.
• Built and launched AggLayer’s developer portal and sandbox, with tutorials and code examples to help developers get started.
• Researched zero-knowledge infrastructure and develop the Chainless Apps framework, connecting technical research with practical use cases for developers.
Working on a crypto wallet made the practical challenges of stablecoin adoption much clearer to me: how people bring funds in, move them across networks, and actually use them.
I want to keep working on those problems, including how AI agents will make payments.
I’ve also been building an offline, on-device LLM app and AI-assisted workflows for team syncs, product feedback, and moving GitHub issues through implementation. I’m comfortable getting into the code as well as owning the product.
If you know PM hiring managers at @Stablecoin, @stripe, @Visa, or other teams building payments infrastructure and AI products, I’d really appreciate an introduction!
And to my teammates at Miden and Polygon Labs: thank you. I’ve learned a lot from building with you, and wish you all the best!
Walnut retweeted
New blog post out!
@ethdebug is an open format for compilers to explain their output in a developer's own language.
Our first post about it on the Argot blog covers this year's progress, with interactive visuals that run on actual compiler output.
Walnut retweeted
Love working with the @walnut_dev team
Check out playground.miden.xyz/ to better understand how Miden works 😉
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 👇
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.
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 🧵
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.
1
42
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: walnut.dev/blog/introducing-…
36
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/
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 👇
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/
Try Bread, its good for you 👇
@0xMiden making moves, exciting times ahead!
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/…
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.
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!
2
759


















