FREQUENTLY ASKED QUESTIONS

Aephoron is the Empoorio ecosystem Web3-native browser — a Rust engine from network to GPU, with Kinetoor (rendering) and BlepoOS (search) as its core pillars. Not Chromium, not Electron.

Aephoron is built on a Servo fork in Rust with compiler-guaranteed memory safety. Web3, wallet, shields, and on-device AI are native — not extensions injected into Chromium.

Aephoron (browser shell), Kinetoor (rendering engine), and BlepoOS (search). All three live in the projects/Aephoron_browser_browser monorepo under MPL-2.0.

Yes — MPL-2.0 Servo fork. Build with mach, contribute via GitHub, and run WPT conformance suites alongside aephoron-desktop.

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.

This is ecosystem token information, not traditional equity stock. DracmaS (DMS) utility and sale terms are covered on the Stock Information page and Empoorio.org.

Aephoron and the Empoorio ecosystem are pre-revenue, in public testnet and token-sale phase — there are no audited financial statements to publish yet. Governance and token-economics documents are listed on the Investors Financials page.

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 getting started guide and Web3 integration docs, or reach Empoorio partnerships for dApp and browser integrations.

Kinetoor — a Servo fork with SpiderMonkey v140, WebRender GPU paint, and Hyper + Rustls networking. Multi-process Constellation coordinates WebViews.

Three layers: our own SearXNG clearnet node, an index of the Empoorio ecosystem (EmpooScan data plus a directed crawl of the ecosystem sites, Tantivy), and on-device Ailoos synthesis with citations (roadmap). Live at blepoos.aephoron.com, default engine of the omnibox.

The native Web3 API exposed to dApps — chain connection, DMS gas, and signing through the embedded Eoonia wallet without extension injection.

Clone projects/Aephoron_browser_browser, run ./mach build in aephoron-main, and launch aephoron-desktop. See the getting started guide for platform prerequisites.

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 Aephoron Privacy Policy is at /docs/resources/privacy — it covers the website, browser telemetry practices, and public documentation.

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 Aephoron SDKs and anchor DIDs on EmpoorioChain. Onboarding includes schema review and security assessment.