jup.sh 0.1.0-alpha.8 Draft Release Notes

Status: draft.

v0.1.0-alpha.8 is planned as a design checkpoint for the future transaction request boundary.

The main addition is a Transaction Request Skeleton:

intent -> policy -> quote -> review or ready_for_authorization
       -> future Solana Pay transaction request
       -> wallet signing boundary

This draft does not add transaction creation. It documents the next contract before implementation so the wallet-facing boundary stays explicit.

What This Draft Adds

• Transaction Request Skeleton design docs.
• Planned Solana Pay transaction request shape:
  • GET for wallet display metadata;
  • POST for signer account input and transaction response.
• Planned jup.sh endpoint shape:
  • GET /api/transaction-requests/:intentId;
  • POST /api/transaction-requests/:intentId.
• Future CLI JSON shape for a nested transactionRequest field.
• Safety rules for request tokens, review gating, replay prevention, and wallet authorization.
• README, npm README, and GitHub Pages docs navigation links for the skeleton.

Why This Matters

jup.sh is moving toward a wallet-facing authorization path, but the current alpha is still quote-only and review-only.

The skeleton keeps the product boundary clear:

• agents create payment intents;
• policy decides whether the intent can continue;
• Risk Review handles exceptions;
• a future transaction request endpoint may compose a transaction;
• the wallet remains the signing boundary.

Current Boundary

This draft is still a developer alpha design checkpoint. It does not change the runtime CLI behavior. The current published CLI still stops at local intent creation, policy decisioning, quote evidence, local persistence, and Risk Review handoff.

The npm alpha package remains jup-sh@0.1.0-alpha.7 until a runtime release is prepared. This draft can be merged as documentation without changing the published npx jup-sh@alpha behavior.

Not Included

• No wallet signing.
• No swap execution.
• No Solana Pay transaction request generation.
• No custody.
• No remote backend persistence.
• No authentication.
• No published SDK package.

Verification

Run the current project checks:

npm run check

For a full implementation release, continue to use:

npm run release:check

The transaction request skeleton is documentation-only and should not be treated as payment execution support.