Deployments

Seed Protocol's contracts are deployed on OP Sepolia (chain ID 11155420), an Optimism testnet. They're built with solc 0.8.38, EVM target cancun. There's no mainnet deployment yet (Roadmap). With this bytecode, deployer and salt, SeedProtocolExecutor would land at the same address on mainnet; the extensions take the EAS address as a constructor argument, so theirs would differ. The contracts repo's Ignition record (ignition/deployments/chain-11155420/) is the source of truth for these addresses.

OP Sepolia

The three Seed contracts were deployed with CREATE2 through CreateX, with a salt only Seed's deployer can use. The contracts repo's deploy log records source verification on Etherscan and Sourcify; the checks below don't cover that. The publish package has the factory and the EAS predeploys built in for OP Sepolia; you set the executor yourself with modularAccountModuleContract (see Publish overview). You never send anything to the extension or router extension addresses directly: your account runs their code.

How these were checked

Every row above has contract code on OP Sepolia (eth_getCode). These read-only calls, made on 2026-10-30 against https://sepolia.optimism.io (block 50,799,058), show the configuration:

You can repeat any of them with cast call (Foundry) or any JSON-RPC client. For example:

cast call 0x76F47D88bfaf670F5208911181fCDC0E160cb16d \
  "getImplementationForFunction(bytes4)(address)" 0xa1263421 \
  --rpc-url https://sepolia.optimism.io
# 0x851C5527240CAD1f6839B1379c5A348b59B14437

At runtime, the publish package's verifyPublishChain() checks that the RPC serves the configured chain and that the EAS, SchemaRegistry, factory and executor addresses have code, readFactorySeedExecutor() reads which executor and EAS the factory's router extension trusts, and assertMultiPublishRouted(target, { executorModule }), which a contract publish runs first, fails with MULTI_PUBLISH_NOT_ROUTED when the target doesn't have the multiPublish the package sends (MULTI_PUBLISH_SELECTOR).

History

The current contracts went live on 2026-10-30, when the factory's routing switched to them in one multicall (block 50,793,041, 0xbcc3a306…6617). They add the three-phase multiPublish (selector 0xa1263421), references to list elements and an exact msg.value check, and the install record now stores the executor's address. @seedprotocol/publish 0.8.0 is built for them. Releases from 0.6.9 to 0.7.13 send 0x2a29fadc, which isn't routed any more, so they can't publish through a ManagedAccount; direct EAS, reads and item.unpublish() still work. Each account's admin installs the new executor, and session keys are granted again (After the factory moves to a new executor).

The set before that went live on 2026-10-03, in one transaction (block 49,632,889, 0xce3b77ed…e314). It replaced an extension whose multiPublish had no caller check and which exposed setEas, and it added the router extension. @seedprotocol/publish releases before 0.6.9 were built for the earlier contracts. As of 2026-10-18, three accounts had installed that set's executor (the first on 2026-10-04) and none had uninstalled it. The number of accounts still on it today hasn't been read.

What's left of the rollout is in Seed's own apps and test accounts; see Roadmap.

Not in use

These addresses on OP Sepolia hold Seed code but aren't routed by the factory. Don't install, route or point an app at any of them. The implementations from before 2026-10-03 have known access-control bugs.

@seedprotocol/publish also exports MULTI_PUBLISH_ABI_REFERENCE_ADDRESS_OP_SEPOLIA, 0xcd8c945872df8e664e55cf8885c85ea3ea8f2148, marked internal, with a comment that says not to send transactions to it. It isn't part of the deployment above, and it's a 45-byte clone whose code has no 0xa1263421, so the multiPublish the package sends isn't there.

Other chains

OP Sepolia is the only network with a deployment. Addresses on another chain would differ for the extension and the router extension, because the EAS address is a constructor argument and EAS isn't at the same address everywhere. Deploying to a new chain walks through the process, and Local twin covers the local fork of OP Sepolia, which runs under chain ID 31337.

Related

• Contracts overview
• Base schemas: the EAS schemas the protocol registers
• Deploying to a new chain
• Publish overview: managedAccountFactoryAddress, modularAccountModuleContract and verifyPublishChain