GenoVerse Viewer

Anonymous, Wallet-Gated Genomic Risk and Pharmacogenomics Reports

Daniel Uribe

GenoBank.io — Sequentia Blockchain Network

April 2026

Version 1.0

Share this whitepaper: LinkedIn X (Twitter) Download PDF

Table of Contents

1. Origin Story: A Father's Search
2. The Problem: Genomic Reports Without Ownership
3. GenoVerse Viewer Architecture
4. Report Catalogue: Health Risk and Pharmacogenomics
5. SNP Interpretation Engine
6. Membership NFT Access Control
7. GenoVerse Explorer: The Biodata Network Graph
8. Privacy Model: Anonymous by Design
9. Regulatory Positioning
10. Integration with GenoBank.io Infrastructure
11. Future Work
12. References

1. Origin Story: A Father's Search

In 2017, Daniel Uribe's son was diagnosed with Glanzmann's Thrombasthenia—a rare inherited bleeding disorder caused by mutations in the ITGA2B and ITGB3 genes. The diagnostic odyssey that followed exposed every failure mode of the traditional genomics reporting pipeline: results locked inside hospital portals, no way for the family to share data with a second-opinion specialist without a fax machine, and zero ability to query the raw genetic data against new research as it emerged.

Six years later, with the tools GenoBank.io had built in the interim, the same genomic data was re-analyzed through GenoVerse Viewer. The updated interpretation reclassified the diagnosis as Gray Platelets Syndrome (NBEAL2 gene, autosomal dominant)—a related but clinically distinct condition with different treatment implications. This reclassification was only possible because the family owned their data and could re-run it against an updated knowledge base, rather than depending on the original hospital to re-interpret results it had long since archived.

GenoVerse Viewer exists so that no family has to fight for access to their own genetic information.

2. The Problem: Genomic Reports Without Ownership

2.1 The Status Quo

Figure 1. The status quo: genomic reports are generated once and frozen. New research never flows back to the patient.

Today's consumer genomics platforms (23andMe, AncestryDNA, hospital portals) share a common architecture:

• Email + password authentication. The patient's identity is known to the platform. Data breaches expose both identity and genotype—the most permanently sensitive data a person has.
• Institutional custody. The raw VCF/BAM data lives on the company's servers. If the company is acquired, bankrupted, or hacked (as 23andMe demonstrated in 2023), the patient has no recourse.
• Static reports. A report generated in 2020 reflects the knowledge base of 2020. When a new pharmacogenomic association is discovered in 2024, the report does not update.
• No portability. Moving genomic data from one provider to another requires manual export, email-to-email transfers, and often re-sequencing.

2.2 The GenoVerse Alternative

Figure 2. GenoVerse Viewer: wallet-gated, dynamically-interpreted, permanently owned by the patient.

3. GenoVerse Viewer Architecture

3.1 System Overview

Figure 3. GenoVerse Viewer system architecture. The patient's wallet is the only authentication factor. No email, no password, no PII.

3.2 Authentication Flow

Figure 4. Authentication sequence. The wallet signature replaces a login/password pair. The Membership NFT replaces a subscription database row.

3.3 Report Rendering Pipeline

Reports are rendered entirely client-side. The API delivers raw genotype data (rsID + alleles); the interpretation index (a static JSON mapping rsID × genotype → clinical text + magnitude + severity color) is loaded from CDN. The viewer matches the patient's genotypes against the index, computes a coverage ratio (matched vs. total SNPs in the panel), and renders the interactive report card with:

• SNP cards — each card shows the rsID (linked to dbSNP), the patient's genotype (e.g., TT, AG, GG), a clinical interpretation, and a magnitude score (0–3).
• Coverage donut chart — visual ratio of matched SNPs (colored by severity) vs. unmatched SNPs (grey), showing how much of the panel was genotyped in the patient's dataset.
• Download JSON / Print — the patient can export their report as structured JSON or print to PDF at any time.
• Hide Unmatching SNPs — toggle to focus only on SNPs present in the patient's genotype data.

