BioWallet

ERC-4337 Smart Wallet with WebAuthn Passkeys and DNA Social Recovery

Daniel Uribe

GenoBank.io — Sequentia Blockchain Network

April 2026

Version 1.0

Share this whitepaper: LinkedIn X (Twitter) Download PDF

Table of Contents

1. The Problem: Why Wallets Fail in Healthcare
2. The Solution: BioWallet Architecture
3. Passkey Authentication (P-256 / WebAuthn)
4. DNA Social Recovery Guardian
5. ERC-4337 Account Abstraction on Sequentia
6. Deterministic Factory and Counterfactual Wallets
7. Token Custody: BioNFTs and BioAssetVault
8. Smart Contract Specifications
9. Security Model
10. Patent Alignment
11. Future Work
12. References

1. The Problem: Why Wallets Fail in Healthcare

Blockchain-based biodata systems promise patients true ownership of their genomic information. Yet the foundational tool of that ownership—the cryptocurrency wallet—was designed for financially-literate early adopters, not patients recovering from chemotherapy or elderly individuals managing a rare disease diagnosis.

1.1 The Seed Phrase Catastrophe

Every externally-owned account (EOA) in Ethereum depends on a 256-bit private key, typically surfaced as a 12- or 24-word mnemonic seed phrase. In the context of healthcare:

• Cognitive load: Patients dealing with a medical diagnosis cannot be expected to securely store a mnemonic phrase. A lost seed phrase means permanent, irrecoverable loss of every BioNFT, consent record, and data-access token in that wallet.
• No recovery path: EOAs have zero social recovery. Unlike a bank password (resettable) or a physical key (replaceable), a lost private key is computationally irreversible.
• Wrong curve: EOAs use secp256k1 (Koblitz curve). Every modern device—every iPhone, Android, MacBook, YubiKey—ships with a Secure Enclave that natively supports P-256 (secp256r1), the WebAuthn standard curve. Forcing patients onto secp256k1 means they cannot use the hardware security they already carry.
• Gas barriers: Every transaction requires the user to hold and manage native gas tokens. A patient who just received a BioNFT representing their whole genome cannot send a consent transaction without first acquiring ETH/SEQ from somewhere.

1.2 The Healthcare UX Gap

Figure 1. The EOA anti-pattern in healthcare: every step introduces a failure mode that is unacceptable for patient-critical data.

Figure 2. BioWallet eliminates every failure mode: gas is sponsored, authentication uses device biometrics, and recovery uses biological identity.

2. The Solution: BioWallet Architecture

BioWallet is built on four pillars:

2.1 System Architecture

Figure 3. BioWallet system architecture on Sequentia. The patient's device Secure Enclave signs UserOps with P-256; the Bundler relays them to the EntryPoint; the Paymaster covers gas; BioRecovery stands as the DNA guardian.

3. Passkey Authentication (P-256 / WebAuthn)

BioWallet authenticates every transaction with a WebAuthn Passkey—the same FIDO2 credential that unlocks your phone and laptop. The signing key never leaves the device's Secure Enclave (Apple T2/M-series, Android StrongBox, YubiKey 5). There is no seed phrase, no browser extension, no mnemonic to back up.

3.1 Why P-256 Instead of secp256k1

3.2 Signature Flow

Figure 4. End-to-end Passkey authentication flow. The patient's biometric confirmation on-device produces a P-256 signature that the smart contract verifies on-chain via RIP-7212 or the pure-Solidity fallback verifier.

3.3 RIP-7212 Precompile with Graceful Fallback

OpenZeppelin's SignerP256 (v5.6) automatically attempts the RIP-7212 precompile at address 0x100 for P-256 verification. If the precompile is not deployed (as on Sequentia today), it falls back to a pure-Solidity P256.sol implementation that verifies the signature using modular arithmetic on the P-256 curve. This dual-path design means BioWallet works on any EVM chain today and will automatically benefit from native precompile speed once RIP-7212 is adopted.

4. DNA Social Recovery Guardian

Traditional smart wallet recovery relies on a set of human guardians (friends, family, institutional custodians) who can collectively authorize a signer rotation. BioWallet introduces a fundamentally different paradigm: your DNA is your guardian.

4.1 The BioRecovery Contract

BioRecovery is an independently-deployed contract on Sequentia (address 0x1555eC4e6397645147595918657b713Ebb5c8fBD) that implements 96-SNP DNA attestation as described in US Patent 11,915,808 ("Privacy-Preserving DNA/RNA/Microbiome/COVID-19 Test Kit Kiosk and Locker That Pairs To and Stores Results Data in Private Digital Wallet," Uribe 2024).

The recovery process works as follows:

