Ever Integration and Services

Although a decentralized system built on blockchain and IPFS technology offers users the benefit of self-managed data storage, most users may find it difficult to maintain their own IPFS servers or pay gas fees on the blockchain.

Ever therefore provides internal services for its users to simplify the onboarding experience.

Ever Service Architecture

EverApp / WebClient

Device Secrets & Wallet

Client-side crypto

Third-Party Apps

Device Secrets & Wallet

Direct calls

Ever Services

Ever Services

OMA, Health Wallet

HIE / HIS

Hospital integration

IPFS Cluster

File storage

EDH Service

Gas Payer Wallet

Forward Meta Transactions (ERC-2771)

Decentralized Storage

Ever File System (EVFS)

Encrypted files on IPFS / S3

Blockchain (EVM)

TrustedForwarder

Meta-tx relay

EDHAccountRegistry

Account factory

SeedVault

Encrypted seeds

EDHAccount

Public keys

Ever services bridge clients to decentralized storage and blockchain

Service Overview

Service	Description	Type
EDH Account Service	Manages accounts, keys, and the Bio-OIDC Provider	REST API
EDH Gas Payer Wallet	Pays gas fees on behalf of users via ERC-2771	Blockchain
S3/Filebase Storage	Stores files through an S3-compatible API	Storage
IPFS Cluster	Stores files on the IPFS network	Storage
File Viewer	Shares file links with time-limited access	Web
EDH Adaptor	Connects with hospital PHR systems	Integration
Accounts Worker	Processes blockchain transactions asynchronously	Background
EDH API Service	REST API for interacting with Smart Contracts	REST API

EDH Account Service

EDH users or centralized services that do not wish to manage their own device secret storage can use the EDH Account Service to store keys and credentials as if it were a user device. The service also stores keys and credentials for Ever's own services, such as HIE.

Each device's private key is stored on the device itself. Ever never stores users' private keys.

Core Capabilities

• Account Management: Create accounts, generate wallets, and register devices on the blockchain
• Seed Vault Management: Store and share cryptographic seeds across devices
• Account Lookup: Search for and verify user accounts
• Bio-OIDC Provider: OpenID Connect-based identity verification (see next section)

API Authentication

• Service-to-Service: Basic Authentication for internal services
• User Sessions: Bearer Token from the Bio-OIDC flow

Bio-OIDC Provider

The EDH Account Service includes a built-in OpenID Connect (OIDC) identity provider that uses wallet-based authentication instead of passwords, called the Bio-OIDC Provider.

OIDC Endpoints

Endpoint	Description
/.well-known/openid-configuration	OIDC Discovery document
/bio-oidc/authorize	Authorization endpoint
/bio-oidc/token	Token endpoint (issues id_token, access_token)
/bio-oidc/userinfo	UserInfo endpoint
/bio-oidc/register	Client registration
/bio-oidc/wallet-response	Wallet signing callback
/bio-oidc/commitment	Genomic commitment endpoint

Authentication Flow

1. The Relying Party (RP) redirects the user to /bio-oidc/authorize with the client_id and redirect_uri
2. The user authenticates via wallet signing (challenge-response) — no password required
3. The system verifies the bio-anchor on the BioAnchorRegistry (if available)
4. The system issues an id_token (JWT) containing bio claims back to the RP

Bio Claims in id_token

{
  "sub": "did:bio:ever:0x1234...abcd",
  "bio_assurance_level": 2,
  "bio_anchor_mode": "onchain",
  "bio_liveness_active": true,
  "bio_modalities": ["genomic", "physiological"]
}

Claim	Description
sub	Subject identifier in the format did:bio:ever:0x...
bio_assurance_level	Assurance level (0-3)
bio_anchor_mode	Anchoring method (onchain or oidc-only)
bio_liveness_active	Liveness attestation status
bio_modalities	Biometric modalities used

To get started with Bio-OIDC, see the BIA Developer Quickstart.

EDH Gas Payer Wallet

To make things easier for most Ever users who do not want to worry about purchasing cryptocurrency to use the system, Ever has developed a service that pays gas fees on behalf of Ever application users through the ERC-2771 Meta-Transaction standard.

ERC-2771: Meta-Transaction

