FREQUENTLY ASKED QUESTIONS

KryptoOS is sovereign identity infrastructure for the Empoorio ecosystem — decentralized identifiers (did:emp), verifiable credentials, and cryptography anchored on EmpoorioChain. You control your keys; issuers cannot take them back.

Traditional logins assign identifiers owned by the platform. KryptoOS issues DIDs you hold locally. Verifiers check cryptographic proofs without storing your raw identity data in a central database.

Empoorio is the ecosystem foundation. KryptoOS is the shared trust layer across Eoonia Wallet, Ouranoos Cloud, EmpoorioChain, and partner integrations — one protocol, many products.

Core protocol libraries and SDKs are published on GitHub. Production deployments follow W3C DID Core 1.0 and VC Data Model 2.0 with public changelogs and integration guides.

Julio Javier (Founder & CEO), Freddy Machado (CTO), Óscar Villamizar (CSO), and Germán (CMO) lead the executive team. See the Core Team page for all 20 builders and advisors.

Public materials cover DracmaS (DMS) utility and partnership opportunities. Equity and private terms are handled through the Empoorio investor portal.

Annual and quarterly filings are listed on the Investors Financials page. Audited PDFs are available to qualified investors via Empoorio.org.

Sign up on the Investors hub with your email and alert preferences. Press releases and milestones are also published on the Updates page.

Start with the SDK registry and getting started docs, or reach Empoorio partnerships for enterprise issuer and verifier onboarding.

did:emp — W3C-compliant decentralized identifiers registered on EmpoorioChain with versioned documents, key rotation, and public resolution under 200ms target.

W3C Verifiable Credentials Data Model 2.0, Status List 2021 revocation, OIDC4VCI issuance, and OIDC4VP presentation flows across TypeScript, Rust, Python, and Dart SDKs.

Credentials live on the holder's device or chosen encrypted storage. EmpoorioChain stores DIDs, public keys, and hashes — never raw PII.

Follow the getting started guide, download SDKs from the registry, and use the public RPC and EmpooScan explorer for testnet anchoring.

Holders present only the claims a verifier needs — prove age without sharing a full birth date, or prove KYC level without exporting document images.

Rotate keys in your DID document and revoke affected credentials via Status List 2021. Issuers cannot impersonate you without your private keys.

The KryptoOS Privacy Policy is at /docs/resources/privacy — it covers the KryptoOS website, SDKs, and protocol data practices only.

Review partner categories on the Suppliers page, confirm you meet our interoperability and privacy requirements, then submit the supplier inquiry form. The partnerships team responds within 5–10 business days.

Production partners must align with W3C DID Core 1.0, VC Data Model 2.0, and fail-closed verification. Raw PII must not be exported to third-party databases.

Yes. Empoorio engages independent auditors for protocol review before mainnet milestones. Public audit relationships are listed on the Partners page when agreements are announced.

Enterprise integrators can run issuer services with KryptoOS SDKs and anchor DIDs on EmpoorioChain. Onboarding includes schema review and security assessment.