jup.sh 0.1.0-alpha.11 Draft Release Notes

Status: draft.

v0.1.0-alpha.11 is planned as the first transaction request runtime gate. It implements the Solana Pay-style endpoint shape from the skeleton without building or returning a transaction.

This is intentionally not payment execution support.

What This Draft Adds

• Transaction request metadata endpoint:
  • GET /api/transaction-requests/:intentId.
• Transaction request POST gate:
  • POST /api/transaction-requests/:intentId.
• POST validates the wallet account shape.
• POST refuses review-required intents before approval.
• POST refuses rejected intents.
• POST returns 501 transaction_not_implemented for approved intents because transaction construction is still out of scope.
• Server API smoke coverage for transaction request metadata, invalid account, review gating, and the explicit not-implemented response.

Runtime Shape

GET:

GET /api/transaction-requests/intent_xxx

Response:

{
  "label": "jup.sh",
  "icon": "https://www.jup.sh/favicon.svg"
}

POST:

POST /api/transaction-requests/intent_xxx
Content-Type: application/json

{
  "account": "11111111111111111111111111111111"
}

Current ready response:

{
  "error": "transaction_not_implemented",
  "message": "Transaction construction is not implemented in this alpha."
}

Safety Boundary

The endpoint only establishes the wallet-facing protocol boundary. It does not compose transactions, call Jupiter swap transaction APIs, sign, submit, confirm, or claim settlement.

Approved review state is necessary but not sufficient for a transaction. The next checkpoint must add transaction construction separately and keep it behind fresh quote, route, account, recipient, and slippage validation.

Current Boundary

The npm alpha package remains jup-sh@0.1.0-alpha.7 until a runtime release is prepared and published.

Verification

Run:

npm run release:check