1. Sample submission: The wallet owner provides a biological sample (saliva, buccal swab) to an authorized origin lab registered in GenoBank's LabNFT registry.
2. 96-SNP genotyping: The lab genotypes 96 pre-selected single nucleotide polymorphisms (SNPs) from the sample.
3. On-chain attestation: The lab calls BioRecovery.attest(requestId, snpFingerprint, targetWallet, matchCount) with the number of matching SNPs (out of 96).
4. Timelock activation: A 48-hour timelock begins. During this window, the wallet owner (or their legal representative) can challenge the recovery if they suspect unauthorized access.
5. Signer rotation: After the timelock expires, anyone can call BioWallet.executeSignerRecovery(requestId, newQx, newQy) to install a new Passkey as the wallet's signing key.

4.2 Recovery Flow

Figure 5. DNA social recovery flow. The patient's biological sample is the recovery factor, genotyped by a trusted lab. A 48-hour timelock provides a challenge window before the signer rotation completes.

4.3 Recovery Safeguards

5. ERC-4337 Account Abstraction on Sequentia

ERC-4337 separates the account (a smart contract that validates and executes operations) from the signer (the cryptographic key that authorizes those operations). This separation is what allows BioWallet to use P-256 instead of secp256k1, sponsor gas via a paymaster, and support signer rotation without changing the wallet address.

5.1 The UserOp Lifecycle

Figure 6. The ERC-4337 UserOp lifecycle on Sequentia. Steps 1–3 happen off-chain; step 4 is a single atomic on-chain transaction executed by the EntryPoint.

5.2 Sequentia EntryPoint

Sequentia is a private EVM chain (Cosmos SDK + CometBFT, chain ID 15132025) with a single validator. The canonical ERC-4337 EntryPoint (v0.6/v0.7) was designed for public, adversarial networks with complex reputation systems and aggregator support. BioWallet deploys a minimal SequentiaEntryPoint that implements the full IEntryPoint interface but omits:

• Aggregators: handleAggregatedOps reverts. Sequentia has no need for BLS signature aggregation on a single-validator chain.
• Reputation system: Stake/unstake are no-ops. On a private chain, bundler misbehavior is handled out-of-band.
• Simulation: simulateValidation and simulateHandleOp are not implemented. The bundler on Sequentia is a trusted relayer.

What is implemented is the critical path: nonce management, validateUserOp dispatch, paymaster validation, callData execution, and the getUserOpHash computation that binds UserOps to the EntryPoint address and chain ID (preventing cross-chain replay).

5.3 BioPaymaster: Gasless Transactions

On a private chain where gas is essentially free, the paymaster's role is to remove the UX friction of requiring patients to hold native tokens. BioPaymaster auto-approves all UserOps and maintains a SEQ deposit at the EntryPoint that covers gas for every transaction. The deployer funds the paymaster at deploy time (default: 100 SEQ), and the owner can top up or withdraw at any time.

6. Deterministic Factory and Counterfactual Wallets

BioWalletFactory deploys new BioWallet instances via Solidity's CREATE2 opcode, making the wallet address deterministically computable from four inputs:

1. qx — the P-256 public key X coordinate (from Passkey registration)
2. qy — the P-256 public key Y coordinate
3. biosampleSerial — the biosample ID bound to this wallet for BioRecovery
4. salt — a deployer-chosen value for address uniqueness

6.1 CREATE2 Address Derivation

This allows the wallet address to be computed before the wallet is deployed. The ERC-4337 flow exploits this: a UserOp can include initCode that tells the EntryPoint to deploy the wallet on its first operation. The patient gets a wallet address immediately at Passkey registration time, can receive BioNFTs and tokens at that address, and the wallet contract is only deployed when the first transaction is actually sent.

6.2 Counterfactual Wallet Creation

Figure 7. Counterfactual wallet creation. The address is predictable before deployment; the wallet materializes on-chain only when the patient sends their first transaction.

7. Token Custody: BioNFTs and BioAssetVault

BioWallet implements both ERC1155Holder and ERC721Holder (via IERC721Receiver), enabling it to directly custody:

• BioNFTs (ERC-721) — Revocable consent and ownership tokens representing a patient's relationship to their biodata.
• BioAssetVault tokens (ERC-1155) — Parent/child hierarchy tokens where a parent represents a biosample and children represent derived data files (BAM, VCF, FASTQ, SQLite, CRAM, BED, gVCF).

The wallet reports correct ERC-165 interface support for IERC1155Receiver (0x4e2312e0), IERC721Receiver (0x150b7a02), and IERC165 (0x01ffc9a7), ensuring that safeTransferFrom calls from both token standards succeed.

7.1 Batch Execution

BioWallet supports batched execution via executeBatch(address[], uint256[], bytes[]), allowing a single UserOp to perform multiple operations atomically. This is critical for biodata workflows where a patient might simultaneously:

