A reusable, privacy-first alternative to OTP: verify once with a trusted issuer, then re-prove it everywhere — without sharing raw personal data.
Verify once, reuse everywhere. OIVP issues a verifiable credential (VC) for your phone, email, or full KYC—stored locally in your wallet and accepted by any app with the OIVP SDK.
Complete KYC or verify phone/email with a trusted issuer (bank, telco, eID, or exchange). They issue your OIVP Verifiable Credential (VC).
Your VC is stored locally in the OIVP Wallet. Only you control it. A hash/commitment is anchored on Base L2 to prevent tampering.
When an app needs trust (age, phone ownership, or KYC status), tap “Verify with OIVP”. No more OTPs or document uploads.
See exactly what’s requested (e.g., “KYC verified” or “Over 18”) and approve. OIVP shares only a cryptographic proof—never your raw PII.
The app validates the proof via the OIVP SDK and Base L2 commitment. You’re granted access with a timestamped, consent-logged result—privacy intact.
The stack is designed with PII abstraction, security, and scalability in mind. Hover over the layers to see their function.
Decentralized registry for issuer identities and credential revocation hashes. Zero raw PII ever touches the chain.
Defines the W3C VC data models, proof mechanisms (ZKPs), and the standard APIs for minting and verifying credentials.
The secure gateway for banks/telcos to connect their high-trust KYC data to the protocol to issue VCs.
Client-side tools for Verifier Apps to request proofs, and for Users to manage their private credentials.
We are currently raising our Pre-Seed round to fund this 18-24 month plan. Click on any date to see the details.
Design, counsel alignment (ADGM), pilot scoping, team expansion.
Status: Pre-Seed Round open.
Issuer Registry, Credential Registry, basic SDK flows, and non-custodial wallet prototype.
Fintech/telco integrations, KPI dashboards, revocation tests, and initial partner feedback loop.
Full security audits, bug bounties, public developer documentation, and DevRel program kickoff.
Issuer staking, tokenized incentives, transition to community governance, and multi-region rollout.
We are raising AED 1.2M via a SAFE instrument to secure a runway through the initial product launch and our first pilots (18-24 months).
Primary instrument is a Simple Agreement for Future Equity (SAFE) to accelerate the initial build phase.
The protocol is secured and governed by the OIVP token, which creates a durable, aligned incentive layer for all network participants.
Verifier Apps pay transaction fees to the network to process proofs. This is the primary revenue stream.
Issuers must stake tokens to gain reputation and face slashing risk for malicious or fraudulent activity.
Token holders vote on protocol upgrades, fee structures, and the addition/removal of base-layer issuers.
Emissions used to reward developers for integrating the SDK and contributing to core open-source components.
Click any segment of the allocation bar below to see details about its purpose.
Details about the percentage and its long-term use in the protocol will appear here.
Short answers to common questions about the protocol, tokenomics, and security.
Pilots, co-development, or strategic investment.