Skip to main content

Contract addresses

Contract addresses

Every 4626 contract address on Base, Solana, and spoke chains, with the current pins at the top and retired deployments at the bottom.

Addresses link to BaseScan on Base mainnet. New to 4626? Start at What is 4626?.

Deployment directory and dated observations

Use the verification block below when assessing observed state. Documentation labels do not override contract state. Resolve disagreements before treating a deployment as available for use.

$AKITA vault on Base​

The contracts that make up the live $AKITA creator vault. Vault, wrapper, and ShareOFT are the v1.27.0 receipt. The September 25, 2026 snapshot below is the previous listing. See activated vs trading live.

RoleAddressNotes
Creator coin (Zora AKITA)0x5b67…fa75The ERC-20 the creator deposits
Registry4626 (observed ShareOFT binding)0xB395…0B22Returned by this ShareOFT at the verification block; differs from the app registry below
CreatorShareOFT ()0x9788…4626Live v1.27.0 share token
CreatorOVault0x4626…3138Live v1.27.0 ERC-4626 vault
CreatorOVaultWrapper0x462b…Eb26Live v1.27.0 wrapper
CreatorGaugeController0x3A51…98A0Bound to the legacy vault, wrapper, and ShareOFT; not rebound to this vault
CreatorOracle0xC5c5…78ff
CCALaunchArm0x4f6B…A9EAFair-launch auction arm
Solana AKITA mintAKosgUJDaJ1MzquRPwfMTTzJG4w3SeQbNLvk3jcm4626Canonical until a replacement mint is verified. Token-2022, LayerZero share mesh
Solana LayerZero OFT Store5enyS14H31yHkMDHswCjK44ws2W3bLCmtfHWQTSMb7D5Canonical until the replacement store is verified

The Solana rows stay on AKos. A replacement Long Vault OFT is specified in docs/ops/akita-long-vault-oft-cutover.md and is not deployed. Update these rows only after that runbook's verification gate passes.

Other creators' vault, wrapper, ShareOFT, gauge, and oracle addresses are emitted during each launch. Look them up in that creator's deploy release packet or in the onchain launch events.

Verification — September 25, 2026​

Read-only observations at Base block 51,795,475, timestamp 2026-09-25 23:51:37 UTC. This is a historical snapshot, not a live readiness indicator. Deployment, funding, strategy configuration, deposits, auctions, trading, and bridging are separate states.

ComponentObserved state
Listed vault 0x4626…C5CdtotalAssets = 0, totalSupply = 0, strategyCount = 0, gaugeController = address(0)
Listed ShareOFT 0x57df…4626totalSupply = 0, gaugeController = address(0); registry 0xB395…0B22; native buy fee configured to 690 bps
Listed wrapper 0xB1B1…b691totalLocked = 0, totalMinted = 0; wrap and unwrap fees configured to zero
Listed vault, ShareOFT, wrapperEach owner() returned DeploymentBatcher 0x4973…ec8F
Gauge 0x3A51…98A0Bound to legacy vault 0x4dE4…61D7, wrapper 0x0D47…a200, and ShareOFT 0xe7e4…4626
Gauge lottery binding0x7777…4626, distinct from the documented current manager 0x7777CEd5…4626
Gauge voting and voter distributorBoth zero addresses; voter rewards are not configured for this gauge
Documented current lottery managerBoost and voting addresses both zero

These bindings do not establish a reconciled launch configuration. Cross-chain readiness and public deposit eligibility were not established by these reads. The Solana and auction entries elsewhere on this page include legacy deployments; they are not proof that the newly listed vault is bridged or trading. No contract was rebound during this review. Existing holder obligations require their own reconciliation.

The old claim that the new ShareOFT returns registry 0x7779…4626 is corrected here. Earlier homepage allocation claims and deck diagrams must not be read as active positions in this new vault. Verify fresh state and reconcile the component set before changing its status.

Shared infrastructure on Base​

These are documented protocol infrastructure pins; each launch must verify its actual bindings. For app lookups, always use the live Registry4626 in the first row.

