aabc-tx-plan

To validate an on-chain transaction plan, you create a tx_plan JSON object that conforms to templates/tx-plan.schema.json, ensuring required fields like chain, network, operation_type, signer_mode, and transactions are present. The schema validates the structure and routes actions to the correct signer mode.

A tx_plan schema is a standardized JSON contract that defines on-chain actions for deploys, swaps, or LP operations across chains like bsc and solana. You need it when building automations that emit transactions for backend execution without exposing private keys, ensuring consistent routing to the appropriate signer mode.

Yes, the tx_plan validation schema supports multiple chains including bsc and solana through a single unified schema. It handles varying transaction details and signer modes across these multichain workflows, ensuring required fields are present and conform to the defined templates/tx-plan.schema.json structure.

To structure a transaction plan payload, include the signer_mode field with values like prepare_only, connected_wallet, or session_wallet. The tx_plan JSON object must also contain required fields such as chain, network, operation_type, and transactions, plus optional metadata like risk, approval, and artifactHints.

In a multichain tx_plan JSON object, you can include optional metadata fields such as risk, approval, and artifactHints. These fields provide additional context for on-chain actions like deploys or swaps, supplementing the required fields chain, network, operation_type, signer_mode, and transactions within the templates/tx-plan.schema.json.

An on-chain transaction plan fails validation if the tx_plan JSON object does not conform to templates/tx-plan.schema.json, typically because required fields like chain, network, operation_type, signer_mode, or transactions are missing or incorrectly specified. Ensure the signer_mode is set to connected_wallet and all mandatory fields are present.