Ouranoos Integration
Ouranoos Cloud needs a way to recognize users and provider devices without collecting raw PII. Aephoron's embedded Eoonia Wallet is the natural login and credential-holder surface for that — today via wallet-based (SIWE) auth, with locally stored did:emp credentials as the on-chain piece matures.
Credential Types (planned schemas)
OuranoosUserCredential: proves a user has an ecosystem identity commitment.OuranoosProviderDeviceCredential: proves a provider controls a device class and declared capacity range.
These schemas are defined; full on-chain issuance and verification depend on the same DID registration and VC verification work tracked for did:emp across the ecosystem (see Web3 & Wallet for current status).
Provider Registration Flow (target design)
- Provider device generates or receives a device possession proof.
- A credential describing the device is stored in the user's wallet.
- Ouranoos verifies the credential locally.
- EmpoorioChain receives only commitments and public provider parameters needed for market/proof logic.
- PII and raw device identifiers stay out of public transaction metadata.
Privacy Rule
Provider reputation should attach to commitments and revocation status, not names, addresses, raw serial numbers, or phone identifiers.