0x999111D1AFc0fA233893b2D3956092C1DDDddddD0x999111D1AFc0fA233893b2D3956092C1DDDddddD

Why it’s rare

On one CPU core, about 140 days

Each line is the chance that a random address has that pattern. We divide by 6 at the end because an address doesn’t need these exact patterns to be this rare; several others would do. The CPU time is only for a sense of scale: one core tries about 243,000 keys a second. How we work this out

How to deploy to this address

You get the private key of a fresh deployer. The first contract it deploys lands on the address above, on any EVM chain you deploy it to.

Deployer 0x6F9E3d033E2189f870EF9369478E6280BF9cCfd5

1. 1Send the deployer just enough native token to pay for the deployment.
2. 2Check its nonce is 0: cast nonce 0x6F9E3d… --rpc-url $RPC
3. 3Deploy your contract as its very first transaction. Any other transaction first, even a test, uses up the address for good.

After you pay

• Your order page shows the private key as soon as the payment confirms, usually within minutes. Copy it, or save it as a password-protected file MetaMask can import.
• Before you see it, we check the key really controls the deployer and this contract address. If it didn’t, you’d get a refund, not a broken key.
• The address comes off the shop the moment you pay. You see the key once, and right after that we delete our encrypted copy for good. How we handle keys
• You can send and receive on any EVM network right away; there’s nothing to register.