ContractAddressNotes
Registry4626 (live)0x253B…4626Use this one. v1.27.0 CREATE2 ending in 4626. Confirm the receipt before treating it as live
Registry4626 (v1.26.0 app)0x7779…4626Rejected app pin after the v1.27.0 cutover
Registry4626 (greenfield)0xB395…0B22Rejected app pin. Earlier shells returned this from registry()
OVaultFactory46260x5440…4626v1.27.0 CREATE2 ending in 4626. registry() must be the live Registry
VaultActivationBatcher0xFB50…4626v1.27.0 CREATE2 ending in 4626
DeploymentBatcher0x485E…4626v1.27.0 CREATE2 salted by the registry above
DeploymentBatcherPhase1Module0x8751…4626
DeploymentBatcherPhase2Module0x40bF…4626
DeploymentBatcherPhase3Helper0xfE63…4626
DeploymentBatcherShareMeshHelper0x4a16…4626
DeploymentBatcherUtilsHelper0xAe58…4626
CreatorOVaultCoreModule0x2d3A…4626Creator core bound by Phase 1. Stable CREATE2
AgentOVaultCoreModule0x2d3A…4626Same module when AGENT_VAULT_CORE_MODULE is unset at deploy
CreatorOVaultStrategiesModule0x9388…4626
CreatorOVaultAdminModule0xf7f4…4626
LotteryManager46260x914D…4626v1.27.0 CREATE2 ending in 4626. Solana peer is this address padded to 32 bytes. Not retired: live registry 0x253Bb02E…4626 still returns this address. Shovel indexes this manager. 0xc05b36df…4626 is pre-fix bytecode and is not this pin
LotteryManager4626 (creator plane)0x7774…4626Deployed at Base block 52846451, tx 0x8c3a08fa7c2bce166d8eee0d0d5109f232f13e73d18534a9cc876c000c36bc43. Same LotteryManager4626.sol as c435b752. Not verified on Basescan. Admin module 0x1fEA…A460 is delegatecalled, so its events log from this manager. 0x9453B205…4626 has no code
LotteryManager4626AdminModule0xAcAE…4626v1.27.0 CREATE2 ending in 4626. Distinct from the creator-plane admin module 0x1fEA6534…
VRFConsumer46260xbDb7…4626v1.27.0 CREATE2 ending in 4626
UniversalBytecodeStoreV20x18AE…4626v1.27.0 store. Stable CREATE2. Empty on Base until seed
UniversalCreate2DeployerFromStore0x5d69…4626CREATE2 deployer on the v1.27.0 batcher
VaultAuxiliaryDeployBatcher0xFee5…4626Live v1.27.0 CREATE2. Do not reuse 0xC83587C7…

Things to know about these pins​

  • One live Registry. DeploymentBatcher.registry() on 0x485E0Aa1… must return 0x253Bb02E… after the broadcast. Never resolve app data through 0x777968CB… or 0xB395….
  • Core modules. The Phase 1 module binds creator core 0x2d3AA11C…. Agent core is that same module when the deploy leaves AGENT_VAULT_CORE_MODULE unset.
  • Lottery boost. Read boostManager and ve4626GaugeVoting on LotteryManager 0x914D24e2…4626 after deploy. The planned formula is in Lottery personal boost v2.
  • Parallel stack, not an upgrade. The AKITA vault above was deployed alongside earlier stacks. It is not an in-place upgrade of abandoned ones. Earlier addresses stay onchain for vaults that already use them but are not supported for new launches. See Deprecated.

Protocol Safes​

Safe accounts used to operate protocol contracts. At the verification block, each inspected Safe required only one owner signature; multiple listed owners do not imply a multiple-signature approval requirement.

RoleAddress
Protocol treasury Safe (cold custody, strategy ownership)0x7d42…f2d3
Protocol automation Safe (Charm manager, Ajna admin)0x08f0…8eBE
Protocol leverage Safe (retired factory owner; treasury-only)0xd352…13e8
  • At Base block 51,795,475, the treasury Safe was 1-of-3 and the automation Safe was 1-of-2. Safe modules and guards were not reviewed. The automation owners are keeper 0xed7e… plus the treasury for recovery. Phase 3 still wires the Charm manager and Ajna admin roles to it.
  • LeverageMarketFactory and createMarket are removed from source. Isolated 1x short does not deploy a market at vault launch. The retired leverage contracts are listed under Deprecated.

Free lottery entry (AMOE)​

AMOE (alternative method of entry) lets people enter the lottery without a purchase, using zero-knowledge proofs of attested points.

Contract / roleAddressNotes
LotteryAmoeRouter (live)0x4625…7a95Live on LotteryManager 0x7777CEd5…. Reuses PLONK verifier 0xcEA9e27c…. Publisher = protocol CSW 0x793c…
AmoePlonkVerifier (paired)0xcEA9…c229Shared with prior multi-entry routers
LotteryManager46260x7777…4626Canonical manager since the venue-notional CREATE2 cutover (2026-08-08)
Allowlist + ledger publisher0x793c…c145Protocol CSW. Must match onchain allowlistPublisher / pointsLedgerPublisher
Protocol AMOE creator coin (AKITA)0x5b67…fa75Default target for protocol-entry AMOE flows

