ENS Diamonds lets a fixed group pool ETH to register one .eth name. Funds stay in an onchain vault during the attempt. If the purchase succeeds, ENS registers the name directly to a Safe controlled by the group.
The protocol never owns the name. It only coordinates funding, registration, and refunds.
Splitting the cost of a name is the easy part. The harder part is agreeing on what happens to the money and the name:
- Who holds the ETH before registration?
- Can a member take their contribution back?
- Who owns the name after purchase?
- What happens when the attempt fails or the price changes?
Using one person's wallet would make that person the custodian. ENS Diamonds moves the rules onchain instead. Contributions are tracked per member, the purchase has a fixed spending cap, and ownership is decided before anyone deposits.
The discover page tracks recently expired names through their 21-day premium period.
Each vault is created for one name and one group. Its owners, Safe threshold, spending cap, registration duration, hidden target, and ENS commitment cannot be changed later.
The creator chooses between 2 and 10 Safe owners, sets the maximum spend, and may make the first deposit. The target label is committed as a salted hash instead of being stored as plain text.
Group members deposit independently. They can add or withdraw ETH while the vault is in
Funding. The creator can also cancel the vault during this stage, which makes every recorded contribution claimable again.When the group is ready, the creator starts acquisition. Funding is locked while the ENS commitment is active. After ENS's minimum commitment age, anyone with the reveal values can execute the purchase.
The contract deploys the predicted Safe and registers the name directly to it. Any unused ETH is split proportionally between contributors. If the attempt expires, each member can claim their full remaining balance.
A vault moves from funding to one acquisition attempt, then settles through purchase or refunds.
The Safe address is known before the purchase. ENS uses that address as the registrant, so the name never passes through ENS Diamonds or another member's wallet.
Safe owners are fixed when the vault is created. The threshold is a strict majority: a two-person group requires both owners, three owners require two, four owners require three, and so on. After registration, the Safe controls records, renewals, transfers, and any later changes to its own configuration.
ENS Diamonds uses pull-based refunds. The contract records what each member can claim, but it does not send ETH to every member inside the purchase transaction.
The claim depends on how the vault ends:
| Result | What each member can claim |
|---|---|
| Acquired | A proportional share of the unused ETH |
| Cancelled | Their full remaining contribution |
| Failed | Their full remaining contribution after expiry |
Each member claims their own balance to a chosen address. One failed transfer cannot block the rest of the group.
The protocol is one immutable contract with no administrator, upgrade path, protocol token, or protocol fee. It can hold escrow, validate the fixed commitment, deploy the Safe, register the name, and account for refunds. It cannot redirect the purchase or move a member's balance at someone's discretion.
The web app handles the product layer around that contract. It lists names in temporary premium, charts the live premium decay, prepares vault configuration, tracks indexed protocol events, and gives each member a clear view of the vault state and their claimable balance.
A completed vault links to the registered name, the shared Safe, and each member's remaining balance.
ENS Diamonds is live on Ethereum mainnet. The web app (opens in a new tab) and contracts (opens in a new tab) are open source, including the architecture, tests, deployment scripts, and audit reports.
The contract charges no protocol fee. A purchase still includes the ENS registration price, any temporary premium, Ethereum gas, and later Safe or renewal costs.
