Your new TLD, set up with your team.
Holding an onchain TLD is where the work starts. Our TLD setup service takes a new holder from transfer to the first live names: policy, wallets, payments, a website and agent identities, built alongside your people. You keep every key.
What you have at day ninety
Each deliverable rests on a capability that works today. The linked pages explain each one with its public sources.
A signed issuance policy
Who may request a name, who approves it, what it may point to, and which names stay reserved.
Verified treasury names
Addresses your counterparties check by name in compatible wallets.
Wallet names PaymentsLive payment names
Invoices and payouts that settle to a name under your TLD.
Payments at a name WebsiteA site on the TLD
An official page published to IPFS, opening on your own name.
Websites on onchain TLDs AgentsAgent identities
Names for the AI agents you run, connectable to ERC-8004.
AI agent identity OperationsAn assistant workflow
Routine record changes handled from an AI assistant, inside your policy.
Names from AI assistantsLaunch an onchain TLD in three phases
The plan is drafted with your team in week one and adjusted as you go.
Foundations
- Custody review of the holding wallet
- Issuance policy drafted and signed
- Reserved names locked
First names live
- Treasury and payment names published
- Site on the TLD
- Test transfers with a small amount
Extend and hand over
- Agent identities and subsidiary names
- Runbook for your team
- Review of what to open next
Who may issue names
Only the wallet holding the TLD can create names under it. That makes it the most sensitive key your organization owns.
The issuance register turns that power into a process. Every name has a purpose, a requester, an approver and a destination, and the reserved list protects the names a bad actor would want most.
What do you need from our team?
An owner on the business side, someone from legal or compliance, and whoever controls the holding wallet. A few hours a week each during the first phase.
Can the acquisition be announced?
When you decide, and only then. Some holders launch quietly and let the names speak first.
pay.yourbrandCustomer paymentsRequested by Finance, approved by CFO and legaltreasury.yourbrandTreasury verificationRequested by Treasury, approved by CFOagents.yourbrandAI agent identitiesRequested by Engineering, approved by CTO and legallabs.yourbrandSubsidiaryRequested by subsidiary lead, approved by group legalsupport.yourbrandReservedNot issued without board sign-offsecurity.yourbrandReservedNot issued without board sign-off
Lines we hold when we set up a web3 TLD for a company
Activation is optional and scoped apart from the transaction. Some lines it never crosses.
- We never hold keys or admin rights over your TLD
- We never issue a name under it in our own name
- Nothing goes public without your written approval
- No promise of reach in wallets or browsers beyond what each integration supports
Activation questions
Do we need activation to own the TLD?
No. The TLD is yours from the moment transfer is confirmed onchain. Activation is a separate engagement you can start at any time.
How is this different from the Launch Roadmap?
The Launch Roadmap is a free planning tool you run alone. Activation is the same plan carried out with a partner next to your team.
Can you activate a TLD we bought elsewhere?
Yes. Ownership is checked on the registry first, then the work starts the same way.
How is the TLD setup service priced?
Quoted privately once the scope is clear, usually after a first working session.