1. Pilot scope
Scoped before launchDefine the partner surface, approved chains, allowed assets, supported flow, user-facing copy, and production-review owner.
Pilot report template
After a demo or sandbox review, this report gives a buyer a clear summary of scope, route policy, wallet review, receipts, usage posture, limitations, and next steps.
It is deliberately conservative. It should help a partner decide whether to continue a controlled pilot without implying custody, financial advice, public launch approval, or performance claims.
Report identity
Define the partner surface, approved chains, allowed assets, supported flow, user-facing copy, and production-review owner.
Confirm allowed pairs, blocked assets, route behavior, fee disclosure posture, and any partner-specific limits before wallet prompts are enabled.
Confirm users review and sign in their own wallet, and that no server, operator, or platform wallet executes on the user’s behalf.
Confirm the pilot can produce a clean receipt or proof summary for successful, failed, rejected, and retryable flows.
Summarize safe usage records, proof requests, payment state, and invoice readiness without storing secrets or raw transactions.
Record whether the pilot should continue, pause, widen scope, or move into production review with explicit unresolved risks.
Report fields
These fields are intentionally buyer-safe. They avoid raw wallet addresses, raw transactions, API keys, private keys, secrets, and unsupported performance claims.
Decision block