Repository layout
Live protocol defaults
The official devnet USDC
token_id is resolved from the protocol TokenRegistry or from RYVO_PROTOCOL_DEVNET_USDC_TOKEN_ID. Do not hardcode demo token IDs in agent integrations.
CLI packages
MCP packages
Gateway MCP:ryvo://protocol/llm.txt. Like the protocol CLI, it is read + prepare only and never signs or submits transactions.
LLM text
Payment-channel guardrails
Gateway channel payments use signed cumulative commitments against locked channel collateral. For/v1/ryvo-channel/... routes, agents should:
- Open a channel to the gateway merchant participant.
- Lock official devnet USDC into that channel.
- Sign one cumulative commitment per request.
- Send
X-Ryvo-Request-IdandRYVO-COMMITMENTwith the gateway call.
Protocol caveats
- Participant withdrawals are instant on the live devnet deployment.
- Unilateral channel unlocks take 72 hours.
- Cooperative channel unlocks are immediate when both parties agree.
- Ryvo BLS is Ryvo-specific. It is not a generic IETF hash-to-curve BLS ciphersuite, so clients must use the shared Ryvo implementation and test vectors.
- BLS key rotation does not exist yet. If a BLS key is lost or compromised, the participant should migrate to a new participant identity for future BLS clearing.
