Swept 2026-09-03 · explorer-confirmed
Cashflow · Fund HOT · x402 tiers

Genesis Conductor Verification Ledger

Every ETH and SOL address in the Genesis Conductor surface, classified by what verification actually applies to it. Three contracts need source verification. All three are on Base, none on Ethereum mainnet, and none exist on Solana. I could execute zero of them today — every one is blocked on missing source, not on access.

3 Base 8453 · unverified Deployed contracts, source not published. All deployed by the treasury EOA.
0 Ethereum mainnet Nothing of yours is deployed to chain 1. The open Etherscan tab is the wrong explorer.
0 Solana No .sol handle is minted and no Solana wallet exists. Nothing to verify yet.
Correction to canonical record

The gap page undercounts by two

“One contract is deployed and unverified — wQFLOP”

That line in Source Verification Gap (2026-08-26) is wrong. QFLOP 0xa8F5…59c7 and Genesis V3 0x8519…205E are also live, unverified contracts, both created by the same treasury EOA around 2026-01-24. The Base Treasury Sink registry lists Genesis V3 with a $0.00 balance, which reads like a dormant wallet — it is a contract with a startConductor() entry point. This closes part of the registry-bounded hole that page flagged.

Disposition A · action required

Source verification applies — and is blocked

Contracts you deployed, live on Base mainnet (8453), with no published source. Confirmed on BaseScan today.

wQFLOP · Wrapped QFLOP (ERC-20) 0x69262A2D7c92c074729823B654fE7E4Cdb749747
Unverified
Txs86,694 Deploy block43,929,079 Compiler (CBOR)solc 0.8.33 Optimizer runsunknown

Blocker: the original .sol was never recovered, and the metadata CID QmXjS5…cvjbb is unpinned — I tried three IPFS gateways, all 403 or timeout — so optimizer runs cannot be read. The repo is not publicly readable and Drive holds no matching source. Constructor arg is the treasury EOA, already encoded. Do not submit: a failed first attempt pollutes the verify queue, and the repo's foundry.toml pins 0.8.28, not the 0.8.33 the deployed bytecode declares.

QFLOP · QFLOP Quantum Computer (ERC-20) 0xa8F5e136aa74803B8DB377a14f79F6c8Dd3959c7
Unverified
Txs117 Creatortreasury EOA Age~222 days Compilernot yet read

Not in the gap page at all. The underlying token that wQFLOP wraps, and the thing the 267.35M supply figure is booked against. No source located. Read its CBOR metadata for the compiler before touching it — do not assume it matches wQFLOP's 0.8.33.

Genesis V3 · Conductor entry point 0x851936cA8874c05f1eDc2f5Fc2e6A3Cd97c7205E
Unverified
Txs1 Selector0x213a1ddd MethodstartConductor() Deployed2026-01-24

False lead ruled out. Drive holds Genesis.sol (310 bytes, saved 2026-01-24 — same day as deployment). It is not this contract. That file declares emitEvent() (0x7b0cb839) and CREDIT_PURCHASE; the deployed contract answers startConductor() (0x213a1ddd) and emits ConductorStarted(address indexed, uint256) — I recomputed the keccak of that signature and it matches the on-chain topic0 0x425845ef… exactly. Submitting the Drive file would fail. The operator recorded in that event is the MPC Vault, not the treasury.

Disposition B · no action

Verification does not apply

Wallets have no source to publish; undeployed contracts have nothing to verify against. Neither is verification work.

Treasury / profit sink — EOA 0x9545e2439c5c75d3aA723AcaC1AA6B0fa1DB6956
Wallet
Txs3,079 Balance0.0000072 ETH Deployer ofall 3 unverified contracts

Flag, unrelated to verification: BaseScan shows a MetaMask EIP-7702 delegator set on this address. A treasury EOA carrying delegated code is worth a deliberate review — confirm you set it, and that the delegate is what you think it is. Separately, the ETH balance is effectively drained.

W0 Prover · W1–W3 Wrappers — EOAs 0xb154Ad4D467dBa90bdDa1979c48Ff37Bb23f47D6 · 0x3b3E5FbDC1A6775C1734F4F711103867e11001Ef · 0x4284BaF799280874b18B0B5CDeE7A778660A12a9 · 0xd16785614f7Ea54B314BF1E8E9d5CD11EB714c5D
Wallets
Verificationnot applicable
Booster v2.0 triad — never deployed EulerCycleAttestorV2.sol · SupportEscrow.sol · ImplicitAgreement.sol
Not deployed
StageContract Compilation StatusPending Tx hashempty

Verification is post-deployment. The 2026-07-10 Claim Validation flagged EulerCycleAttestorV2 as “deployment asserted”; the Deployment Tracker still carries no tx hash. Prior lock stands — these are not verification work until an address exists. Full ImplicitAgreement source does sit in a Drive doc, so the eventual verification will not have wQFLOP's source problem.

Solana handles — unminted maru.sol · yennefer-treasury.sol · kovach-enterprises.sol
Pending mint
Addresses0 Off-ramp partnernot selected (F5)

Two of the three are marked “proposed handle, not reserved.” No Solana wallet has been created, no SNS transaction signed. Your own anti-fabrication gate (Greg × /maru R2) forbids claiming otherwise until Phase 4 closes with a verified_by annotation. The blocked step here is minting, not verification — and whether maru.sol is already taken by a third party is still an open question that decides the fallback chain.

