EVDI (End-to-End Verifiable Data Infrastructure) is Empeiria's own platform that handles the entire lifecycle of Verifiable Credentials and Decentralized Identifiers—from creation and issuance to verification and revocation. Through simple REST APIs, any application can add cryptographically-verifiable data capabilities. The platform is anchored on our custom-built blockchain for security and trust, but we handle all the underlying complexity including token management, key handling, and blockchain interactions, so you can focus on building your application.

No. The One-Click Deployment portal abstracts blockchain complexity. You can deploy production-ready Issuer and Verifier services in minutes without writing smart contracts or managing nodes, or even buying crypto tokens.

Digital credentials (certificates, licenses, tickets), Supply chain tracking (product passports, authenticity), Identity verification (KYC/AML, age verification), Access control (building access, API authentication), AI agent interactions (agent identity and authority delegation)

W3C Verifiable Credentials, W3C Decentralized Identifiers (DIDs) v1.0, OpenID4VC (OpenID for Verifiable Credentials), OIDC4VP (OpenID Connect for Verifiable Presentations), W3C Bitstring Status List v1.0, DIF Well Known DID Configuration (with Domain Linkage)

Yes. The platform provides RESTful APIs that integrate with any tech stack. Use the provided endpoints for credential issuance and verification within your existing workflows.

Private keys are managed securely depending on the component: User wallet keys never leave the user's device. The Empe DID Wallet stores keys securely on the user's mobile device. Issuer keys are stored securely in HashiCorp Vault or Google KMS (depending on deployment) and used by the issuer service to sign credentials. Blockchain access keys are managed automatically by our platform. Issuers and Verifiers never have access to user private keys.

No. Only DID documents (public keys, service endpoints) are on-chain. Actual credential data is stored off-chain in wallets. The blockchain serves as a trust anchor, not a database.

Rotate the keys associated with this DID and update the DID document. Note that credentials may need reissuance after key rotation, as defined by W3C standards. Revoke any credentials that shouldn't be honored.

Credentials are signed but not encrypted by default. They're stored securely in the wallet. For sensitive data, implement application-layer encryption before including in credential subject.

Export existing credential schemas, Map to Empeiria schema format, Re-issue credentials to users, Update verifier logic to accept new credential format

The platform provides RESTful APIs, so any language with HTTP client support works. For verifiers we provide a simple helper library to automatically handle callbacks from Verifier Service - currently implemented in TypeScript/Express.js but support for more platforms is coming soon.

One-Click Deployment: Pricing available at empe.io/pricing. Blockchain transactions: Gas fees are included in subscription, no need to handle tokens directly. Validator operation: Hardware costs + stake requirements

Yes. Deploy multiple Issuer instances for different departments, use cases, or trust levels. Each gets a unique DID.