4. Report Catalogue: Health Risk and Pharmacogenomics

4.1 Disease Risk Panels

4.2 Pharmacogenomics Panels

4.3 General SNP Risk Analyzer

Beyond curated panels, GenoVerse Viewer includes a general-purpose SNP Risk Analyzer that matches the patient's full genotype against the master interpretation index. This index maps over 100 clinically-annotated rsIDs to genotype-specific interpretations covering MTHFR deficiency (rs1801133), hemochromatosis (rs1800562, rs1799945), drug metabolism (CYP2D6, CYP2C19, CYP3A4 families), caffeine sensitivity (rs762551), and dozens more.

5. SNP Interpretation Engine

5.1 Index Structure

Each report type is backed by a JSON interpretation index. The structure is uniform across all panels:

Fields:

• text — Plain-language clinical interpretation. Written for patients, not geneticists.
• mag — Magnitude score (0 = normal/benign, 1 = mild, 2 = moderate, 3 = significant). Adapted from the SNPedia magnitude scale.
• color — Severity indicator for the report card UI: green (normal), yellow (attention), red (actionable).

5.2 Matching Algorithm

Figure 5. SNP matching algorithm. Every SNP in the panel is rendered — matched (colored) or missing (grey) — so the patient always sees the full scope of what was tested.

5.3 Index Versioning and Updates

Interpretation indices are versioned and served from CDN. When new pharmacogenomic evidence is published (e.g., a CPIC guideline update for a statin), the index is updated, and every patient who loads the report thereafter sees the updated interpretation against their unchanged genotype data. This is the fundamental advantage over static PDF reports: the knowledge base evolves; the data stays stable.

6. Membership NFT Access Control

6.1 GenoVerseMembershipNFT Contract

Access to GenoVerse Viewer is gated by an ERC-721 Membership NFT deployed on Avalanche. The contract (symbol: GenoVerseNFT) implements time-bounded memberships:

Key contract functions:

• isMembershipActive(tokenId) — returns true if expirationDate > block.timestamp. The Viewer calls this on every page load.
• getMembershipExpiration(tokenId) — returns the Unix timestamp of expiration, displayed in the Viewer UI.
• Batch minting — up to 10 NFTs per transaction, enabling lab partners to pre-provision memberships for their patient cohorts.

6.2 Why an NFT Instead of a Database Row

Figure 6. NFT-gated access vs. traditional SaaS subscription. The Membership NFT is transferable, verifiable by any third party, and requires no backend database.

The NFT model provides three properties that a database row cannot:

1. Transferability. A patient can transfer their membership to a family member or caregiver by sending the NFT.
2. Third-party verifiability. Any dApp, researcher portal, or clinical system can verify membership without calling GenoBank's servers.
3. Censorship resistance. GenoBank cannot revoke a valid membership. Once minted, the expiration is enforced by smart contract logic, not by an admin panel.

7. GenoVerse Explorer: The Biodata Network Graph

GenoVerse Explorer is a companion application that visualizes the entire GenoBank.io biodata network as an interactive force-directed graph. It answers the question: "What data exists, where did it come from, and how much is on-chain?"

7.1 Data Model

7.2 The Five Origin Labs

7.3 Interaction Model

The Explorer supports interactive filtering: clicking a lab highlights its subgraph, clicking a file-type chip (BAM, VCF, FASTQ, SQLite, CRAM, BED, gVCF) filters to that type across all labs, and clicking any node opens a detail panel showing metadata. A search bar accepts biocid, tokenId, or wallet address queries. All rendering is done client-side via D3.js force simulation with zoom/pan controls.

8. Privacy Model: Anonymous by Design

8.1 What GenoVerse Knows About You

8.2 The Anonymity Guarantee

Figure 7. Breach impact comparison. A GenoVerse breach yields a pseudonymous wallet address and an encrypted data blob. A traditional platform breach yields a complete identity-to-genotype link.

GenoVerse achieves anonymous genomic reporting through three architectural choices:

