Services & Use Cases

Register DIDs

Mint persistent, resolvable did:bio identifiers for datasets, papers, samples, instruments, and heritage collections. Each one is anchored in the Solana registry, content addressed on IPFS, and verifiable by anyone.

Why?

What a persistent identifier has to do

Research outputs stay discoverable and citable only while their identifiers keep resolving. A did:bio does that, and it also lets anyone verify who controls the record and whether the metadata has changed. It sits alongside the identifiers you already use: through the Dataverse and Zenodo bridges, datasets keep their DOIs and gain a decentralized counterpart.

Persistent and resolvable

Like a DOI, a did:bio is a stable reference that belongs in a citation. Its resolution does not depend on a single resolver staying funded: the identifier is anchored in the Solana registry, and the record it points at is content addressed on IPFS.

Cryptographically verifiable

Every DID document carries its own verification methods, including post-quantum ML-DSA-87 (FIPS 204) assertion keys alongside Ed25519. Anyone can check who controls an identifier and whether its metadata has been altered since it was signed. No registrar has to vouch for it.

Sovereign and GDPR-aligned

Nothing personal is anchored on-chain. The registry holds public keys, opaque fragments, and URIs. Private payloads are encrypted before they reach IPFS, so a right-to-erasure request is satisfied by destroying a decryption key.

What?

Two ways to register

Registration runs through the Ekayana Console or the REST API. Both write the same thing: a W3C-conformant DID document, anchored on the Solana registry and resolvable by anyone.

Ekayana Console

A web interface for minting and managing did:bio identifiers. Enter metadata through guided forms, review and update your DID documents, and see every registration your organization holds. No code required.

REST API

Plain HTTP and JSON for systematic registration: mint, update, and resolve identifiers from repository pipelines and submission workflows. It is the same surface used for workflow integration and by the Registered Service Providers who run Ekayana infrastructure for their own communities.

The metadata record

Every registration follows the Ekayana metadata schema: W3C DID core plus a research profile covering titles, researchers and their roles, keywords, licenses, and links to existing DOIs. The same record that makes an output citable also feeds the knowledge graph behind semantic discovery, and BioAgents can extract and pre-fill it from the deposited documents.

How?

Three steps to a resolvable identifier

The path is the same through the Console and the API: open an account, mint the identifier, then resolve it.

  1. Create an account

    Individual researchers can start on the free Researcher tier: public resolution, 100 did:bio registrations a year, and 5 GB of pinned IPFS storage. Organizations registering at production volume join as a member, beginning with a short membership inquiry.

  2. Mint the identifier

    Enter metadata through the Ekayana Console form, or POST /api/did from your own pipeline. Each registration writes the DID document, anchors it in the Solana registry, stores the metadata record, and makes the identifier available to resolvers.

  3. Resolve it anywhere

    GET /api/did/resolve/{id} returns the signed DID document to anyone, with no account required. The did:bio method is generatively resolvable, meaning every valid identifier resolves to a deterministic document rather than a dead link.

Mint an identifierJavaScript
// Mint a did:bio identifier for a dataset
const res = await fetch('https://api.ekayana.com/api/did', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${token}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    controller: 'did:bio:devnet:2T6zLFvMx7NJ...',
    public_key: 'z6MkfuN2vWAoHermh6vY6TgAJfwhBWZC...',
    metadata: {
      title: 'Coral bleaching survey 2026',
      researchers: [{ name: 'Ada Lovelace', role: 'PI' }],
      keywords: ['coral', 'bleaching'],
      license: 'CC-BY-4.0',
    },
  }),
});

const didDocument = await res.json();
Resolve an identifierbash
# Public resolution: no account and no token required
curl https://api.ekayana.com/api/did/resolve/did:bio:devnet:2T6zLFvMx7NJ...

# Returns the signed DID document: verification keys,
# service endpoints, and the research metadata record.

Authentication, updates, and Dataverse DOI linking are covered in the documentation.

What a registration costs

There are no per-DID charges. The annual service fee covers up to 100,000 did:bio registrations a year, with volume surcharges above that. A registration includes the DID document, Solana registry anchoring, the metadata record, and resolver availability. See the fee schedule for service fee bands and storage add-ons.

Use cases

What you can register

The same registration flow covers research outputs, the objects behind them, and heritage collections. It is one of six Services & Use Cases.

Datasets
Research data addressed by content, so identical bytes always produce the same CID. Pairs with Promote Reuse for citation and usage reporting.
Papers and preprints
Publications, with BioAgents extracting entities and enriching the metadata record for the owner to review before publication.
Physical samples
Specimens, cores, and cultures, linked to the datasets and papers derived from them.
Instruments and facilities
The equipment behind a measurement, so provenance chains in the knowledge graph reach the source.
Cultural heritage
Artifacts, collections, digitized manuscripts, and archival records: content addressed, tamper evident, and discoverable through semantic search, with the holding institution deciding where the data physically lives.

Ekayana is pre-launch. We are assembling a founding network of repositories, libraries, and heritage institutions. Follow the research blog for progress, or start a membership inquiry to join it.

Start registering did:bio identifiers

Follow the quickstart to mint your first identifier, or review the fee schedule if you are planning for production volume.