Sabitlenmiş Tweet
Walnut
874 posts
Walnut
@walnut_dev
debugging blockchains https://t.co/qfcmNxwFTA
Ethereum Katılım Nisan 2021
1 Takip Edilen2.1K Takipçiler
Walnut retweetledi
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-…
English
@jchaskin22 nailed it.
Debugging shouldn't be owned by any single org. SolDB is ETHDebug-first, open standard by design, so any framework or tool can build on a shared core.
Thanks for the coverage @griffgreen
thedao.fund@thedaofund
Debugging is still one of the biggest pain points in Solidity development. soldb by @walnut_dev is an open-source CLI debugger for Solidity, built to give developers and tooling teams deeper visibility into EVM execution, transactions, storage, and contract behavior. Learn more: youtube.com/watch?v=9Fmo43… Support: qf.giveth.io/project/soldb-…
English
Walnut retweetledi
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!
banteg@banteg
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.
English
🔗 Full post: walnut.dev/blog/stylusdb-…
🔗 Repo: github.com/walnuthq/stylu…
English
@gakonst Modular Solidity debugger akin to GDB or LLDB, combined with standard debug info generated by all Solidity compilers.
github.com/walnuthq/soldb
English
Which crypto software do people really depend on they wish was faster, more modular, or open source?
English
Walnut retweetledi
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
Walnut@walnut_dev
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 🧵
English