Hey ZeroDev team! 👋
First off — Kernel is awesome. The modular ERC-7579 architecture, the WebAuthn validator with duo-mode P256, the weighted multisig, session keys — it's exactly the kind of infrastructure the ecosystem needs. We've been going through the codebase and audits and are really impressed with the quality.
What we're building
We're building FlowIndex, a block explorer and developer platform for Flow. We're adding a passkey-powered smart wallet (WebAuthn + ERC-4337) using Kernel v3, and we'd love to have canonical contract addresses on Flow EVM for cross-chain wallet portability.
Current state on Flow EVM
Your deployer (0x9775...) has already deployed v3.0 and v3.3 core contracts on mainnet (chain 747):
| Contract |
v3.3 Address |
v3.0 Address |
Mainnet |
Testnet |
| Meta Factory |
0xd703aaE79538628d27099B8c4f621bE4CCd142d5 |
same |
✅ |
❌ |
| Kernel |
0xd6CEDDe84be40893d153Be9d467CD6aD37875b28 |
0x94F097E1ebEB4ecA3AAE54cabb08905B239A7D27 |
✅ both |
❌ |
| Factory |
0x2577507b78c2008Ff367261CB6285d44ba5eF2E9 |
0x6723b44Abeec4E71eBE3232BD5B455805baDD22f |
✅ both |
❌ |
What's missing
Validators/plugins — not deployed on either network:
- ECDSAValidator (
0x845ADb2C711129d4f3966735eD98a9F09fC4cE57)
- WebAuthnValidator (
0x7ab16Ff354AcB328452F1D445b3Ddee9a91e9e69)
- WeightedECDSAValidator
- Recovery, session key plugins
v3.3 on testnet — core contracts also need deployment there.
We need canonical addresses so our users get the same wallet address across chains.
Gas is covered
- Mainnet: your deployer already has ~114 FLOW
- Testnet: we sent 110 FLOW to your deployer (
0x9775...)
Chain details
|
Chain ID |
RPC |
| Mainnet |
747 |
https://mainnet.evm.nodes.onflow.org |
| Testnet |
545 |
https://testnet.evm.nodes.onflow.org |
Arachnid CREATE2 proxy (0x4e59...) is available on both chains.
If there's a self-service way to do this (Orchestra?), happy to handle it ourselves — just point us in the right direction.
Thanks for building such a great stack! 🙏
Hey ZeroDev team! 👋
First off — Kernel is awesome. The modular ERC-7579 architecture, the WebAuthn validator with duo-mode P256, the weighted multisig, session keys — it's exactly the kind of infrastructure the ecosystem needs. We've been going through the codebase and audits and are really impressed with the quality.
What we're building
We're building FlowIndex, a block explorer and developer platform for Flow. We're adding a passkey-powered smart wallet (WebAuthn + ERC-4337) using Kernel v3, and we'd love to have canonical contract addresses on Flow EVM for cross-chain wallet portability.
Current state on Flow EVM
Your deployer (
0x9775...) has already deployed v3.0 and v3.3 core contracts on mainnet (chain 747):0xd703aaE79538628d27099B8c4f621bE4CCd142d50xd6CEDDe84be40893d153Be9d467CD6aD37875b280x94F097E1ebEB4ecA3AAE54cabb08905B239A7D270x2577507b78c2008Ff367261CB6285d44ba5eF2E90x6723b44Abeec4E71eBE3232BD5B455805baDD22fWhat's missing
Validators/plugins — not deployed on either network:
0x845ADb2C711129d4f3966735eD98a9F09fC4cE57)0x7ab16Ff354AcB328452F1D445b3Ddee9a91e9e69)v3.3 on testnet — core contracts also need deployment there.
We need canonical addresses so our users get the same wallet address across chains.
Gas is covered
0x9775...)Chain details
https://mainnet.evm.nodes.onflow.orghttps://testnet.evm.nodes.onflow.orgArachnid CREATE2 proxy (
0x4e59...) is available on both chains.If there's a self-service way to do this (Orchestra?), happy to handle it ourselves — just point us in the right direction.
Thanks for building such a great stack! 🙏