efe retweeted
From a Solana transaction signature to a function-level compute flamegraph.
Paste a mainnet signature. Replay it locally in LiteSVM. Then follow execution from the outer instruction through nested program calls to the functions consuming compute.
Step debugger: step through instructions and CPIs, inspect account changes, and stop at a failure. Change a value and re-run to see how execution responds.
Compute profiler: explore a flamegraph of compute by program and function, with Rust function names available for programs with verified builds.
Instruction introspection: inspect the Instructions sysvar to understand what a program knows about the surrounding transaction including the repayment instruction a flash loan checks before proceeding.
All in the same workspace, starting from a transaction that actually ran on mainnet.
Free and open source.
Try it: svmscope.vercel.app
Bring a transaction you've been trying to understand.
efe retweeted
Superteam TR Community Call #4 xitter.cf/i/broadcasts/1MJgNbrkO…
At work I had a feature that needed two things at once:
reviewers who could read it in layers,
and a tip I could actually test.
Classic stacked PRs gave me the layers.
They also gave me an endless hole:
implement on an incomplete product, rebase, CI on stubs, restack, repeat.
👇
So I stopped writing on the stack.
Build the Whole until it’s green.
Then project the stack so review is a view, not the workspace.
Tip tree == Whole tree. Product CI on the tip.
That’s Slicer. Spec + agent skills today, compiler not shipped yet.
github.com/beharefe/slicer
efe retweeted
Reminder: @solana is built by community, for community.
Looking for the ultimate cheat code to level up?
Show up IRL. Be present, build in the open, & give people a reason to remember you.
A real-life handshake > A thousand likes.











