Contributor Compliance & KYC Policy
The operational rules governing contributor identity verification, fraud prevention, audit logging, and payout eligibility across the Mesh Native Exchange.
Why KYC is required
Every contributor must complete identity verification before DIU earnings become eligible for settlement to USD. This is a policy and architectural requirement — not optional. Unverified accounts are blocked from payouts entirely.
How identity is protected
Identity data is encrypted end-to-end and used only for verification. DOSFI retains only the minimum verification metadata required for compliance and payout eligibility. Original identity documents are retained only as required by the verification provider and applicable law. Audit logs store only verification outcomes and timestamps — never raw identity documents or biometric data.
Fraud and Sybil prevention
The verification system detects duplicate identity documents across accounts (fraud) and duplicate biometric captures across accounts (Sybil attacks). Each check uses SHA-256 hashing to compare identity and biometric data without storing the raw data.
Audit logging behavior
Every verification lifecycle event is recorded in the Compliance Audit Log. Logs contain only metadata — event type, actor reference, timestamp, and outcome. No raw PII, no document images, no biometric data is ever written to the audit trail.
Payout rules
DIU → USD payouts are gated by verification status. Only contributors with verification_status = 'verified' can request payouts. Pending, failed, and unverified accounts are blocked with clear messaging and a link to complete verification.
No IP leakage & data ephemerality
MeshNativeExchange operates under strict no-IP-leakage and no sensitive information exposure rules. Contributor IP addresses, device identifiers, node metadata, and routing information are never collected, stored, displayed, or transmitted. All contributor data is treated as confidential and ephemeral, and all interactions are isolated to the current session.
No IP Leakage · No Sensitive Information Exposure
MeshNativeExchange operates under strict no-IP-leakage and no sensitive information exposure rules. All contributor data is treated as confidential and ephemeral.
Contributor IP addresses are never collected, stored, displayed, or transmitted.
Device fingerprints, hardware IDs, and device metadata are never collected or stored.
Node metadata and routing information are never embedded in payout, verification, or dashboard output.
Contributor interactions are isolated to the current session. Data is discarded after verification unless legal retention is required.
Identity details beyond what the contributor explicitly provides during KYC are never inferred or revealed.
The verification workflow is designed to support GDPR data handling requirements. The SOC 2 Type II audit is a planned independent audit milestone and has not yet been completed. HIPAA-related controls apply when supporting regulated healthcare workloads.
DOSFI Sovereignty — Closed Core / Open Surface
DOSFI Core is sovereign and closed. All educational content on this page is generated exclusively from open-surface materials — SDKs, ABIs, documentation, tutorials, examples, and conceptual explanations. Internal details of the DOSFI Runtime, Scheduler, Router, Readiness Engine, Privacy Model, Power/Thermal Model, Vital internals, DIU internals, MNE internals, and Mesh-Native App runtime internals are not revealed, described, or inferred.
No proprietary algorithms, system code, or architectural diagrams capable of enabling replication of the DOSFI Core are published. When internal logic is referenced, only high-level conceptual explanations are provided. DOSFI's sovereignty, mission-lock, and non-replicable architecture are preserved at all times.
Ready to verify?
Complete your KYC verification to unlock DIU → USD payouts and earn the Verified Contributor badge.
Start verification