Disposition C · not yours

Already verified, by someone else

Correctly excluded from your verification scope. Listing them so they stop reappearing as candidates.

ContractAddressStateOwner
Aerodrome WETH/wQFLOP pool 0x4aBC6D796cd036b6f1E433A97F9784a00f90C53e Verified · Minimal Proxy Created by 0x05bBe7C3…758F — Aerodrome, not you
Aerodrome Router 0xcF77a3Ba9A5CA399B7c97c74d54e5b1Beb874E43 Verified Aerodrome protocol
Aerodrome Pool Factory 0x420DD381b31aEf6683db6B902084cB0FFECe40Da Verified Aerodrome protocol
WETH (Base) 0x4200000000000000000000000000000000000006 Verified Base predeploy
Justification trace

Why nothing was submitted

  • Source verification — blocked on source, not access. Verification needs a build that reproduces the deploy-time bytecode. For all three contracts the source is missing. I searched the Notion registries, Google Drive (full-text, including pragma solidity and startConductor), Slack, three IPFS gateways for the metadata CID, and the referenced repo. The only Solidity that surfaced was an earlier draft that provably is not the deployed Genesis V3. Fail-closed: I stalled rather than submit a guess that would burn the queue.
  • Address-ownership verification — not mine to perform. That flow proves control by signing a message with the address's private key. I don't handle private keys or wallet signatures. You sign that one yourself; it takes about a minute.
  • The open tab is the wrong door twice over, exactly as your own gap page concluded: etherscan.io/myverify_address proves ownership and publishes no source, and the contracts are on Base rather than Ethereum. BaseScan runs its own separate ownership flow.
  • Candidates considered and rejected: decompile-and-reconstruct (produces bytecode that will not match — worse than not submitting); bytecode-similarity search for a verified twin whose source you could reuse (BaseScan's similar-contracts endpoint returned 403 — still worth one manual look in the browser); submitting with the repo's foundry.toml settings (0.8.28 against deployed 0.8.33 — guaranteed failure).
Next actions

What unblocks each one

Ranked. The first item unblocks two of the three contracts and is the only one that needs you specifically.

  • Find the deploy machine. The source existed on whatever box ran the deploys on 2026-01-24 and 2026-03-27 — a Foundry out/ or cache/ directory, a Remix workspace in browser storage, or a Hardhat artifacts folder. Any one of those carries the standard-json-input with the exact optimizer runs, and that is the whole blocker. Link this session to that computer and I can sweep it directly.
  • Close the registry hole properly. Neither BaseScan's UI nor the free explorer APIs would enumerate contract creations for me — Blockscout 500'd, Routescan doesn't serve chain 8453. One authenticated call with your existing key settles whether there is a fourth unrecorded contract:
# every tx from the treasury EOA; contract creations have an empty "to"
curl -s "https://api.etherscan.io/v2/api?chainid=8453&module=account&action=txlist&address=0x9545e2439c5c75d3aA723AcaC1AA6B0fa1DB6956&startblock=0&endblock=99999999&sort=asc&apikey=$ETHERSCAN_API_KEY"   | jq -r '.result[] | select(.to == "") | [.contractAddress, .blockNumber, .hash] | @tsv'
  • Then, and only then, one shot at wQFLOP. Fill in the real optimizer runs — do not guess 200:
forge verify-contract   --chain 8453   --compiler-version 0.8.33   --optimizer-runs <FROM_METADATA>   --constructor-args 0000000000000000000000009545e2439c5c75d3aa723acac1aa6b0fa1db6956   0x69262A2D7c92c074729823B654fE7E4Cdb749747 <ContractName>

# ETHERSCAN_API_KEY is chain-agnostic — no separate BaseScan key needed.
# Dry-run first with --show-standard-json-input and diff against the CBOR metadata hash.
  • Verify treasury ownership on BaseScan, not Etherscan — that is what earns the name tag and token-info edit rights on wQFLOP and QFLOP, which is the public-credibility half of this. You sign it in-wallet at basescan.org/verifyAddress.
  • Check the EIP-7702 delegation on the treasury before anything else touches it.
Risks & limits

What this ledger does not establish

  • Enumeration is still registry-bounded. A contract deployed and never written into Notion is not on this page unless it happened to be one of the three I could check. The txlist sweep above is what actually closes it.
  • QFLOP's compiler is unread. I confirmed it is an unverified contract; I did not pull its CBOR metadata. Treat its build settings as unknown, not as wQFLOP's.
  • Solana is asserted from your own canonical pages, not from an SNS lookup — the Bonfida resolver endpoints returned 404 for me. "Zero addresses" is well-evidenced by the Integrative Flow and /maru Phase 4 gates, but whether maru.sol is already registered to a third party is unconfirmed.
  • PRODUCTION ≠ Verified. Pipeline Ops marks wQFLOP live because LIVE_EXECUTE=TRUE. That is execution state. Nothing here claims source verification on any explorer, and no page should until a submission succeeds.
  • Re-evaluation triggers: deploy-machine artifacts recovered · the metadata CID gets pinned · a Booster triad row gains a tx hash · any new contract creation from the treasury.