Cryptocurrency & Crypto Payments Security
Irreversibility changes everything. In crypto payments, a single bad
transaction can settle in seconds with no clawback path. The goal of
this workflow is to stop high-blast-radius mistakes before signing,
then produce auditable triage when automation cannot prove safety.
What this workflow covers
- Wallet-op hardening for hot-wallet signing services.
- Address integrity controls to prevent substitution and poisoning.
- Key-material cleanup in code, logs, CI artifacts, and runbooks.
- Settlement policy checks before release and after chain events.
Eligibility profile
A finding is agent-eligible when all are true:
- The fix shape is bounded (policy/config, controlled code path, or deterministic runbook update).
- A signed transaction is not emitted directly by the agent.
- A dry-run or simulation path exists.
- Human approval remains mandatory for production key use.
Recipe catalog
Use the following prompt recipes for this workflow:
- Hot-wallet transaction policy enforcement
- Crypto payment address integrity checks
- Seed phrase and key-material purge
Guardrails
- Signer credentials are scoped to simulation-only in agent runs.
- Allowlists enforce destination, chain, token, amount, and cadence.
- Every fail-open branch is converted to fail-closed with triage.
- Incident evidence is written to immutable audit storage.
Not in scope
- Autonomous treasury strategy decisions.
- Trading or market-making actions.
- On-chain signing from unreviewed prompts.