Mobile Device Attestation is Aurigraph's defense-in-depth layer for verifying that on-chain transactions originate from a genuine, uncompromised mobile device — not an emulator, rooted phone, or replay-attack tool. The system parses verdicts from Google Play Integrity (Android) and Apple DeviceCheck / App Attest (iOS), wraps each verdict in an ML-DSA-87 post-quantum signature, and records the attestation as a verifiable on-chain event.
A Battua wallet on a rooted Android, or a tokenization SDK running inside an iOS jailbreak, can sign valid transactions that nonetheless represent compromised state. Without attestation, the blockchain has no way to distinguish "good device, good user" from "tampered device, attacker user." Mobile Device Attestation closes that gap.
Device → request signed nonce from V12 → call Play Integrity / App Attest with nonce → receive JWT verdict (signed by Google/Apple) → submit verdict to V12 attestation endpoint V12 → verify JWT signature against Google/Apple public keys → check nonce matches issued challenge (replay defense) → parse verdict fields (BASIC/STRONG, app integrity, account integrity) → enforce acceptance policy (e.g. reject EMULATOR, require MEETS_STRONG_INTEGRITY) → emit DMRV event signed with ML-DSA-87 → store hash-not-content (GDPR safety)
Operators configure acceptance policies per wallet tier:
Failed attestation does not silently reject — it returns a structured error code (ATTESTATION_FAIL_<reason>) so wallets can guide users to remediation.
ATTESTATION_FAIL_<reason>
Each attestation request includes a server-issued nonce (v12_attest_nonce) with a 90-second TTL. The V12 attestation table stores (nonce, device_id, used_at). Re-submitting the same nonce within the TTL window returns 409 NONCE_REPLAYED and emits an alert event for the audit log.
v12_attest_nonce
(nonce, device_id, used_at)
409 NONCE_REPLAYED
The attestation pipeline never stores the raw JWT verdict on-chain. Only:
sha256(verdict_jwt)
verdict_outcome
device_id
timestamp
attestation_id
This passes GDPR Article 25 (data minimization) and Article 32 (security of processing) — auditors can verify a verdict happened without revealing what the verdict said about the user's device fingerprint.
✅ Production-ready. Phase 6 release of V12.1.52. JWT verdict parser + acceptance policy enforcement both live. Integrated with Battua, RWAT, and Mobile Nodes. Replay-detection covered by 47 GREEN tests.
Explore: About · Products · Features · Whitepapers · Sustainability · Tokenized carbon credits · Real-world asset tokenization · SDK · Blog · Plain-text site index · Sitemap · Contact: contact@aurigraph.io