Skip to main content
Every signed action on Intention carries a nonce. The nonce protects against replay attacks, allows clients to control ordering of their own actions, and lets the protocol deduplicate retransmitted requests. This page will document the nonce scheme: format, allocation, validation rules, and how clients should manage nonces under concurrency.
Status: not yet published. The nonce scheme will be finalized alongside the first stable signing specification. Treat the descriptions below as planning documentation.

​
What this page will contain

  • Format. The structure of a nonce field — monotonic counter, time-based, or session-scoped — and the validation window the protocol enforces.
  • Allocation. How clients should allocate nonces under concurrency, including ordering guarantees relative to transaction sequencing.
  • Replay protection. What the protocol guarantees about a duplicate-nonce submission and how to retry safely after a network error.
  • Session credentials. How nonces interact with scoped session signing, cross-referenced with signing.
  • Errors. Error codes returned when a nonce is invalid, expired, or duplicated.
For early integration questions, email contact@intention.xyz.