Solana​

Solana has no EVM address for the Base CreatorShareOFT. Each creator gets its own Solana SPL mint and OFT Store, and LayerZero peer wiring joins them with the Base ShareOFT into one omnichain supply. The live AKITA Solana mint and OFT Store are in the $AKITA vault table.

The public token metadata for AKITA:

RoleAddress
Registry JSONhttps://4626.fun/tokens/akita-share.json
Attestationhttps://api.4626.fun/api/v1/assets/akita-share/attestation
Meteora DLMM pool976B92Sf3rUpfksxf825JD4LHSh31PeyoMNqRsGGDZPB
Hub ShareOFT (Base) listed in the JSON0xe7e4…4626

The hub ShareOFT in the metadata JSON is the earlier recovery-stack ShareOFT (see Deprecated), not the new AKITA ShareOFT 0x57df…4626.

LayerZero endpoints​

The LayerZero V2 endpoint and endpoint ID (EID) on each chain the share mesh can reach.

ChainEndpoint IDEndpoint address
Base301840x1a44…728c
Ethereum301010x1a44…728c
Arbitrum301100x1a44…728c
Unichain303200x6F47…DD5B (non-canonical EndpointV2)
Robinhood304160x6F47…DD5B (same CREATE2; different eid)
BSC301020x1a44…728c
Avalanche301060x1a44…728c

$AKITA fair-launch auctions across chains​

AKITA can run its fair-launch auction (CCA) on more than one chain. Base is the full hub. Each spoke chain gets only a remote ShareOFT, a thin CreatorOracle, and a CCA arm; the vault, wrapper, gauge, and Zora creator coin stay on Base.

Base, Arbitrum, and Robinhood are kept in parity on these pins: Registry 0x7779…4626, ShareOFT on Base 0xe7e44b29…4626, CreatorOracle 0xC5c51eBB…78ff, and the recovery-stack CCALaunchArm 0x4f6BcDAD…A9EA.

ChainchainIdLZ EIDStatus
Base845330184Full hub
Ethereum130101ShareOFT + oracle + CCA TBD
Arbitrum4216130110Live (pins below)
Unichain13030320ShareOFT + oracle + CCA TBD
Robinhood466330416ShareOFT + oracle + CCA TBD
Factory protocol fee must be zero

On every chain, the auction factory's protocol fee must be zero. CCALaunchArm.migrate() requires the swept currency to equal currencyRaised().

Arbitrum spoke (live 2026-07-29)​

RoleAddress
Registry4626 (spoke; not Base vanity)0xd83b…627c
ShareOFT0x6423…5740
CreatorOracle0xC5c5…78ff
CCALaunchArm0xf140…4469
SimpleSellTaxHook0xb797…4088

The price feeds each spoke oracle reads. L2s also check the sequencer uptime feed.

ChainETH/USD feedSequencer uptime
Ethereum0x5f4e…8419n/a
Base0x7104…Bb700xBCF8…6433
Arbitrum0x639F…a6120xFdB6…697D
Unichain0xBcE7…8CCan/a (decimals=18)
Robinhood0x78F3…d3A9n/a

Uniswap v4 PositionManager​

Used when a graduated auction seeds its liquidity position.

ChainPositionManager
Ethereum0xbD21…ee9e
Base0x7C5f…9bDc
Unichain0x4529…17bf
Arbitrum0xd88F…D869
Robinhood0x58Da…4Fa7

External contracts​

Third-party contracts 4626 integrates with on Base.

ContractChainAddress
Chainlink VRF CoordinatorBase0xd5D5…F634
WETHBase0x4200…0006
Sudoswap v2 pair factoryBase0x6051…8eb8
Sudoswap v2 XYK curveBase0xd0A2…037B
Sudoswap v2 fast routerBase0xa07e…5548

Release notes​

Version labels you will see in scripts, release packets, and older docs. A few terms first:

  • Greenfield: a fresh deployment of the shared contracts, rather than an upgrade of existing ones.
  • Remine: redeploying contracts at newly mined CREATE2 addresses. Remine-2 is the second such pass, used to recover the $AKITA stack.
  • Vanity: addresses mined to carry a recognizable pattern (here, 4626).
  • Epoch tag: a version label that names one deployment set.

