espi

Thank you @italoacasas for bringing us together. I’m excited to be contributing to RPC at @JupiterExchange.

@jords Journey before destination.

one dm can change your life bros press send and see what happens

@jords Accurate.

look mom im on tv

Revision we got our auth check P95 to 2ms.

The developer platform is real nice. Big.

@ujjwalgupta49 @JupDevRel @0xanmol Should I tell him Jupiter Compute Platform is built on top of AWS? Its really a CNFC technology chain so its cloud agnostic but its tough to compete with AWS.

@JupDevRel @0xanmol @espicodes friendship ended with aws, compute platform is my favorite now.

If you're building on Jupiter's APIs, this is the infrastructure serving your requests. The v2 → v3 API gateway migration led by @espicodes and infra team that now powers the Jupiter developer platform. Deep dive worth reading 👇

@defido @MikazukVII We were also getting charged up the a** for data transfer from CF to AWS. Cost isn't the primary focus but are looking to reduce hops between providers.

@espicodes @MikazukVII Nice. Just saw that you’re trying to increase size to lower AWS bill. Which makes sense also.

Cloudflare can handle routing, but it’s primarily designed for edge-level use cases. Workers require implementing routing logic in code, and while Cloudflare Load Balancing exists, it’s more limited in terms of advanced traffic policies and consistency with in-cluster routing. We use Envoy + Envoy Gateway because it provides a declarative way to manage routing (e.g. traffic splitting, retries, timeouts) and keeps the same model across all clusters and services.

@espicodes @MikazukVII You’re using cloudflare dns wouldn’t a worker or load balance rule be faster than using AWS on top to route traffic?

New lib dropped github.com/blueshift-gg/s… Run it as a service Fetch blockhashes with custom expiry so timeout strategy becomes super easy Check blockhash validity etc.. @blueshift

@0xAkvn @0xanmol This may evolve, but in general we’re consolidating infrastructure under AWS to strengthen our position in contract negotiations and secure better terms. Separately, since Cloudflare is our DNS provider, we are also leveraging their WAF capabilities.

@espicodes @0xanmol Cool! Wondering why you are using AWS WAF instead of Cloudflare WAF though

@Vinayapr23 @ordrtrade There is a solana rpc source too. Less polished but if you want to give it some love. PRs are welcomed.

@espicodes @ordrtrade Def a fan of yellowstone vixen We are exploring that also closely But yeah the gRPC source is an expensive option right now 😂 Lets see how things proceed

Working on the Indexer and matching engine for @ordrtrade Is writing an indexer trend over ?👀

@ClassicScuba @corbits_dev @solana @x402 No token left behind 🫡

@corbits_dev @solana @x402 Leave no token unturned

Guess we're shipping support for Token-2022 on @solana too. Big day for @x402! Shippers ship.

@corbits_dev @ClassicScuba @solana @x402 Just keep shipping 🛥️

Pleasure to share Jupiter's shift to platform first engineering.

@0xanmol @arifkazi_ @brianlong @mtndao @triton_one @solana @solana_devs @SolanaEvents @linuskendall @SteveCleanBrook @leafar_dev @JET_EUROPA_ It’s @brianlong man knows good tek. No surprise there. @JupiterExchange getting involved and driving the next release of Yellowstone Vixen. Game changer.

@arifkazi_ @brianlong @mtndao @triton_one @solana @solana_devs @SolanaEvents @linuskendall @SteveCleanBrook @leafar_dev @JET_EUROPA_ @espicodes Vixen mentioned 👀

wrapped up a session w @brianlong at @mtndao  some points on solana infra: - apparently swqos is dead: major block builders (firedancer, jito bam, harmonic) don't support it. - rpc 2.0 kills the magical backend in web3. serious teams already run their own indexers; with 2.0, everyone should just index what they need. - no more accounts db in agave client (that's ibrl). firedancer won't ship with one. - rpc 2.0 working group is listening to validators & app devs for better devex. this openness to feedback sets solana's builder culture apart

Today, we’re opening early access to Galileo, our natural language interface, on jup.ag. This marks our first step toward making AI a core part of the Jupiter experience. Galileo introduces a high-intent, natural language layer across the full range of actions available on Jupiter today, from swaps and routing to data and advanced workflows, all expressed in plain English.

Excited to announce that at @anza_xyz we are cooking up a free, high speed archive of all txns + account updates since solana genesis! * unlimited free bandwidth (cloudflare R2) * stream sequentially at jetstreamer speeds * fully seekable on a per-slot basis more details soon!