Skip to main content
POST
/
sdk
/
{environmentId}
/
waas
/
aleo
/
prover
/
{network}
/
prove
/
encrypted
Submit a libsodium-encrypted Provable proving request through redcoast
curl --request POST \
  --url https://app.dynamicauth.com/api/v0/sdk/{environmentId}/waas/aleo/prover/{network}/prove/encrypted \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "ciphertext": "<string>",
  "key_id": "<string>"
}
'
{}

Documentation Index

Fetch the complete documentation index at: https://www.dynamic.xyz/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
environmentId
string
required

ID of the environment

Required string length: 36
Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

​
network
enum<string>
required

Aleo network whose prover to forward to.

Available options:
testnet,
mainnet

Body

application/json

Request body for POST /waas/aleo/prover/{network}/prove/encrypted. Iframe sends the libsodium crypto_box_seal ciphertext of the Provable SDK's ProvingRequest, paired with the key_id returned by /pubkey. Redcoast forwards verbatim; the plaintext never leaves the iframe.

​
ciphertext
string
required

Base64-encoded libsodium-sealed proving request.

​
key_id
string
required

The key_id from the matching /pubkey response.

Response

Upstream proving response

Response body for POST /waas/aleo/prover/{network}/prove/encrypted. Mirrors the Provable response shape (transaction id, proof bytes, broadcast status, etc.). We don't pin a strict schema because Provable can evolve its response and we want forward compatibility.