1. Wallet-only identity. The wallet address is a pseudonymous identifier. Without external data (exchange KYC records, on-chain analytics), it cannot be linked to a real-world person.
2. Client-side rendering. The interpretation index is a static JSON served from CDN. The matching happens in the browser. GenoBank's servers never see which report the patient viewed or which SNPs matched.
3. Revocable access. If the patient revokes their BioNFT (Metamorphic Consent), all downstream access to their genotype data is blocked at the smart contract level. The encrypted GCS object remains, but no API can serve it.

9. Regulatory Positioning

9.1 FDA Section 3060(a): Clinical Decision Support Software

GenoVerse Viewer is positioned as Clinical Decision Support Software (CDS) under FDA 21st Century Cures Act, Section 3060(a), which exempts software that:

1. Is not intended to acquire, process, or analyze a medical image or signal from an in vitro diagnostic device.
2. Displays, analyzes, or prints medical information about a patient already generated by qualified professionals.
3. Is intended for healthcare professionals or patients to independently review before making clinical decisions.
4. Enables the user to independently review the basis for the recommendation.

GenoVerse satisfies all four criteria: it displays pre-generated genotype data, provides interpretations for independent review, does not acquire or process diagnostic signals directly, and always presents the underlying SNP evidence alongside every interpretation.

9.2 GDPR Compliance via Patient Ownership

GenoVerse's privacy model makes traditional GDPR data-controller obligations largely moot: the patient is both the data subject and the data controller. The patient's BioNFT is the access-control mechanism, and revocation (Article 17 right to erasure) is enforced on-chain. GenoBank acts as a data processor only to the extent that it stores encrypted genotype blobs in GCS—access to which is gated by BioNFT ownership, not by GenoBank's unilateral decision.

10. Integration with GenoBank.io Infrastructure

Figure 8. GenoVerse Viewer and Explorer in the broader GenoBank.io ecosystem. Viewer is the patient-facing surface; everything below it is infrastructure the patient never sees.

11. Future Work

11.1 GenAI Co-Pilot Integration

GenoVerse's next evolution is a conversational AI co-pilot that can answer patient questions in natural language: "Do I carry APOE ε4?", "What does my MTHFR status mean for folic acid?", "Which of my medications might interact with my CYP2D6 genotype?" This co-pilot (powered by the GenoClaw RAG engine already deployed at /web3kit) will query the patient's actual genotype data from the BioWallet Health Vault, ensuring answers are grounded in real variants, not generic population data.

11.2 BioWallet-Native Access

Once BioWallet (ERC-4337 + WebAuthn Passkeys) is deployed, patients will authenticate to GenoVerse with FaceID or TouchID instead of MetaMask. The Membership NFT will reside directly in the BioWallet, and the wallet's DNA social recovery guardian will protect both the membership and the underlying genomic data from permanent loss.

11.3 Decentralized "Spotify" for Genomics Data

The long-term vision is a marketplace where patients are data partners, not data sources. Researchers query genetic variants through privacy-preserving Bloom filters (never seeing raw genotypes), and patients earn Biodata Dividends via Shapley value attribution when their data contributes to a discovery. GenoVerse Viewer evolves into the patient's dashboard for this economic relationship—showing not just health reports, but revenue from their data, consent logs, and clinical trial candidacy matches.

11.4 Expanded Pharmacogenomics Coverage

The current pharmacogenomics panels cover the most clinically-actionable drug-gene pairs. Future panels will expand to cover the full CPIC (Clinical Pharmacogenetics Implementation Consortium) guideline set: 40+ drugs with level A/B evidence, including opioids (CYP2D6/OPRM1), antidepressants (CYP2D6/CYP2C19), and immunosuppressants (TPMT/NUDT15).

12. References

GenoVerse Viewer is part of the GenoBank.io decentralized biodata infrastructure.
Live at genoverse.io — Explorer at explorer.sequentias-test.genobank.io

Your genome. Your wallet. Your reports.