Is this a token sale?
DOA solidification refers to protocol, registry, and custody—not an offer of securities. Any token would be a separate, disclosed process.
Base mainnet · chain 8453
Genesis Conductor DOA — On-chain orchestration authority
Genesis Conductor solidifies Decentralized Orchestration Authority (DOA) on public mainnet (Base)—metered AI skills, escrow, and, as components ship, protocol governance—bound to the same research identity (ORCID, Zenodo) and platform stack (Google · Anthropic · Notion · Shopify).
1. Why DOA
Scientific and agentic systems need more than prompts: they need accountable orchestration—who paid, which skill ran, what it cost, who can upgrade the rules. DOA is that layer for Genesis Conductor.
2. Bound identity
| Off-chain | On-chain (mainnet) |
|---|---|
| Igor A. Holt · ORCID 0009-0008-8389-1297 | Admin / vault addresses — see registry when published |
| Genesis Conductor · genesisconductor.io | Protocol / vault / oracle addresses on Base |
| Zenodo DOIs | Skill IDs (bytes32) + IPFS packages |
3. Protocol components
Target mainnet components (names are architectural; an address is listed only once it is live on a production chain):
- Not yet deployed
YenneferProtocol
entrypoint
- Not yet deployed
EnterpriseEscrowVault
USDC credits, bonds, settlement
- Not yet deployed
SkillCostOracle
dynamic skill pricing
- Not yet deployed
Skill registry
decentralized skill metadata + metering
4. Networks & addresses — mainnet only
Publication rule: a row is allowed only if (a) chain is a production mainnet and (b) the address is a live contract or canonical token on that chain. Testnet rows are omitted, not marked pending.
| Network | Chain ID | Contract | Address | Explorer | Status |
|---|---|---|---|---|---|
| Base | 8453 | Genesis v1 (Yennefer body / CREDIT_PURCHASE) | 0x542db00D9c83F4444cAD5353D1580D97baFaBb50 | Basescan | Verified source · name Genesis |
| Base | 8453 | USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 | Basescan | Canonical Circle USDC |
| Base | 8453 | Genesis v3 | 0x851936cA8874c05f1eDc2f5Fc2e6A3Cd97c7205E | Basescan | Contract live · source not yet verified |
Related Base mainnet wallets (ops, not protocol)
| Role | Address | Note |
|---|---|---|
| Ops wallet (owner of Genesis v3) | 0x029472221aBa41446821777136eB82Ad171D04e6 | EOA · owner of Genesis v3 |
| Legacy minter | 0x9545e2439c5c75d3aA723AcaC1AA6B0fa1DB6956 | EOA · deployer/owner of Genesis v1 |
5. Platforms & DOA
Platforms we build on accelerate real-world delivery; DOA makes orchestration inspectable. We do not replace research identity with tokens—we anchor it. Settlement asset on the public page is mainnet USDC, not a project token.
6. FAQ
Which chain is authoritative?
Base mainnet (chain ID 8453). Testnet deployments are rehearsal only and are not shown on this page.
How does this relate to Genesis Conductor research?
Research defines how to orchestrate intelligently; DOA defines how orchestration is accounted for on-chain. The research side is published openly as working papers on Zenodo under ORCID 0009-0008-8389-1297.
Where is source?
Genesis v1 source is public in the Yennefer engineering repo at contracts/Genesis.sol, identical to the verified source on Basescan. Further contracts will be published, and their bytecode verified on explorers, as components deploy.