Webhook and receipt-export boundary
This documentation does not currently publish a production webhook-subscription, receipt-export, or signed-payload outbox contract. Names found in a local MCP source tree—such as connector, receipt, or outbox prototypes—do not establish a hosted service, stable schema, authentication guarantee, delivery SLA, or readiness for real funds.
Do not register production endpoints or place API secrets into prototype tools. Do not let a webhook initiate signing, withdrawal, agent-commerce, booking, payment, or escrow actions. The public network is a value-less, resettable testnet.
Future release requirements
Section titled “Future release requirements”A supported eventing release must publish exact schemas and versioning, authentication and secret-rotation rules, replay and deduplication behavior, retry limits, delivery and retention semantics, source authenticity, incident procedures, privacy boundaries, and end-to-end conformance tests. Consumers must still reconcile against independently verified chain state; a webhook is a notification, not finality evidence.
Safe work today
Section titled “Safe work today”Use the verified read-only RPC probes for identity and health checks. Keep exchange custody, withdrawal automation, and economic actions disabled until a separately reviewed production release exists.