In order from newest:

  • v1.26.0 / v1.26.0-v2pg3ers: the current new-vault CREATE2 namespace and grounded AKITA salt on the app-registry batcher. AKITA_DEFAULTS still names the deployed v1.25.1 registry vault until this salt is deployed.
  • v1.25.1-v232n60f: the deployed AKITA registry vault. Vanity Phase 1 deploy with vault prefix 4626 and ShareOFT suffix 4626. That deploy used the parked shell batcher; the live Registry is 0x7779…4626.
  • v1.24.0: prior page-default namespace. It is not the current salt. Remine-2 recovery addresses are under Deprecated.
  • v1.23.0: Phase 2 inventory epoch. Took over the label from v1.21.0; the v1.21.0 shell addresses were kept.
  • v1.21.0: greenfield shell that is still in use for factories and the batcher.
  • v1.20.0, v1.19.1 / v1.19.3, v1.18.0, v1.16.1-share-mesh: earlier greenfield stacks, each superseded by the next.
  • v1.17.0: partial broadcast, never wired for production.
  • v1.16.0, v1.14.1, v1.14.0: earlier batcher shells. v1.14.1 refreshed v1.14.0 and predates the share mesh; v1.16.0 lacks shareMeshHelper().

Deprecated​

The addresses below remain onchain. Their availability, backing, and redemption state require separate verification; a deprecated label does not settle existing holder claims. None of it is a supported target for new vault launches.

Earlier $AKITA addresses​

RoleAddressNotes
CreatorOVault (remine-2 recovery)0x4dE4…61D7Recoverable historical URL; keep links working
CreatorOVaultWrapper (remine-2 recovery)0x0D47…a200Recoverable historical URL
CreatorShareOFT (remine-2 recovery)0xe7e4…4626Still the hub variant in the metadata JSON
Solana AKITA mint (retired A6HB)A6HB5FWRjknVuMXpuwupr6QjZpsRSS98nBb1DW9dAZsHSuperseded by AKos…4626
Solana LZ OFT Store (retired Asa8)Asa8DaR3bxQCAb3io5pLcYHZK4t2SeMn5jGnb1YBoDWzSuperseded by 5eny…b7D5

Earlier shared infrastructure​

Epoch / labelRepresentative addressesNotes
v1.21/v1.23 greenfield Registry0xB395…0B22Superseded for app lookups by 0x7779…4626; still returned by the newly listed ShareOFT and DeploymentBatcher.registry() at the verification block
Greenfield LotteryManager0x2fC7…28CCStill pinned for batcher-era scripts
LotteryManager4626 (prior remine vanity)0x7777…4626Superseded in app documentation 2026-08-08; still bound to the legacy AKITA gauge at the verification block
v1.20.0 greenfieldRegistry 0xF60a1490…, batcher 0x83A9b248…, store 0x8599CA87…, CREATE2 0xdffB255…, LM 0x0fC6f30…Superseded by v1.21.0; existing vaults may still reference
v1.21.0 greenfieldSame shell addresses as the shared infrastructure tableSuperseded as a label by the v1.23.0 Phase 2 inventory epoch; shell retained
v1.19.1 / v1.19.3 greenfieldRegistry 0x1365e9…, batcher 0xa18169…, store 0xF96226…, CREATE2 0xe2a8aA…, aux 0xaA9229…Superseded by v1.20.0; existing vaults (incl. AKITA) may still reference
v1.18.0 greenfieldRegistry 0xDb8570…, batcher 0x02D7…, store 0xfa3e…, CREATE2 0x54660E…, aux 0xde93…Superseded by v1.19.1 greenfield; existing vaults may still reference
v1.16.1-share-meshRegistry 0x1eb9A3…, batcher 0xA9024e…, store 0x7D1029…Superseded by v1.18.0; existing vaults may still reference
v1.17.0 orphanRegistry 0x5646B5…, batcher 0xa4090F…Partial broadcast — never wired for production
v1.16.0 shellBatcher 0x1716…6D33Lacks shareMeshHelper()
v1.14.1 shellBatcher 0x660B…61c1Pre–share-mesh
v1.14.0 shellBatcher 0xa990…0651Pre–v1.14.1 refresh
Legacy AMOE router0xc57a…6b0av1.11 manager fan-out
Legacy lottery manager0x04CA…7Cf8Pre–v1.16.1 registry stack
Retired Twin SolanaBridgeAdapter0x9A61…Be60Historical onchain deployment only
Retired LeverageMarketFactory0x32FD…667ARemoved from source
Retired LeverageCreateMarketModule0xEaC5…4502Removed from source