Record a submitted on-chain transaction
Records the on-chain submission against a pending, unexpired intent and marks it executed (single-use replay protection). Submission itself happens through the SDK/adapter.
Records the on-chain submission against a pending, unexpired intent and marks it executed (single-use replay protection). Submission itself happens through the SDK/adapter.
Authorization
cookieAuth JWT access token set by /auth/google/callback or /auth/refresh
In: cookie
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/wallet/transactions/submit" \ -H "Content-Type: application/json" \ -d '{ "intentId": "9b966aba-7d18-4a93-b6a8-43845b096776", "txHash": "string" }'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "intentId": "9b966aba-7d18-4a93-b6a8-43845b096776", "chain": "string", "network": "string", "txHash": "string", "status": "prepared", "createdAt": "2019-08-24T14:15:22Z"}Rotate the on-chain authority to a registered replacement credential POST
Credential-lifecycle rotation: register the replacement credential first (approval flow), then the current key authorizes on-chain `update_authority` here. The old credential is revoked in DB only after the chain confirms the new authority.
Create the wallet POST
Creates the wallet for the authenticated PID with a user-supplied Solana address. The chain is fixed to `solana` for V3 (single-chain MVP). A PID has at most one wallet: creating again returns the existing wallet. Custody is record-only — Peridot does not generate, hold, or return any key material.