Back to Blog
Product

Introducing Bio-DID-Sequencer: Decentralized Identifiers for Research Data

What Bio-DID-Sequencer is, what it does with W3C identifiers and IPFS, and where the boundaries of the current implementation are.

Sneha Priya
December 15, 2025
8 min read

The Challenge of Research Data Management

Research institutions worldwide face a common challenge. They have to manage, share, and preserve research data in a way that is secure, accessible, and compliant with evolving privacy regulations. Traditional centralized systems create single points of failure, while existing identifier systems often lack the flexibility needed for modern collaborative research.

Introducing Bio-DID-Sequencer

Bio-DID-Sequencer implements the W3C Decentralized Identifier specification for research data. A researcher's identifier is their Solana wallet address, so it is derived from a keypair rather than issued by a registrar. A dataset, a paper or a claim gets an identifier of its own, which the wallet derives from itself and a nonce, so nobody has to keep a key per asset. Once anchored on-chain, both resolve to documents the wallet controls.

Key Features

W3C DID Compliance Every identifier created through Bio-DID-Sequencer follows the W3C DID specification, ensuring interoperability with the broader decentralized identity ecosystem.

Sealed IPFS Storage Research data is stored on IPFS through the platform's own cluster.

  • Every upload is sealed before it is added, under a fresh AES-256-GCM key wrapped with ML-KEM-1024.
  • The CID names the sealed envelope, so a modified copy is detected on retrieval.
  • A file stays available for as long as the platform keeps it pinned.

Privacy by Design Privacy is part of the architecture rather than a feature added later.

  • Nothing personal is anchored on-chain. The registry holds public keys, opaque fragments and URIs.
  • Public metadata documents carry no contact details.
  • Access is granted per file, through passes the owner's wallet signs, each with an expiry and each revocable.
  • Deleting a file unpins the platform's copy, and any copy fetched earlier is an envelope only the service can open.
  • Deactivating a DID is permanent and public. It retires the identifier and erases nothing, which is why nothing personal goes on-chain in the first place.

Architecture Overview

Clients & AuthorizationResearcherwallet, session tokenBrowser applicationsigns bytes the API preparesUCAN passeswallet signed, revocableEkayana API (bio-did-seq)axum, Postgres, private IPFS clusterAPI modulesAccounts & walletssessions, Sign In With SolanaDID recordsowned subjects, workflowsFilessealed, pinned on writeUCAN validationpq-ucan, service as executorPapersregistration, ingestionIPNS namesversions, delegated updatesStoresPostgresaccounts, records, passesPrivate IPFS clusterswarm key, replicated pinsbio-did-registryDID documents on SolanaSealed payloadsowner bound envelopesMetadata documentspublic JSON, one per DIDIPNS keysfronted peer keystoreUpstream servicesBioAgentsElizaOS agents and pluginsDataversewith the user's own tokenOpenAI / Anthropic/api/ai/*, agent text modelKnowledge basepgvector, registered papersKnowledge graphOxigraph, one graph per DOIProtein structureAlphaFold DB, UniProtsession token and wallet signaturesread and writeproxied by the API
The Bio-DID-Seq platform stack

Getting Started

Getting started with Bio-DID-Sequencer is straightforward. The account needs a linked wallet, because the identifier is derived from it.

typescript
// There is no SDK to install. The platform is a plain HTTP/JSON API.
const res = await fetch('https://api.ekayana.io/api/did', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${token}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    kind: 'dataset',
    metadata: {
      title: 'Climate Research Dataset 2024',
      keywords: ['climate'],
      license: 'CC-BY-4.0',
    },
  }),
});

const record = await res.json();
console.log('Created DID:', record.did);

Nothing is on-chain yet. The wallet anchors the DID by signing one transaction, and from then on it resolves for anyone. The did:bio Identifiers guide walks through both steps.

What's Next

We're just getting started. In the coming months, we'll be rolling out:

  • Enhanced BioAgents for automated metadata extraction
  • Knowledge graph integration for semantic discovery
  • Expanded Dataverse integration capabilities
  • Additional Protocol Labs integrations

Stay tuned for more updates, and get started with the documentation today!

Ready to Get Started?

Explore our documentation to learn how to integrate Ekayana into your research workflow.