The published implementation behind Jolt Guard: an on-chain program, instruction-building SDK, codec tests, protocol specification and deployment records.
This browser loads each complete published file from Joltwork’s own site. The Rust program parses the signed intent, validates accounts, invokes policy and route programs through CPI, reloads token balances, enforces postconditions and returns a settlement receipt. The SDK builds the matching instruction format; the tests exercise its codec.
You do not need to read Rust to understand what is being proven. Start with JOLT_GUARD.md for the execution contract, then open sdk/src/index.ts to see how an application builds the instruction. The Rust file is the final authority: it shows which accounts are trusted, which values are checked and which errors stop settlement.
The browser displays the same source snapshot published with this site rather than decorative snippets maintained separately for marketing. Readers can inspect complete files without being redirected to a third-party code host. Tests demonstrate deterministic encoding and account assembly, but they are not a substitute for an independent security review.
The interface formats and implementation are separated so wallets, routers, launchers and indexers can integrate only the layer they need.
Think of the repository as three layers. The specification names the promises. The SDK translates those promises into bytes and ordered accounts. The Solana program enforces them. CI then repeats the available tests whenever implementation files change. The table is a map of those layers, not a claim that every production dependency has already shipped.
| path | responsibility | consumed by | state |
|---|---|---|---|
| programs/jolt-guard | atomic route wrapper and settlement checks | Solana runtime | implemented |
| sdk/src | typed constraints, canonical encoding, account assembly, adapters and receipt decoding | wallets / apps | implemented |
| sdk/test | separate codec, instruction, Jupiter and receipt suites | CI | active |
| launch-client.ts | Pump create_v2 assembly, safety checks and confirmation | coin creators | implemented |
| JOLT_GUARD.md | JOLT V1, JHK1 and JRC1 interfaces | integrators | specified |
| automation workflows | repeatable Rust and SDK checks | contributors | active |
| docs | architecture, integration, security and operations runbooks | integrators / operators | maintained |
| scripts | site contract and deployed-byte verification | release engineering | active |
Source code proves which mechanism was implemented; the mainnet and devnet manifests publish executable Program IDs, ProgramData accounts and the reproducible SBF hash. They do not prove that every route adapter is free of adversarial edge cases, which still requires integration coverage and independent review.
The browser now connects Jupiter Swap API V2 raw instructions to the mainnet Jolt Guard wrapper and asks the user wallet to sign the resulting versioned transaction. Deployment, integration and audit remain separate evidence, so each is presented explicitly.
The mainnet and devnet programs are real and independently inspectable. Published manifests bind their identities to the same reproducible SBF digest; audit and production monitoring remain separate evidence.
Read the protocol architecture, then inspect the exact source file that enforces each invariant.