Non-custodial security model

txcast is a coordinator, not a custodian. It never needs your private key or seed phrase.

What txcast does

• saves reusable workflow intent;
• renders exact transaction targets, values, and calldata;
• checks definitions, current permissions, account grants, and lifecycle state;
• prepares Safe typed data or EOA transaction requests;
• accepts externally produced signatures or transaction hashes; and
• verifies Safe and onchain outcomes before advancing dependent work.

What your wallet or Safe does

• displays the final signing request;
• protects private keys;
• signs and broadcasts transactions; and
• enforces Safe owners, threshold, and nonce rules.

Danger

Never paste a seed phrase, private key, bearer credential, or raw signature into txcast support, a workflow description, an AI prompt, or an audit note.

Review before confirmation

Before approving any wallet prompt, verify:

1. the connected chain and account;
2. every destination address;
3. native-token value and token amounts;
4. decoded function and arguments;
5. the Safe nonce and proposal hash, when applicable; and
6. whether the action is expected at this point in the run.

AI-agent confirmation prompts improve usability but are not an authorization boundary. Credential scopes, controlled-account grants, live role checks, cryptographic verification, and wallet confirmation are the enforced boundaries.

If something looks wrong

Do not sign. Close the wallet prompt, cancel the run if possible, and start a corrected run. A cancellation cannot reverse a transaction that has already been broadcast.

For a compromised agent credential, revoke it under Organisation settings → Agent access. For a compromised wallet, follow the wallet or Safe provider’s recovery procedure immediately.