A critical vulnerability in traditional approval systems is parameter tampering or scope drift:
A human operator reviews and approves: update_account(account_id="acc_99", role="viewer")
An adversarial agent modifies the payload before retry: update_account(account_id="acc_01", role="admin")
Dmint eliminates this attack vector through Exact Request Binding.
An approval in Dmint is never a blanket permission. It is a cryptographic assertion bound strictly to the byte-for-byte canonical hash of one exact request.
The Request Binding Envelope
Before any approval record is created or evaluated, Dmint constructs an immutable request binding envelope:
In standard JSON implementations, semantically identical payloads produce distinct raw string representations:
12345// Representation A:{"account_id":"acc_100","amount":500.0}// Representation B (different key order, added spaces, different float formatting):{"amount":500,"account_id":"acc_100"}
If hashed naively as raw text, Representation A and Representation B produce completely different SHA-256 hashes, causing false-positive approval mismatches or allowing hash-malleability exploits.
The prefix b"dmint/request-fingerprint/v2\x00" prevents cross-protocol signature forgery. A hash computed for a policy digest (b"dmint/policy-digest/v1\x00") or row integrity check (b"dmint/approval-record-integrity/v2\x00") can never collide with or be substituted for a request fingerprint.