Guarded transaction sending

Guarded sending is Pro and disabled until an administrator enables the site policy. It is available only for reviewed adapters, trusted contracts, callable schemas, exact capabilities, and supported networks.

Send lifecycle

1. Build and simulate an immutable intent.
2. Present the complete preview and warnings.
3. Obtain explicit visitor confirmation bound to that intent.
4. Recheck account, chain, capability, policy, expiry, and idempotency.
5. Ask the provider wallet to sign or send.
6. Monitor the submitted hash or signature to a bounded lifecycle result.

The wallet remains the final signing authority. Tools never requests or stores a seed phrase or private key.

Cancellation, rejection, account change, chain change, expiration, uncertain provider state, replacement, and possible reorganization must remain distinct outcomes. Never label an uncertain transaction successful merely because a provider request returned.