Ecosystem Synced·11 Articles7 Rules5 Actions5 Continuity Plans0 Supra-Signals
Contributor Compliance

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.

Only verified contributors are eligible to earn and settle DIU to USD
One verified human per contributor account — no exceptions
Designed to support GDPR data handling; SOC 2 Type II audit is a planned independent audit milestone and has not yet been completed; HIPAA-related controls apply to regulated healthcare workloads
Protects the settlement layer from fraud and abuse

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.

Encrypted at rest and in transit throughout the verification flow
No raw PII in audit logs — only outcomes and timestamps
Identity data is used solely for verification, fraud prevention, and payout eligibility
DOSFI retains only minimum verification metadata; original documents retained per provider policy and applicable law

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.

Duplicate identity document detection — same ID on multiple accounts is blocked
Duplicate biometric detection — same face on multiple accounts is blocked (Sybil)
SHA-256 hashing enables comparison without storing raw identity data
Failed liveness checks flag photo, video, or digital replica attempts

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.

Verification submissions, approvals, and rejections are all logged
Fraud and Sybil attempts are logged as critical policy violations
Logs are available to admins for audit readiness and regulatory review
No raw PII is stored in audit logs — only event metadata and timestamps

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.

Verified contributors can request DIU → USD payouts
Pending contributors are blocked until verification is complete
Failed contributors must resubmit with correct information
Unverified contributors are prompted to start verification before any payout

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 contributor IP addresses, device identifiers, or routing information collected or stored
No node metadata or routing information embedded in payout, verification, or dashboard output
No identity details inferred or revealed beyond what the contributor explicitly provides during KYC
All contributor interactions are session-isolated and governed by controls designed to support SOC 2, HIPAA, and GDPR

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.

No IP addresses

Contributor IP addresses are never collected, stored, displayed, or transmitted.

No device identifiers

Device fingerprints, hardware IDs, and device metadata are never collected or stored.

No node metadata exposure

Node metadata and routing information are never embedded in payout, verification, or dashboard output.

Ephemeral by default

Contributor interactions are isolated to the current session. Data is discarded after verification unless legal retention is required.

No identity inference

Identity details beyond what the contributor explicitly provides during KYC are never inferred or revealed.

Designed to support SOC 2 · HIPAA · GDPR

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