Blockchain & Consensus•Sovereign Ledger Active

Client Retry & Idempotency Contract

Defining client retry semantics, client-generated idempotency keys, and transaction deduplication.

To prevent duplicate submissions in high-throughput B2B environments, TrustedTrucks establishes a strict idempotency contract between client applications and the KLS Application Gateway.

Contract Rules

Idempotency Keys: All write API endpoints require a X-Idempotency-Key UUID header.
Storage Window: Idempotency keys are cached in Redis for 24 hours.
Deduplication: If a second request arrives with the same key while the first is processing, the gateway returns a 409 Conflict or locks until completion.
Safe Retries: Clients can safely retry network timeouts using the identical idempotency key without risking duplicate RFQs or duplicate invoice registrations.

Ecosystem Progression

Follow the standardized operational sequence of stages.

Proceed to Next Stage→

Related Specifications

RAFT Transaction Reconciliation Engine Transactional Outbox & Projection Delivery Deterministic Transaction Execution Fabric

Normative Precedence NoticeThis specification document is a binding part of Release Bundle v7.0. In case of operational or discrepancies, the Integration Yellow Paper TT-ARCH-REL-001 takes precedence.