Sabitlenmiş Tweet
New project drop: cairovm.codes 💅💅
Inspired by @smlxldotio's evm.codes, cairovm.codes seeks to provide an interactive guide to unravel the complexities of CairoVM on @Starknet
Read on to understand why & roadmap 👇
English
Walnut
813 posts
Walnut
@walnut_dev
debugging blockchains https://t.co/qfcmNxwFTA
Ethereum Katılım Nisan 2021
0 Takip Edilen2.2K Takipçiler
Walnut retweetledi
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.
English
🌰🔩 Weekly nuts and bolts 🔩🌰
This week we focused on tightening the internals and cracking a few stability bugs 👇
1️⃣ Core processing optimization: Reduced redundant operations in the core processing pipeline to improve overall responsiveness.
2️⃣ Fixed toast memory leak: Resolved a memory leak in the notification system that could slow the app down over time.
3️⃣ Cache management improvements: Refined cache logic so data loads faster and stays consistent while navigating the app.
4️⃣ Better internal logging: Expanded logging and monitoring to help us detect and crack bugs faster.
English
We fully agree with ser @EliBenSasson
And we are lucky enough to partner with two on the list: @Starknet and @0xMiden
Coming your way @RiscZero 🫡
Eli Ben-Sasson | Starknet.io@EliBenSasson
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.
English
Walnut retweetledi
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.
English
🌰🔩 Weekly nuts and bolts 🔩🌰
This week we improved L2 gas visibility on @Starknet and fixed edge cases around Scarb builds for verified contracts.
1️⃣ L2 gas flamecharts without full Sierra 1.7.0 adoption — Flamecharts now render even if not all classes are Sierra > 1.7.0, so you get consistent gas profiling across mixed-version projects.
2️⃣ L2 gas in transaction overview — We now display L2 gas directly in the simulation transaction overview, making cost analysis faster and more explicit.
3️⃣ Fixed Scarb build failures for Voyager-verified contracts — Resolved an issue where Scarb builds failed due to a missing .lock file when compiling contracts verified via Voyager.
English
Walnut retweetledi
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 >>
Starknet (Privacy arc) 🥷@Starknet
1/ It’s finally time for Bitcoin to get privacy. Introducing strkBTC [₿]: a new wrapped Bitcoin token with built-in privacy capabilities. Shield your Bitcoin balances and transfers, or don’t. You choose 🧵
English
Walnut retweetledi
Bitcoin + Privacy + ZK
It took 5 years but the thesis is finally shipping.
I'm incredibly excited
Starknet (Privacy arc) 🥷@Starknet
1/ It’s finally time for Bitcoin to get privacy. Introducing strkBTC [₿]: a new wrapped Bitcoin token with built-in privacy capabilities. Shield your Bitcoin balances and transfers, or don’t. You choose 🧵
English
Walnut retweetledi
1/ It’s finally time for Bitcoin to get privacy.
Introducing strkBTC [₿]: a new wrapped Bitcoin token with built-in privacy capabilities.
Shield your Bitcoin balances and transfers, or don’t. You choose 🧵
English
Starknet continues to lead on both Bitcoin and Privacy fronts
Starknet (Privacy arc) 🥷@Starknet
1/ It’s finally time for Bitcoin to get privacy. Introducing strkBTC [₿]: a new wrapped Bitcoin token with built-in privacy capabilities. Shield your Bitcoin balances and transfers, or don’t. You choose 🧵
English
@ajwarner90 We can optimize more through compiler optimisations
x.com/walnut_dev/sta…
Would love to collaborate 🫡
Walnut@walnut_dev
This is exciting and here is how to make it even better Scaling isn’t just about the execution client — the compiler is the other side of the coin. Better compiled contracts = less gas per transaction = more throughput for the same hardware. Web3 should leverage battle-tested compiler infra like MLIR instead of building optimization passes from scratch. We proved it works — plugged an MLIR pipeline into solc and got real gas savings. * Up to 25% gas savings compared to --via-ir * Up to 50% code size savings compared to --via-ir #issuecomment-3855141597" target="_blank" rel="nofollow noopener">github.com/walnuthq/solid…
dms open if you are interested in exploring this English
We are going to bring a lot more scale to Arbitrum. We need to for our mission to power global finance and independent economies.
Arbitrum Everywhere
Nethermind@Nethermind
Nethermind's execution client implementation for Arbitrum is now public. Nethermind processes, on average, 1.4 Ggas/s on a typical Ethereum staking machine. With the Nethermind client on @arbitrum, we will be able to push the frontier of performance and throughput for Arbitrum chains. Where it stands: full node execution processing over 300M Arbitrum One archive blocks, with Stylus smart contract support. Correctness is validated by running Nethermind alongside Nitro's native execution layer in comparison mode. In progress: validator mode, sequencer support. The work should be visible and verifiable as it matures. github.com/NethermindEth/…
English
This is exciting and here is how to make it even better
Scaling isn’t just about the execution client — the compiler is the other side of the coin. Better compiled contracts = less gas per transaction = more throughput for the same hardware.
Web3 should leverage battle-tested compiler infra like MLIR instead of building optimization passes from scratch. We proved it works — plugged an MLIR pipeline into solc and got real gas savings.
* Up to 25% gas savings compared to --via-ir
* Up to 50% code size savings compared to --via-ir
#issuecomment-3855141597" target="_blank" rel="nofollow noopener">github.com/walnuthq/solid…
dms open if you are interested in exploring this
Nethermind@Nethermind
Nethermind's execution client implementation for Arbitrum is now public. Nethermind processes, on average, 1.4 Ggas/s on a typical Ethereum staking machine. With the Nethermind client on @arbitrum, we will be able to push the frontier of performance and throughput for Arbitrum chains. Where it stands: full node execution processing over 300M Arbitrum One archive blocks, with Stylus smart contract support. Correctness is validated by running Nethermind alongside Nitro's native execution layer in comparison mode. In progress: validator mode, sequencer support. The work should be visible and verifiable as it matures. github.com/NethermindEth/…
English
🌰🔩 Weekly nuts and bolts 🔩🌰
Market noise aside — we keep cracking bugs and tightening the bolts. This week we improved debug data for Voyager-verified contracts on @Starknet 👇
1️⃣ Voyager call trace support — Contracts verified via Voyager now display function calls directly in the Call Trace, making execution flow easier to follow.
2️⃣ Full step-by-step debugger restored — Fixed an issue that prevented complete Debugger data from loading for Voyager-verified contracts.
3️⃣ Debug button highlight fix — Resolved a UI bug where the Debug button was not properly highlighted for Voyager-verified contracts.
4️⃣ Correct calldata re-simulation — Fixed a bug where decoded calldata was sent without type names during re-simulation, leading to incorrect encoding.
English
🌰🔩 Weekly nuts and bolts 🔩🌰
The market is bleeding, but the Walnut team keeps shipping, and you should too!
While timelines slip elsewhere, we’re tightening stability and sharpening simulation ergonomics across @Starknet.
1️⃣ Verification source badges — Contracts now clearly show whether they’re verified via Voyager or Walnut, so you always know where the source of truth comes from.
2️⃣ Server timeout fix — Resolved a backend timeout issue that was causing intermittent instability. Fewer dropped requests, more predictable debugging.
3️⃣ Better struct support in simulations — Fixed rendering for deeply nested types (e.g. Layout → FieldLayout → Layout) in the Simulation Form, so complex Cairo structs no longer crack the UI.
English
🌰🔩 Weekly nuts and bolts 🔩🌰
We keep cracking bugs and wiring Walnut deeper into the Starknet toolchain. This week was about closing the gap between verification and debugging, with a tight integration into @Starknet’s verification flow via Voyager.
1️⃣ Voyager verification integration — Contracts verified through Voyager now show up directly in Walnut, no extra setup required.
2️⃣ Debugger support for verified contracts — You can step through Voyager-verified contracts in the debugger and inspect execution with full context.
Less friction between “verified” and “debuggable.” More signal, fewer nuts left loose.
English
🌰🔩 Weekly nuts and bolts 🔩🌰
The Walnut team keeps cracking bugs and tightening the bolts. This week was about trace accuracy and clearer contract data.
1️⃣ Complete token transfer traces — Added the missing token transfer call to transaction traces, giving a full and accurate execution flow.
2️⃣ Enum variant names everywhere — Enum variants now render by name across the UI, making decoded data easier to reason about.
3️⃣ Struct member types in simulations — Simulation forms now show struct member types, so inputs are explicit and harder to mess up.
English
Hi @0xMiden @walnut_dev
I'm testing Playground and I'm stuck at the step of getting tokens via faucet. Can you tell me where the error is and how to fix it?
English
🌰🔩 Weekly nuts and bolts 🔩🌰
The Walnut team keeps shipping—tightening infra and UI details that tend to break when no one’s looking. This week was about RPC sanity and a less fragile header, especially on smaller screens. @Starknet devs, this one’s for you.
1️⃣ RPC URL normalization — URLs with and without trailing slashes are now treated as the same endpoint. No more duplicate RPCs because of a missing /.
2️⃣ Header responsiveness improvements — Cleaned up breakpoints so the network badge, search, and user section behave predictably across screen sizes.
3️⃣ Better mobile header UX — Improved button visibility and text wrapping to avoid cramped, half-hidden controls on small screens.
Small cracks sealed before they turn into nuts-up bugs.
English