Local first, dev & trading environment for Solana.
🏆 Award winning devtool - #1 Infra Colosseum 2025
Follow for tips & releases.
@ludo_txtx & @micaiah_txtx
🎉 Big day for Surfpool!
Surfpool just made its way into the official Solana developer stack — right in the installation docs.
We always built Surfpool to feel like the “dev mode” Solana deserved… and seeing it land in the canonical path for builders is surreal.
Huge thanks to everyone who has tested, contributed, and pushed us forward - just way too many names 😂
Follow @surfpool_sol to stay up to date with our progress!
👉
https://t.co/Z8gLjgwE7h
one of the big issues I ran into with my e2e sims at first was how long running they were. luckily with @surfpool_sol i can use cheat codes like time travel to scale them easier. its been a really amazing local development tool for me.
Workshop @solanaturbine was really good
it was a deep dive into Surfpool and testing in Surfpool
Yaaa , sometimes I felt a little lost, but it was very interesting and gave a deep understanding of the runbook / testing
@surfpool_sol
full e2e with 32 passing tests for v3.4.0 using @surfpool_sol. sim it 🫰🫠 this is designed to test the entire token lifecycle, vault routing, etc. time travel is such a cool cheatcode
I'm excited to announce @beeman/testcontainers: Docker-based test containers for Solana development 🥳
Spin up solana-test-validator or @surfpool_sol in your tests with a single line of code.
I'm thinking about adding on for Kora, what more should I add?
Surfpool launch week - day 2: Infrastructure as Code.
Bash scripts. Hardcoded keypaths. Private keys in plaintext.
Web3 DevSecOps are fundamentally hard, and broken.
Runbooks are the perfect solution.
https://t.co/ok6q9yNPJV
Run your bot like its on mainnet but with fake #Solana
Swaps using @JupiterExchange API, @PythNetwork price feeds all locally using @surfpool_sol using scenario builder.
Great way to test your trading strategies.
https://t.co/80jDT92635
PR #457 just got merged into @surfpool_sol
Worked on fixing a critical edge case where Surfpool would stop producing blocks when a Solana program close error occurred, caused by disconnected channels in the RPC handler now the status channel always sends a response first, preventing the simnet from stalling .
What I learned:
• Deep dive into RpcSVM & process_transaction flow
• Handling async channels and ensuring reliable status propagation
• Debugging core simulator logic in Rust
Recovery from “program close” errors so Surfpool keeps simulating blocks smoothly ...
https://t.co/tktRl3UlwA
@solanaturbine@solana@SuperteamIN@superteam@jacobvcreech@micaiah_txtx
A single open source contribution can teach a lot ... i went through @surfpool_sol got to know bout crossbeam realized the knowledge gap and then studied about the async backends made few projects got resources from @solanaturbine dc and now feeling confident ... built a CLOB
GM @solana Devs!
✅Today I will finish episode 4. Focus on Solana transactions.
❌Many use the default 200k CU limit!
✅Better determine the compute units your Tx consumes
👉Minimum units === increasing the chance of your Tx being included
Course here:
https://t.co/eeALg2UUjZ
@digbenjamins@solana love it! let us know if there’s anything we can do to support. if you hit limitations / bugs, experience friction / suboptimal devex or have feature requests, we’d like to help.
One of my @solana 2026 goals is to create a full beginner to advanced series.
I already started. First 3 videos available.
https://t.co/QEpnIxX2aF
We are going to cover all topics step by step following the #Solana Cookbook series and documentation.
Using the latest like @surfpool_sol@anza_xyz Solana Kit
on the surfpool front, I would not classify this as a memory leak - we usually talk about memory leak when that's accidental - in our case, that was by design: a surfnet is keeping all its data (accounts, transactions, etc) in memory and never touching the disk.
Durable surfnets are coming soon, give us 1-2 weeks!