Chain
777001
Chain 777001 · live since 2026-05-25
The chain you can show your lawyer.
An EVM Layer-1 built for regulated records.
Khromosome is a sovereign EVM L1 (Reth + Lighthouse PoS) running production today with a lock-and-mint bridge to Ethereum mainnet, encrypted file vault, sanctions-screened bridge transfers, formal verification on every bridge invariant, and a 16-validator network. Built for HIPAA-aware medical records and audit-trailed financial events — but it's just Ethereum underneath, so anything you can write in Solidity runs here.
01
The problem.
The problem.
Three industries can't use blockchain — and they're the biggest.
Healthcare
HIPAA + records that follow you for life
Every clinic has its own EHR. Records don't follow patients. Audit trails are paper. A blockchain is the natural primitive — but no chain has HIPAA-grade compliance baked in, and no chain stores files (only hashes), so it's been theoretical for a decade.
Finance
DeFi can't pass a sanctions audit
Permissionless chains can't refuse a transfer. That makes them unusable for any regulated institution — banks, fintechs, broker-dealers. Public chains route around the problem; we built it in.
Identity
Self-custody but ZK-private is still theoretical
Wallet = identity is great until you have to disclose. Real-world identity wants both irrevocable proofs (chain-anchored) and selective disclosure (everything else off-chain, encrypted, revocable). No general-purpose stack ships this.
02
What Khromosome is.
What Khromosome is.
A sovereign L1 + a bridge + a stack of regulated-vertical primitives.
Think of it as Ethereum mainnet, except (a) we run it, (b) every contract you'd need for medical records / financial audit / sanctions / identity is preinstalled and verified, and (c) tokens flow back to mainnet via a lock-and-mint bridge so the real-money side stays on Ethereum.
Layer 1 · Application surfaces
9 live dApps
khromosome.network apex · app dashboard · pools (DEX) · staking · faucet · 3D chain viewer · charts · KHROME Explorer · docs · self-hosted Sourcify. All HUD-styled, all served via Cloudflare-proxied origin masking.
▼
Layer 2 · Compliance contracts (deployed + verified)
8 contracts
KhromeChain (records anchor) · KhromeVault (encrypted file storage with on-chain manifests) · KhromeSubscription (stake-for-tier) · KhromeBridge ↔ BridgedKHROME (mainnet bridge) · OperatorRegistry (KYC'd validators) · AuditLog (tamper-evident log primitive) · SanctionsScreen (OFAC-synced registry) · Khromeswap (KDEMO/KHROME AMM).
▼
Layer 3 · Off-chain services
Vault API · Bridge relayer · OFAC sync · Watchdog · Web3Signer
Vault API serves presigned MinIO URLs (ciphertext-only). Bridge relayer reads SanctionsScreen before signing. OFAC daemon syncs the U.S. Treasury list daily. Watchdog auto-recovers stuck containers. Web3Signer holds all 16 validator BLS keys with Postgres slashing protection.
▼
Layer 4 · The chain
Reth v1.8 · Lighthouse v8 · Casper FFG
Identical stack to Ethereum mainnet. 16 validators across 2 hosts (opensolara DE + openclaw-vps DE — geographic diversification on roadmap). Chain ID 777001. ~12-second blocks. Submitted to ethereum-lists/chains (PR #8367, awaiting merge).
03
Every contract.
Every contract.
Live on-chain · open source · verified bytecode.
BridgedKHROME
ERC-20 on Ethereum mainnet. The KHROME you trade on Uniswap.
L1 MainnetEtherscan ✓Sourcify ✓
KhromeBridge
L2 lock contract. User sends KHROME → relayer mints BridgedKHROME on mainnet.
L2 777001Halmos ✓Sourcify ✓
KhromeChain
Records anchor — signed entries, validator-voted finality.
L2 777001Sourcify ✓
KhromeVault
Encrypted file storage. Manifests on-chain, ciphertext off-chain (MinIO).
L2 777001Sourcify ✓
KhromeSubscription
Stake KHROME → unlock Vault tier (BASIC / PRO / ENTERPRISE). Fully refundable.
L2 777001Sourcify ✓
OperatorRegistry
KYC'd validator metadata + jurisdiction tags. Regulators read this.
L2 777001Sourcify ✓
AuditLog
Tamper-evident append-only log. Merkle-chained. Universal compliance primitive.
L2 777001Sourcify ✓
SanctionsScreen
OFAC / EU / UK sanctions registry. Bridge relayer reads before every transfer.
L2 777001Sourcify ✓OFAC-synced
04
The user flow.
The user flow.
From "never heard of crypto" to encrypted records on-chain.
01
Sign up at app.khromosome.network
Standard email signup — no wallet required to start. Supabase Auth on the back. Once they're in, the dashboard offers "Connect Wallet" — MetaMask, Trezor, WalletConnect, anything EIP-1193.
02
Get KHROME — three paths in
(a) Faucet drips 110 KHROME on first connection (enough to subscribe to BASIC). (b) Moonpay fiat onramp — credit card → KHROME → onchain in <5min (partnership pending). (c) Bridge ETH from mainnet via Khromeswap (BridgedKHROME ↔ ETH pool on Uniswap, post-seeding).
03
Stake KHROME → unlock a tier
BASIC (100 KHROME, 1 GB) · PRO (1,000 KHROME, 50 GB) · ENTERPRISE (10,000 KHROME, 1 TB). Stake is fully refundable — call unsubscribe() any time and get every wei back. No fee, no lockup, no vesting. The protocol earns yield by delegating the locked stake to validator pools.
04
Upload encrypted files to the Vault
Encryption happens in the browser. The vault server only ever sees ciphertext. Master key is derived from the user's wallet signature (no password ever). Per-file AES-GCM. Manifests anchored on-chain via KhromeVault. Auditors verify the trail without ever seeing the contents.
05
Run AI agents on your records (with consent gating)
Tax agent / clinical summary / actuary agent. Each one receives a scoped consent token, processes off-chain, returns an attestation hash. The user grants and revokes consent on-chain. Producers (your clinic, your bank) write records on your behalf with their own signing key, recorded against their OperatorRegistry entry.
06
Bridge out to mainnet — sanctions-checked
User calls bridgeOut on L2. Relayer detects, checks SanctionsScreen for sender + recipient, waits 8 L2 confirmations, then mints BridgedKHROME on Ethereum. Round trip: ~2 minutes. Sanctioned addresses: silently blocked, never minted. Bridge contracts both formally verified (15/15 invariants proven by Halmos SMT solver).
05
What makes us defensible.
What makes us defensible.
Six things competitors don't have.
A.
Identical stack to Ethereum mainnet
Reth + Lighthouse. Same PoS, same Casper FFG, same RPC, same Solidity. Every tool that works on Ethereum works on Khromosome — MetaMask, Foundry, Hardhat, ethers, OpenZeppelin. Zero developer education. Zero new tooling burden.
B.
Formally verified bridges
Both bridge contracts have 15/15 invariants proven by Halmos (SMT solver, a16z crypto research). "Only relayer can mint", "no replay", "conservation of value", "pause halts mints" — all mathematically proven, not just tested. Bridges are the #1 hacked surface in crypto; ours are math, not faith.
C.
Sanctions screening at the protocol layer
Bridge relayer reads SanctionsScreen.isSanctioned() before EVERY transfer. OFAC daemon syncs the U.S. Treasury list daily. Real-time compliance — not retroactive freezing. Regulated buyers (banks, fintechs) get a one-line answer: "all bridge transfers are OFAC-screened in real time."
D.
Source-verified at every layer
8/8 contracts on self-hosted Sourcify (exact_match — strongest tier). Mainnet bridge also verified on Etherscan with 39kb of source published. Releases signed via Sigstore. Code reproducible from any byte-of-bytecode upward.
E.
Hardware-backed validator keys
All 16 validator BLS keys signed through Web3Signer with Postgres slashing-protection. Compromised host can't sign for a key it doesn't hold. YubiHSM2 migration in progress — keys move from disk to hardware.
F.
Real bridge to Ethereum mainnet
Lock-and-mint, owner = Gnosis Safe controlled by hardware wallet, replay-guarded both ways. KHROME is real money the day a Uniswap pool seeds. Most "L1s" never get this far — they live in isolated testnet limbo. Khromosome's BridgedKHROME exists on mainnet TODAY.
06
The work so far.
The work so far.
~30 days from genesis to compliance-ready.
2026-04 → 05
Chain design + 87 Foundry tests + initial Reth + Lighthouse spec. Foundation milestones
A (single-node dev) + B (4-validator finality via Kurtosis) reached.2026-05-17
L1 production network LIVE — 4 nodes, 256 validators, real Ethereum-PoS finality across the Tailscale tailnet.
2026-05-18
Records-bridge (Supabase → KhromeChain) LIVE on ascend. Records-validator signs voteFinality. KhromeChain redeployed with explicit writtenAt.
2026-05-21
Mainnet bridge LIVE. BridgedKHROME deployed
0x6E34…68F6, etherscan-verified, 0.05 KHROME round-trip from L2 to mainnet confirmed.2026-05-25
Chain re-genesis to v2 (fresh validator mnemonic, 1B supply premined to Trezor cold storage). Watchdog systemd unit deployed for self-healing.
2026-05-26 → 28
Khrome Vault LIVE. Self-hosted Sourcify. Forta runtime monitoring. Sigstore release signing. Halmos formal verification of bridge contracts (15/15 proofs).
2026-05-29 → 31
Web3Signer Stage 1 LIVE on both hosts (16/16 validators behind remote signer). 3 compliance contracts deployed + Sourcify-verified. Bridge relayer wired to SanctionsScreen. OFAC sync daemon built (97 addresses ready). All-RPC endpoints behind Cloudflare proxy.
Next 30 days
Code4rena bridge audit · Vanta SOC 2 observation start · Delaware C-Corp formation · YubiHSM2 for relayer key · Uniswap pool seed · first commercial pilot.
07
The ask.
The ask.
Three doors. Pick the one that's yours.
Buyer
Run a 90-day pilot.
You're a clinical research org, a fintech, an audit firm, or a self-insured employer. You have records that need a tamper-evident trail and a story your compliance team will sign. We give you a dedicated Vault tenant, custom OperatorRegistry entries, and direct support. 90-day pilot, $25k, includes integration + your team trained. Production tier starts at $5k/month.
Book a pilot →Supporter
Run a validator.
You can host a Linux box with 8GB RAM + 200GB SSD and you want to be one of the named operators in OperatorRegistry — at minimum that's a credibility signal on your CV; eventually it's KHROME-denominated validator rewards from the ValidatorRewards pool. We onboard 2 more partners this quarter (target: 4-operator decentralization). Hardware help available if you need it.
Apply →Investor
$1M seed round.
We're raising $1M against a $10M cap (SAFE). Use of funds: (1) Code4rena bridge audit + SOC 2 Type II ($60k); (2) Three founding engineers ($600k/yr); (3) Sales hire for regulated verticals ($150k/yr); (4) Uniswap deep liquidity seed ($200k). 24-month runway, first paying customer within 90 days, $1M ARR target by month 18. Closed loop on a real chain, not a deck.
Request the deck →Joshua Dunn · Founder
joshuadanieldunn@gmail.com
· @Khromosome_xyz
· github.com/jdunn7
· Trezor multisig:
0x5301aEa2…b178a7