Yellowstone Vixen is now Shipstern, under the Solana RPC Working Group. From hand-written parsers at Holaplex to Janus, the data backbone of @JupiterExchange. The full story and what's next. Using Shipstern? Reply, I want to hear how it can serve you.

Now this is a compliment.

Shipstern 0.10.0 is out. Agave 4.2.2 stack. Transaction V1 (SIMD-0385) now decodes end to end: the V1 message variant, its inline compute budget, and the Jetstreamer replay path that used to fail on it. spl-token-2022 v11 brings the PermissionedBurn extension. DeactivatedStake rewards and exact commission basis points are forwarded from Agave 4.2. Requires Rust 1.93+. 18/19 crates published, jetstream-source follows once upstream Jetstreamer ships an Agave 4.x release. github.com/solana-rpc/shipst…

Shipstern 0.9.0 is out. Live filter updates on the Yellowstone gRPC source. Take a RuntimeHandle, patch the filter set with update_filters, the subscription is replaced mid-stream. No reconnect. Also: Transaction V1 (SIMD-0385) support with the inline compute budget on InstructionShared, Prefilter now covers the full Yellowstone subscription surface (memcmp, datasize, lamports, data slices, accounts_exclude, vote, interslot_updates), DISCRIMINATOR constants on generated types, and CPI event envelopes read straight from the IDL. Breaking if you match exhaustively on PrefilterError or build prefilters with struct literals. Builder users unaffected. github.com/solana-rpc/shipst…

Steal from the poor, give to the rich. Really living up to the Robinhood name. Oh wait… that’s not how the story goes.

Smells like GUM.

I'll share more context on this exciting revelation this weekend, but in the meantime, all you devs using Yellowstone Vixen should take note.

The Portfolio V2 API is powered by an on-chain data layer we've built at Jupiter over the last 6 months. Portfolio is the largest product we've shipped on it, but not the first. It already tracks historical account state for Jupiter Lend, powers our mobile notifications, and gives our business analytics real visibility. At its core is Yellowstone Vixen, a Solana data framework I started while working with @triton_one and was lucky enough to keep developing at @JupiterExchange alongside a new set of talented engineers (@KinoDataEnjoyor , @TheOnlyOrex). Vixen turns raw on-chain events into structured data. Sources are pluggable, so Dragon's Mouth gRPC, RPC, and snapshots all normalize through one parser and handler pipeline. We write the decoding logic once. On top of that, our data layer maintains a program registry that tracks IDL revisions, and handles consistency, ordering, and persistence. One foundation, many products. Today it tracks 75+ protocols and we're adding more every day. We can gain visibility into any program on Solana as soon as it ships or updates. In the coming days Yellowstone Vixen will be renamed Shipstern and join the Solana RPC GitHub organization, alongside Cloudbreak, a Postgres backed RPC for getProgramAccounts, and Superbank, Solana ledger data in ClickHouse served over JSON-RPC. It continues Jupiter's commitment to making Solana more accessible. github.com/rpcpool/yellowsto…

At @JupiterExchange we built and operate our own transaction-sending network, so your trades go straight from us to the leader. We continually benchmark it against the top transaction-sending services to ensure your trades are not only safe but also fast. The result: the lowest sandwich rate of any trading venue.

Yellowstone Vixen v0.7.0 is out 🚀 This release is all about making production indexing more reliable while improving data completeness. Highlights: • Jetstreamer upgraded to v0.5 Block rewards now forwarded Block entries included Built-in stats tracking Graceful shutdown support • Yellowstone gRPC now auto-reconnects by default with replay-aware recovery (when supported by the server), making transient outages much less painful. • Block coordinator is significantly more resilient: Better historical backfill Correct skipped-slot handling Handles late arriving records • Runtime rewritten with a native worker pool for bounded concurrency and much cleaner shutdown semantics. • Proc macro migrated to codama-rs events, bringing numerous parser fixes, SPL Governance support, improved Kafka error reporting, and more robust IDL generation. • New downstream APIs: InstructionUpdate::direct_log_messages() Flat instruction indexes • Added pToken instruction support. There are a few breaking changes for projects constructing config structs directly (JetstreamSourceConfig and YellowstoneGrpcConfig), but existing config files continue to work thanks to serde defaults. Thanks to everyone who contributed! Looking forward to seeing what the community builds with it. github.com/rpcpool/yellowsto…

This would not happen on @solana and wire time measured in seconds instead of days. Sending money with traditional banking is so frustrating yet is a basic banking primitive. The change is inevitable.

Had to make @JupiterExchange Ron and claimed Harry for @triton_one 😜

Thrilled to represent @JupiterExchange in the Solana RPC Working Group. Even more excited to see Cloudbreak released, which brings to life early prototypes and design patterns I developed while contracting with @triton_one. My old team and I are immortalized in the authors list: github.com/solana-rpc/cloudb…

Just locked a 5-leg World Cup challenge on @jup_predict. jup.ag/prediction/world-cup

Finishing up my game and using GPT-5.5 for ability icons. The icon on the far right was generated by GPT Image 2 as a reference. The icons on the left were hand-drawn with a JavaScript script written by GPT-5.5. Hilarious. Building @FAANGorigins on nights and weekends.

Revision we got our auth check P95 to 2ms.