sap_perpspad_build_escrow_launch

ai.oobeprotocol.sap.mcp/sap-mcp · Verify this server

Build an escrow-backed PerpsPad launch (creator-split Option B): derives the trustless escrow PDA from the NEW token mint, swaps the launch creatorAddress to that PDA, and returns the unsigned config + pool + initialize_escrow transactions. The hourly creator_payout then lands on the escrow PDA, which hard-splits 70% to the agent wallet / 30% to the OOBE treasury on-chain — non-custodial, permissionless. The mint keypair is generated by the CALLER (agent flow) and passed as mintKeypairSecret (64-byte array); the config tx materializes that exact mint. Agent wallet (70% destination) is stored immutably. Sign and send: initialize_escrow FIRST (agent wallet signs), then config, then pool. BUILDER tier. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.