Ship checklist
Pre-launch verification for AICW-powered apps
Before shipping your AICW-powered app, verify each item in this checklist. Items marked critical can result in fund loss or security vulnerabilities if missed.
Security (critical)
| Check | Why |
|---|
Agent identity is the solana_pubkey + mpc_wallet_id pair from one issuance; AICW PDA existence checked on onboarding | Mismatched pairs fail signing; random keys must not pose as agents |
| MPC_WALLET_ID is never in client-side code, URLs, or logs | The Bridge is public and signs for whoever presents the ID — it is a bearer secret |
aiAgentPubkey sent on every Bridge sign call | Lets the Bridge refuse to sign for a dead agent (403) |
Your <app>_skill.md is published and linked | Without it agents cannot discover how to use your app |
| Environment variables are not committed to git | Check .gitignore includes .env files |
| HTTPS used for all Bridge communication | Prevents man-in-the-middle attacks on signing requests |
| Transfer amount caps enforced server-side | Client-side validation alone can be bypassed |
Operations
| Check | Why |
|---|
| Heartbeat scheduler running and monitored | Missed heartbeat → eventual will execution |
| Agent pubkey has fee buffer | Zero SOL = all operations fail silently |
| Bridge health monitoring in place | Bridge down = no signing possible |
| Will activated with correct beneficiaries | Inactive will means no recovery if agent dies |
| Error alerting configured | Silent failures can cascade |
Testing
| Check | Why |
|---|
| All flows tested on devnet with real transactions | Simulation differs from actual on-chain behavior |
| Tested heartbeat recovery after simulated downtime | Verifies agent can resume after restart |
| Tested transfer failure cases (insufficient balance, dead wallet) | Error handling must work in production |
| Tested will execution in controlled scenario | Understand what happens when agent actually dies |
Documentation
- Document which network and program ID your app uses
- Provide clear error messages for AICW-specific failures
- Link to aicw.ai/docs for protocol reference
- Document your app's transfer limits and business rules
- Include recovery procedures for common failure scenarios