• Grant consent to a researcher (BioNFT transfer)
• Transfer a data-access token (BioAssetVault child)
• Update a BioRoutes storage pointer

All three operations execute in a single on-chain transaction, with a single Passkey signature, and zero gas cost to the patient.

8. Smart Contract Specifications

8.1 Contract Inventory

8.2 Inheritance Hierarchy

Figure 8. BioWallet inheritance hierarchy. Green = BioWallet. Blue = OpenZeppelin v5.6 primitives. Yellow = ERC-4337 interface. Red = BioRecovery interface.

8.3 BioWallet Interface

// Core execution
function execute(address target, uint256 value, bytes calldata data)
    external onlyEntryPointOrSelf returns (bytes memory);
function executeBatch(address[] targets, uint256[] values, bytes[] datas)
    external onlyEntryPointOrSelf;

// ERC-4337
function entryPoint() public view returns (IEntryPoint);
function validateUserOp(PackedUserOperation, bytes32, uint256)
    external returns (uint256 validationData);

// Recovery
function executeSignerRecovery(bytes32 requestId, bytes32 newQx, bytes32 newQy)
    external;

// State
function biosampleSerial() external view returns (uint256);
function signer() external view returns (bytes32 qx, bytes32 qy);
function usedRecoveryRequests(bytes32) external view returns (bool);
function bioRecovery() external view returns (IBioRecovery_Wallet);

8.4 BioWalletFactory Interface

function createWallet(bytes32 qx, bytes32 qy, uint256 biosampleSerial, bytes32 salt)
    external returns (BioWallet wallet);
function computeAddress(bytes32 qx, bytes32 qy, uint256 biosampleSerial, bytes32 salt)
    external view returns (address);

function entryPoint() external view returns (address);
function bioRecovery() external view returns (address);
function isWallet(address) external view returns (bool);

8.5 SequentiaEntryPoint Key Functions

function handleOps(PackedUserOperation[] calldata ops, address payable beneficiary)
    external;
function getUserOpHash(PackedUserOperation calldata userOp)
    external view returns (bytes32);
function getNonce(address sender, uint192 key)
    external view returns (uint256);
function balanceOf(address account)
    external view returns (uint256);
function depositTo(address account) external payable;

8.6 Events

8.7 Custom Errors

9. Security Model

9.1 Threat Model

Figure 9. Threat model and mitigations. Red = threat. Green = mitigation. Every attack vector has a concrete, implemented defense.

9.2 Security Properties

10. Patent Alignment

BioWallet implements key claims from US Patent 11,915,808 B2 ("Privacy-Preserving DNA/RNA/Microbiome/COVID-19 Test Kit Kiosk and Locker That Pairs To and Stores Results Data in Private Digital Wallet," Uribe 2024):

11. Future Work

11.1 Multi-Device Passkey Sync

Apple, Google, and Microsoft now support cross-device Passkey synchronization via iCloud Keychain, Google Password Manager, and Windows Hello respectively. BioWallet can leverage this to reduce recovery scenarios: if a patient registers a Passkey on their iPhone, it automatically becomes available on their iPad and Mac. The on-chain P-256 verifier does not need to change—the synced credential produces the same (qx, qy) public key.

11.2 Session Keys

For high-frequency, low-risk operations (e.g., BioRoutes resolution queries, Bloom filter match requests), BioWallet could issue time-limited session keys that are authorized by a single Passkey signature but execute independently thereafter. This would reduce biometric prompts for routine operations while maintaining the security invariant that the Passkey remains the root of trust.

11.3 Multi-Signer Guardianship

The current recovery model uses a single DNA attestation. Future versions could support M-of-N recovery combining DNA attestation with institutional guardians (e.g., a hospital compliance officer + DNA attestation, or two independent lab attestations). The executeSignerRecovery function's interface is designed to accommodate this extension.

11.4 RIP-7212 Precompile Deployment on Sequentia

Once the Sequentia validator deploys the RIP-7212 precompile (a configuration change in the Cosmos SDK EVM module), P-256 verification gas cost drops from ~330k gas (pure-Solidity) to ~3,450 gas (native precompile)—a 100x improvement. BioWallet's OpenZeppelin SignerP256 will automatically use the precompile with zero contract changes.

11.5 BioRoutes Integration

BioWallet is designed to integrate with the BioRoutes protocol (the "DNS of biodata"), where every storage location of a patient's biodata is an on-chain event. The wallet's executeBatch function enables atomic operations that simultaneously update BioRoutes entries, transfer BioNFT consent tokens, and log BioAssetVault provenance—all in a single gasless UserOp.

12. References

BioWallet is part of the GenoBank.io decentralized biodata infrastructure, deployed on the Sequentia Blockchain (Chain ID 15132025).

Your body. Your wallet. Your data.