Submit a record to the database
Submission and correction process for the biomedical blockchain database. What to include, what is out of scope, and how reviews are handled.
Submitting to the database
This is the directory-side entry point for new projects and corrections. The process and the standards are identical to the root submission page. Both routes lead to the same review queue.
What a useful submission contains
- Project name, team, and a primary website or repository.
- A plain description of what the project actually does, separate from marketing language.
- The industry focus category that fits best.
- Any standards, specifications, or published papers the project relies on.
- Source links for every claim that needs verification.
What stays out of scope
- General cryptocurrency without a biomedical or healthcare data angle.
- Token sales, presales, and fundraising vehicles.
- Patient-facing services that do not use ledger or verifiable data structures in their actual stack.
- Promotional material without primary information.
How records change state
A new project usually starts at category level. It is promoted to a named record once enough independent material can be confirmed. Confidence labels are reviewed when new evidence comes in and can move in either direction.
How to send a submission
Use the contact page. There is no submission fee, no paid placement, and no expedited review tier. Replies are not always immediate; queue length varies with the volume of material under review at the time.
What does not appear in records
Records do not include investment encouragement, clinical endorsements, or implied regulatory approval. Where a project itself makes claims of that kind, the record describes those as the project's own claims rather than presenting them as confirmed.