GENESIS
Current
8-char suffix
Target: face4663 — the foundational identity suffix.
Difficulty: 2^32
~4.3 billion attempts
[ 0x01 / CONTRACT IDENTITY LAB ]
FACE4663 RESEARCH
FACE4663 CONTRACT
IDENTITY LAB
An open research lab exploring contract identity on-chain — how addresses are generated, how rarity is measured, and how recognizability can become verifiable identity.
Understand the address. Measure the rarity. Verify the identity.
[ 0x02 / PATTERN CALCULATOR ]
VANITY PATTERN CALCULATOR
CALCULATE THE COST
OF A VANITY ADDRESS
Estimate difficulty, time, and probability for mining a vanity contract address with specific prefix/suffix patterns.
RESULTS
Pattern Type—
Locked Hex Chars0
Difficulty (2^n)1
Avg Attempts (16^n)1
Rarity1 in 1
Avg Search Time—
Median Time (50%)—
90% Probability Time—
Prob ≤ 1 min—
Prob ≤ 1 hr—
Prob ≤ 1 day—
Prob ≤ 1 week—
Mining is probabilistic — actual time may vary. These are statistical estimates, not guarantees.
[ 0x03 / ADDRESS INSPECTOR ]
ADDRESS INSPECTOR
INSPECT ANY ADDRESS
FOR UNIQUE PATTERNS
Analyze an address structure and compare it against an explicit prefix or suffix target.
Full Address—
Validity—
Char Count—
First 4—
First 8—
Last 4—
Last 8—
Leading Zeros—
Trailing Zeros—
Target Pattern—
Target Mode—
Pattern Length—
Match—
Difficulty—
Average Attempts—
Rarity—
⚠ Visually interesting ≠ authentic identity. Always verify origin on-chain independently.
[ 0x04 / KNOWLEDGE BASE ]
EDUCATIONAL REFERENCE
UNDERSTAND
CONTRACT IDENTITY
01 What Is a Vanity Contract Address?
A vanity contract address is a smart contract address that contains a recognizable prefix or suffix — like 0xface...4663 or 0x...face4663.
The address is generated by searching through many possible deployment parameters (typically CREATE2 salts) until one produces an address matching the desired pattern.
Important: A vanity address does not change the contract's functionality, security, or behavior. The contract code is identical regardless of the address. It is purely cosmetic — but cosmetics can become identity.
02 Prefix vs Suffix Patterns
Prefix pattern: The address starts with specific characters after 0x. Example: 0xFACE4663...
Suffix pattern: The address ends with specific characters. Example: 0x...face4663
Key difference: Each additional hex character you lock adds 4 bits of difficulty, making the search 16× harder per character.
| Chars | Difficulty (16^n) | Avg Attempts |
|---|---|---|
| 4 | 65,536 | 65,536 |
| 6 | 16,777,216 | 16,777,216 |
| 8 | 4,294,967,296 | ~4.3 billion |
Prefix and suffix patterns have the same statistical difficulty when they lock the same number of hexadecimal characters. Suffixes are often chosen for branding because they appear like a signature at the end of an address.
03 Valid Hex Characters
Ethereum addresses use hexadecimal encoding. Valid characters after 0x are:
01234567 89abcdef
That's 16 possible values per character position. Hex addresses are case-insensitive on EVM chains — 0xABCD and 0xabcd refer to the same address.
Characters like g, h, x, y, z are invalid in hex strings and will be rejected by this lab's tools.
04 CREATE2 Salt Mining
The CREATE2 opcode allows deterministic address generation. The deployed address is calculated from three inputs:
address = keccak256(0xff ++ factory ++ salt ++ keccak256(initCode))[12:]
This means you can compute the address before deploying, and search for a salt value that produces a desired pattern.
The mining process:
- Fix the factory address and init-code hash
- Try different salt values (usually starting from 0 and incrementing)
- Compute the CREATE2 address for each salt
- Check if the address matches the target pattern
- When found, deploy with that specific salt
The speed of this search depends on hashing throughput — Optimized GPU miners can test hundreds of millions to billions of candidate salts per second, depending on hardware and implementation.
05 CREATE2 vs CREATE
CREATE
- Address Factors
- Deployer address + deployer nonce
- Predictability
- Can predict before deployment (if nonce is known)
- Pattern Control
- Possible through deployer-key search at a selected nonce, but operationally less convenient than CREATE2
- Deploy Cost
- Standard gas
- Key Risk
- The intended nonce must remain unchanged. Any earlier transaction or deployment from that wallet can change the resulting contract address
CREATE2
- Address Factors
- Factory address + salt + init-code hash
- Predictability
- Fully deterministic from inputs
- Pattern Control
- Full control via salt mining
- Deploy Cost
- Similar to standard deployment, with additional hashing cost for the init code
- Key Risk
- Changing any input changes the address entirely
CREATE2 enables vanity address mining because the salt parameter can be any 32-byte value, giving 2^256 possible addresses to search through.
06 Why Difficulty Grows Fast
Each hex character has 16 possible values. Adding one more character multiplies difficulty by 16. This exponential growth means:
| Chars | Difficulty (2^(4n)) | Avg Attempts | ~Time @ 500M salts/s |
|---|---|---|---|
| 4 | 2^16 = 65,536 | 65,536 | Instant |
| 6 | 2^24 = 16,777,216 | ~16.8M | ~0.03s |
| 8 | 2^32 = 4,294,967,296 | ~4.3B | ~8.6s |
| 10 | 2^40 ≈ 1.1 × 10^12 | ~1.1 trillion | ~36 min |
| 12 | 2^48 ≈ 2.8 × 10^14 | ~281 trillion | ~6.5 days |
At 12+ characters, mining requires specialized hardware running for days or weeks. This is why truly long vanity patterns are considered rare and valuable as identity markers.
[ 0x05 / GENESIS BENCHMARK ]
PUBLIC PROOF
GENESIS BENCHMARK
Transparent, verifiable proof of the mining process. Every parameter will be published for independent verification.
PENDING PUBLIC BENCHMARK
- Target Pattern
- Pending
- Pattern Type
- Pending
- Pattern Length
- Pending
- Difficulty
- Pending
- Hardware
- Pending
- Miner / Software
- Pending
- Miner Version
- Pending
- Salts / Second
- Pending
- Search Start
- Pending
- Search End
- Pending
- Total Duration
- Pending
- Factory Address
- Pending
- Init-Code Hash
- Pending
- Salt Used
- Pending
- Predicted Address
- Pending
- Deployed Contract
- Pending
- Deployment Tx Hash
- Pending
- Explorer Verification
- Pending
Every benchmark must be reproducible. All parameters will be published for independent verification.
[ 0x06 / MILESTONES ]
PUBLIC MILESTONES
THE PATH FORWARD
Each milestone represents an increasing level of difficulty and a new public benchmark.
LAB I
Planned
9–10 char suffix
Extending the identity suffix beyond 8 characters.
Difficulty: 2^36 — 2^40
~68B — ~1.1T attempts
LAB II
Planned
Dual prefix–suffix feasibility research
Matching both beginning and ending of the address simultaneously.
Difficulty: 2^48+
~281T+ attempts
FRONTIER
Long-term
Faster mining, longer patterns
Pushing the boundary of what's computationally feasible for vanity identity.
Difficulty: 2^56+
Custom hardware acceleration
Every milestone will be benchmarked publicly with full reproducibility.
[ 0x07 / SECURITY NOTES ]
⚠ SECURITY
IMPORTANT
SECURITY NOTES
Salt ≠ Private Key
The salt used in CREATE2 deployment is not a private key. It is a public parameter that determines the contract address. Exposing a salt does not compromise wallet security.
All Three Inputs Matter
CREATE2 address = f(factory, salt, init-code). Changing any of these three inputs produces a completely different address. There is no partial match.
Verify Independently
Never trust a claimed address without verifying it on-chain yourself. Compute the CREATE2 address from the published factory, salt, and init-code hash, then compare with the deployed contract.
Don't Expose Config Early
If you plan to deploy a vanity contract, do not publish a discovered salt or complete executable deployment configuration before deployment unless the factory prevents unauthorized deployment or front-running.
Never Share Private Keys
No legitimate tool, lab, or project will ever ask for your private keys, seed phrases, or wallet recovery information. Never submit these to any interface.
This Lab Doesn't Request Keys
FACE4663 Contract Identity Lab is entirely client-side. All calculator and inspection operations run locally in your browser. No keys are requested and no wallets are connected.
[ 0x08 / CLOSING ]