Horizen Vela System info

No body. Send Accept: application/json for a machine-readable view.

JSON body with an EIP-712 RequestAuthorization signed by the user. The nonce is read from facilitatorNonces[sender] on-chain by the client before signing (no nonce endpoint).

protocolVersion

Protocol version (currently 0).

applicationId

Target application ID

sender

User address that signed the request.

requestType

1 = PROCESS, 3 = ASSOCIATEKEY (only these two are accepted).

payload

Hex bytes. ASSOCIATEKEY: raw 133-byte P-521 pubkey (0x04 || x || y). PROCESS: ECIES-encrypted PayloadInstructions (app specific format).

tokenAddress

ERC-20 address, or address(0) when assetAmount = 0.

assetAmount

Token amount in base units, as a string.

deadline

Unix timestamp after which the signature is rejected.

requestSignature

EIP-712 RequestAuthorization signature (hex).

depositPermit

EIP-2612 permit { v, r, s } when assetAmount > 0, otherwise null.

{
  "sender": "0xUSER",
  "protocolVersion": 0,
  "applicationId": 1,
  "requestType": 3,
  "payload": "0x04...133bytes",
  "tokenAddress": "0x0000000000000000000000000000000000000000",
  "assetAmount": "0",
  "deadline": "1711929600",
  "requestSignature": "0x...",
  "depositPermit": null
}
// → 200 { "requestId": "0x..." }

JSON body. Anyone can call it — funds are always sent to payee, so there is no auth risk. If nothing is pending, it is a no-op returning amount "0".

tokenAddress

ERC-20 address, or address(0) for ETH.

payee

Address that will receive the pending balance.

{
  "tokenAddress": "0xTOKEN",
  "payee": "0xPAYEE"
}
// → 200 { "amount": "1000000", "transaction": "0x..." }

No body.

// → 200
{ "schemes": [ { "scheme": "private-vela-fixed", "network": "eip155:<chainId>" } ] }

x402 JSON body. Checks the EIP-712 signature, deadline, nonce and permit off-chain — no transaction is sent.

paymentPayload

x402 payload: { x402Version, accepted, payload: { sender, requestSignature, depositPermit, requestAuthorization, payload } }.

paymentRequirements

x402 requirements: { scheme, network, asset, amount, payTo, maxTimeoutSeconds, extra: { invoiceId } }.

{ "paymentPayload": { ... }, "paymentRequirements": { ... } }
// → 200 { "isValid": true }  |  { "isValid": false, "invalidReason": "..." }

Same body shape as /verify. Calls ProcessorEndpoint.submitRequestFor(), then polls for the matching AppEvent (eventSubType = keccak256(len(invoiceId)||invoiceId||sender||token||amount||recipient)). Tunable via APP_EVENT_POLL_INTERVAL_MS / APP_EVENT_POLL_TIMEOUT_MS.

paymentPayload

Same as /verify.

paymentRequirements

Same as /verify.

{ "paymentPayload": { ... }, "paymentRequirements": { ... } }
// → 200 (confirmed) { "success": true, "transaction": "0x...", "extensions": { "requestId": "0x...", "eventSubType": "0x..." } }
// → 200 (timeout)   { "success": false, "errorReason": "tee_processing_timeout", "extensions": { "requestId": "0x..." } }