espi
@espicodes
Followers
2K
Following
2K
Media
162
Statuses
1K
Engineering @JupiterExchange Co-founded @abklabs. Core contributor on @metaplex DAS, @triton_one Yellowstone OSS, @anza_xyz Codama.
Joined August 2017
Thank you @italoacasas for bringing us together. I’m excited to be contributing to RPC at @JupiterExchange.
The @JupiterExchange team keeps leveling up. Every addition pushes the bar higher. Excited to have @espicodes, @nagaprasad_246, @GroovieGer88951, and @_fanatid join the team; it's hard to match this much Solana brain power in one room. Lots in store... 🚢🚢
6
0
28
Stoked to be advising and contributing to $HYPER. Just watched the latest demo—and I’m in love. Tune in next Tuesday. You’re gonna fall for it too. 🎭 on.
Next Tuesday, @hungrytrtl and I are pitching HyperStack to @aeyakovenko @blknoiz06 @0xMert_ and @QwQiao. Solana is fast. Building on it isn’t. We’re fixing that. HyperStack turns your program into app-ready infra in 5 minutes. Open-source, Firebase-style, dev-friendly. Big
0
0
4
One of us.
Been working on this @triton_one will have @anza_xyz • High-throughput @solana_devs streaming (>2.7 MTPS) • Multi-threaded processing + slot reordering • Epoch/slot range conversion with validation • Comprehensive config system + testing • Vixen pipeline integration
3
0
37
🚀 Issue Open: We’re adding @anza_xyz Jetstreamer as a new data source to Yellowstone Vixen! This will enable ultra-fast historical backfill from Old Faithful directly into the Vixen pipeline. 👉 https://t.co/GzqQeQjHmQ Open source contributions welcome 💛
github.com
🧩 Context Jetstreamer is a high-throughput toolkit for streaming historical Solana ledger data from the Old Faithful archive. It can replay transactions and blocks from any epoch or slot range at...
Proud to announce the initial public release of #Jetstreamer ✈️ which can stream all transactions and blocks since #Solana genesis against a local plugin at 2.7M+ TPS or 12 epochs/hour 🔥! Powered by @triton_one's Old Faithful archive, free for everyone! https://t.co/yWZRq9Xa13
1
2
20
We are approaching a playable demo of FAANG Origins. Follow the account for updates.
The battle begins ⚔️ Welcome to FAANG Origins a competitive, tactical, turn-based PvP experience forged on Solana. ♟️ Strategic gameplay chess 🛡️ Player-owned assets 🌐 True on-chain competition Do you have what it takes to rise through the shadows? #FAANGOrigins
0
0
4
Jupiter’s own @mandarin_canard just landed a slick upgrade to Yellowstone Vixen: handlers now get access to the raw update event. It’s a pattern you’ll recognize — just like how HTTP clients pass the raw response as the last argument in a callback. Clean, powerful, and
1
0
8
Wow. This is epic. The amount of bandwidth and access to shreds we have now is insane. Absolute game-changer. And honestly? I don’t care how good your tech is—if you don’t have stake, you’re not even in the game. @JupiterExchange runs the game.
1
0
21
If you're not following Wincode, you're missing out on a lot of things. @ax_1000x can confirm 😂
wincode v0.1.2 released - zerocopy deserialization for byte slices - automatic single-pass memcpy specialization for collection types containing bytes (Vec<u8>, [u8; N], etc) (no longer need to annotate Pod) - tuples now panic safe - doc improvements https://t.co/oSjkELNm0X
1
3
18
Tomorrow is the day. Come join me at 15:25 UTC to learn about Yellowstone Vixen, Solana program parsing toolkit. See you then!
Yellowstone Vixen by @triton_one 🔥Join and learn to build real-time, program-aware data pipelines on @Solana - turning on-chain events into actionable insights 🚀 ft. @espicodes from @JupiterExchange
3
2
22
I'll be presenting Yellowstone Vixen. Come learn about program indexing and other great OSS Solana tooling at @solanaturbine Toolapalooza.
It's here.... the Alpha Drops NOW- @solana_devs Tooling and the @solana DevEx will never be the same.
2
3
21
X402 v2 spec proposal are open for discussion. We are seeking contributors to aid in the implementation of v2. Please comment on GitHub if you are willing and able. Link 🧵
16
13
91
Got your own Linear tips? Reply below and let’s make our workflows better 🧠⬇️
1
0
1
5. 🧹 Archive Ruthlessly Don’t let old issues rot. 📦 Archive closed, stale, or irrelevant work often. A clean board = a clear head.
1
0
1
4. 🧱 Structure with Initiatives Initiatives = objectives Projects = key results They give shape to quarters and keep strategy aligned.
1
0
1
3. 📝 Use Project Updates Updates = async reflection, not status spam. ✅ Share progress ⚠️ Raise blockers early 🔁 Review updates as retros 💡 Tip: Post every 2–3 days during active work.
1
0
1
2. 📦 Keep Projects Small Aim for 3–12 issues, closed in 1–2.5 weeks. Short projects build momentum and make pivots easy. Bonus: Run 3–5 day “quick win” projects for fast wins. 🥇
1
0
1
1. 🎯 Keep Teams Laser-Focused Avoid mixing scopes in one team. If you’re constantly filtering/hiding—split it. One team per repo or product line works well for devs.
1
0
1
💡 How to Get the Most Out of @linear A quick guide for teams to keep your boards clean, scoped, and effective 👇
1
0
3