Skip to content
Protean

Live on Base Mainnet

Public sequence.
Public proof.

Protean's provenance layer has three parts. Published candidate and family records expose full sequences, sequence hashes, lineage, attribution, and provenance. The private vault still holds operational material — raw spectra, salts, scoring internals, embeddings, and unreleased assay data. The Protean Ledger on Base Mainnet is the canonical public record: typed records, typed lineage edges, lifecycle and disclosure state, content digests, replay pointers, and publication attestations.

The chain stores existence, timing, attribution, and integrity. It does not store secrets. The treasury wallet holds governance authority. The operator EOA holds only operational write roles. Bankr — the automation wallet — holds exactly AUTOMATION_WRITER_ROLE and refuses to broadcast without a single-use, 5-minute-TTL operator approval token. Compromise of the operator wallet does not compromise governance.

Live on Base Mainnet · chainId 8453

Protean Ledger — canonical scientific record

View on Basescan Download ABIImplementation
Network
Base Mainnet
Chain ID
8453
Schema
protean.ledger.v1
Deployment block
46,837,000

Proxy

0xE3c261F3C05D4c4710003cd6066EfD95094cf5f0
RPC unreachable · showing build-time state from 44 days ago

00—Canonical scientific ledger

The chain is the source of truth.
The mirror is supplemental.

The Protean Ledger is a separate, content-addressed scientific ledger deployed on Base Mainnet. Every record (RuntimeCycle, Hypothesis, Experiment, Thesis, ScientificAsset, IPAsset, and eight others) is a typed envelope with a deterministic recordId. Every relation between records is a first-class on-chain edge. Lineage, supersession, and retraction are events the contract emits and any indexer can re-derive.

Contract

0xE3c261F3C05D4c4710003cd6066EfD95094cf5f0

Proxy · ERC1967 · UUPS · verified on Basescan

Verified source on Basescan

Indexer digest

Every page on protean.sh/ledger publishes a sha256 over the canonical-bytes of the confirmed indexer state. The same digest must reproduce from any public Base RPC using the open-source script in the mirror — that is the architectural reproducibility commitment.

Live digest endpoint

Public verification mirror

The mirror at proteanlabs1/ledger-mirror is a public distribution surface, not a source of truth. It holds the schema, role topology, contract ABI, deployment metadata, per-record JSON artifacts, the canonical indexer script, and the verification manifest — nothing else. The Protean Labs private repo is never exposed.

A second supplemental rail replicates approved public artifacts to Gitlawb across protean-ledger, protean-papers, protean-governance, and protean-research. Like the GitHub mirror, it is a public distribution surface, not a source of truth — sensitive artifacts never replicate automatically, and a mirror failure never invalidates a Ledger write.

Each artifact in the mirror is sha256-addressed. Records that postdate the mirror cite a real artifact hash in their on-chain replayPointer; the four bootstrap records (genesis + activation cycle + reproducibility hypothesis + launch package v1.0) predate the mirror and surface a "Historical Bootstrap Record" badge on the explorer.

Independent re-index

Reconstruct the ledger digest from genesis on any machine, against any Base Mainnet RPC, with no Protean infrastructure on the path:

curl -sL https://raw.githubusercontent.com/proteanlabs1/ledger-mirror/main/scripts/index_ledger_from_genesis.py -o index_ledger.py

python3 index_ledger.py \
  --rpc https://mainnet.base.org \
  --proxy 0xE3c261F3C05D4c4710003cd6066EfD95094cf5f0 \
  --db protean.db \
  --from-block 46837000 --once

python3 index_ledger.py --digest-only --db protean.db

Match against /ledger/api/v1/indexer/digest. If the digests match, you have just reproduced the entire ledger state without trusting us.

01—Ledger status

Live state,
fetched at request.

The proxy and implementation addresses, role posture, recent Ledger events, and indexed record/edge counts are read from the deployed Ledger or its current indexer snapshot. If the live indexer is unavailable, the page may show a build-time V1 export only as historical fallback, never as canonical truth.

Deployed Ledger

Protean Ledger

Base Mainnet · chain 8453