Calling Smart Contract functions incurs gas costs. Since most users may not be comfortable managing gas fees on the blockchain, Ever's Smart Contracts implement the ERC-2771 standard for sending meta-transactions.

• Users sign a message digest according to the EIP-712 Typed Data standard
• The EverTrustedForwarder contract verifies the signature and submits the transaction on behalf of the user
• Ever covers the gas costs through the Gas Payer Wallet
• The Smart Contract verifies the msg.sender from the forwarder to confirm the actual account owner

Estimated Gas Costs

Actual costs depend on the network being used (Polygon, Ethereum, Base, etc.).

Operation	Gas (estimated)
Register Account	~200,000
Register Device	~100,000
Revoke Device	~50,000
Update Storage	~60,000
Register Bio-Anchor	~65,000

注記

The Gasless Transaction feature is a supplementary service provided by Ever to help Ever users avoid paying gas fees themselves. Other users or service providers can still call the Smart Contracts directly as usual.

S3/Filebase Storage

In addition to uploading files directly to IPFS, EDH also supports storage through an S3-compatible API via filebase.com.

How It Works

• The application uploads files (already encrypted) via the S3 API to Filebase
• Filebase automatically pins the files to IPFS and returns a CID
• The application can download files using an S3 presigned URL or directly via the IPFS CID

Advantages

• No need to maintain your own IPFS node
• Supports presigned URLs for secure uploads and downloads
• Files remain accessible via their IPFS CID
• Ideal for applications that need simple HTTP-based uploads

Ever IPFS Cluster

Uploading data to the IPFS network requires a server to store the files. While users are free to use any IPFS service provider and can even run their own IPFS node, Ever also provides an IPFS file storage service for Ever users.

File Viewer

To share file links with doctors or other parties, Ever provides a File Viewer web service that allows files to be viewed with time-limited access. It also logs link access events for auditing purposes.

Features

• Time-limited link access
• Link access logging (audit trail)
• Supports rendering of FHIR, DICOM, PDF, and image formats
• No application installation required — accessible directly through a web browser

EDH Adaptor (PHR Integration)

The EDH Adaptor is a service for connecting hospital Personal Health Record (PHR) systems with the EDH platform.

How It Works

Healthcare System Integration

Hospital HIS

EMR / PHR

→

EDH Adaptor

PHR Bridge

→

EDH Account Service

+ Bio-OIDC

→

Smart Contracts + EVFS

Integration Methods

HIE

EDH API + FHIR

HIS

PHR Adaptor + Pub/Sub

OMA

Direct EDH SDK

Health Wallet

ever-edh-core SDK

Supported Data Standards

FHIR R4DICOMVCFPDFJPEGHL7

All files encrypted with NaCl SecretBox before storage on EVFS. Compliant with HIPAA, GDPR, and Thai PDPA.

Hospital data flows through EDH Adaptor into encrypted, patient-controlled storage

• Receives health data from the hospital's HIS system
• Automatically creates EDH accounts for new patients
• Stores PHR data with a CID reference on EVFS
• Uses Google Cloud Pub/Sub as a message queue for asynchronous processing
• Supports webhook/event-driven architecture

Supported Integrations

For more details on integration formats, see Medical Data Standards.

EDH Accounts Worker

A service for processing blockchain transactions asynchronously to handle high transaction volumes.

• Uses a job queue (pg-boss) to sequence transactions
• Manages gas estimation and retry logic
• Tracks transaction status (pending, confirmed, failed)
• Supports admin operations for scaling

X3DH Key Exchange

EDH includes the edh-x3dh library for Extended Triple Diffie-Hellman key exchange to establish encrypted messaging channels between accounts.

• Uses the X3DH protocol for forward secrecy
• Creates session keys for encrypted communication between two accounts
• Suitable for secure messaging between patients and doctors

EDH API Service

A REST API service for interacting with Smart Contracts on the blockchain, designed for other services that do not need to connect to the blockchain directly. Services such as HIE and HIS connect through the EDH API Service.

See Also

• System Overview — EDH system architecture
• User Account — Smart Contract for account management
• BIA Developer Quickstart — Getting started with BIA
• Medical Data Standards — FHIR, DICOM, VCF