Proxy address0xE3c261F3C05D4c4710003cd6066EfD95094cf5f0
Current implementation0xf343dC86b186D2A1C7A052252D150672308854c4
Proxy deployment tx0xca9f68ac031d651a…73f90e06cb

Ledger state

Upgradeablesource · live ledger/indexer

Upgrade authority is controlled by Ledger roles. If this panel is showing historical fallback data, upgrade details are archival and not the source of current truth.

RuntimeCycle / record root0xad73a17f29391ece…edbccf22
Ledger transaction0x4ccbad6b9bd4a3…b8a763cd
Indexer digest0x1d8c272d6386bb3fe2…9c9e8a43
Indexed records / edges4/4 objects · 2/2 edges

Recent Ledger events

On-chain event trail

Every state-changing call to the Protean Ledger leaves an event log. The list below is read from live Ledger/indexer state. Historical entries are archival context, not the current source of truth.

02—Live provenance graph

One cycle, every typed
scientific object.

The Provenance Atlas maps what Protean has publicly committed: a ledger timeline and typed object lanes for runtime cycles, candidates, hypotheses, evidence, and assets. Select any record to see its relationships and full public proof — published candidates show full sequences, hashes, and lineage. Private salts, raw spectra, embeddings, and scoring internals remain outside the public artifact, and provenance proves lineage and publication state, not biological validation.

Source · live ProteanLedger · 0xE3c261F3C05D4c4710003cd6066EfD95094cf5f0 · 253 records · 38 edges

Provenance Atlas

Public proof, indexed by the Protean Ledger

A scalable map of what Protean has publicly committed: runtime cycles and the candidates, hypotheses, evidence, and assets they produced. Canonical on Base mainnet (0xE3c261F3…); this view reads the public indexed Ledger graph (253 records, 38 links).

118candidates18hypotheses52evidence40assets

Ledger timeline

Typed object lanes

Overview

Start from a runtime cycle, a lane, or search.

Every public scientific object is produced during a runtime cycle and committed to the Protean Ledger. Open a lane to browse a class of records, or select any record to see its relationships and full public proof.

The Protean Ledger on Base mainnet is canonical. Public exports and replay artifacts are supplemental proof surfaces. Provenance records existence, timing, integrity, lineage, and publication state — not biological validation.

Published candidates · full sequences and commitments

rank 5

20260608T175356Z-004

MAIEQHHKPQENQDNHDE

medium signal

rank 6

20260608T175356Z-008

KPADSQHHNQNHQQDPHMG

medium signal

rank 3

20260608T175356Z-003

IEHSTNPHQQDNHMA

medium signal

rank 1

20260608T175356Z-001

IEHQPPHQQDPHMA

medium signal

rank 10

20260608T175356Z-031

WPIWQPHQTQCGQGGGC

medium signal

rank 2

20260608T175356Z-002

IEHQPEHQPNHQQDPHMG

medium signal

rank 4

20260608T175356Z-034

DEQWPPADSHPEHQPGC

medium signal

rank 7

20260608T175356Z-032

CPPSNSSAVANACNQPNS

medium signal

rank 8

20260608T175356Z-018

HQMAQHCDDCDQFPTDCG

medium signal

rank 9

20260608T175356Z-019

GHQMPCGGQQHCDKA

medium signal

03—What is on chain

Commitments and pointers
— never secrets.

Written to the Ledger

  • Record IDsdomain-separated keccak256 (PROTEAN_LEDGER_RECORD_V1)
  • Content digestkeccak256 over the canonical envelope
  • Lineage edgestyped RelationType, first-class on chain
  • Candidate publicationsfull sequence + hash + signed attestation
  • Lifecycle state10-state Solidity enum
  • Runtime cyclesRecordRegistered + RecordContentEmitted events

Kept in the private vault

  • Raw spectra or proteomics binaries
  • Private salts
  • Scoring internals and adaptive weights
  • Embedding vectors
  • Unfiled IP and unreleased assay data

The chain records existence, timing, and integrity. It does not record biological activity. Committing a candidate proves the candidate existed and was committed at a specific moment. It does not prove the candidate works.

Read the provenance architecture

Boundary

On-chain publication is a commitment mechanism, not a truth oracle. Wet-lab validation and human scientific review remain the authoritative downstream layer.