Summary
Following the discussion in the 2 December 2025 Town Hall, one major community concern was preventing a single user from scooping desirable names in FCFS model. Several ideas were presented, such as linking name ownership to existing Web2 identities (X, Telegram, Discord). While helpful, these approaches only partially solve the problem and introduce concerns around privacy, centralization, and onboarding friction.
This issue proposes an alternative design that remains fully on-chain, human-oriented, anti-squatting, privacy-preserving, and avoids reliance on external Web2 systems.
Problem
-
FCFS allows early users or bots to grab large swaths of high-value names.
-
Web2-identity-linked verification introduces centralization risks, privacy concerns, and onboarding friction.
-
A sustainable name service should:
- resist name squatting,
- stay accessible to real users,
- avoid Web2 dependencies,
- remain decentralized and user-friendly.
Proposed Solution
A combined approach of on-chain mechanisms that discourage abuse while keeping the system simple and decentralized.
1. Use Human Passport Score for Eligibility
- Integrate "Human Passport" scoring to ensure an address represents a real human.
- No need for direct Web2 social accounts or personal data.
- Aligns with AtomOne’s vision of human-first, decentralized identity.
- Prevents bots and mass-registration attempts.
2. Progressive Cooldown System
Most users realistically need only 1–2 names (wallet identity + pseudonym).
To discourage squatting:
- After purchasing 1 name → impose a 30-day cooldown.
- After purchasing 2 names → increase cooldown to 3–6 months.
- Cooldown escalates progressively with each name per address.
This makes squatting expensive and slow, while keeping normal usage frictionless.
3. Make Names Non-Transferable (Soulbound-Like)
- Names cannot be transferred or sold.
- Removes the financial incentive for name hoarding.
- Prevents black-market resale of desirable names.
- Genuine users who want a name for actual usage are unaffected.
4. Add Voluntary Name Forfeit / Release
- Users should be able to release a name before expiration.
- Helps recycle unused names back into the pool.
- Reduces long-term accumulation by inactive or abandoned addresses.
5. DAO Governance for Impersonation or Abuse Cases
-
Introduce governance controls for exceptional cases:
- impersonation of real people or brands,
- malicious or harmful use.
-
Requires a strong quorum / high voting threshold.
-
Adds a necessary safety valve without making the system centralized.
Why This Approach Works
- Decentralized: Avoids Web2 identity reliance.
- Human-first: Uses Human Passport to prioritize real users.
- Anti-abuse: Progressive cooldown + non-transferability discourages registration farming.
- Low-friction: No uploads, no linking, no off-chain social verification.
- Governable: DAO provides controlled, transparent resolution for edge cases.
This is what can solve not only the problem but also easier to implement as well.
Summary
Following the discussion in the 2 December 2025 Town Hall, one major community concern was preventing a single user from scooping desirable names in FCFS model. Several ideas were presented, such as linking name ownership to existing Web2 identities (X, Telegram, Discord). While helpful, these approaches only partially solve the problem and introduce concerns around privacy, centralization, and onboarding friction.
This issue proposes an alternative design that remains fully on-chain, human-oriented, anti-squatting, privacy-preserving, and avoids reliance on external Web2 systems.
Problem
FCFS allows early users or bots to grab large swaths of high-value names.
Web2-identity-linked verification introduces centralization risks, privacy concerns, and onboarding friction.
A sustainable name service should:
Proposed Solution
A combined approach of on-chain mechanisms that discourage abuse while keeping the system simple and decentralized.
1. Use Human Passport Score for Eligibility
2. Progressive Cooldown System
Most users realistically need only 1–2 names (wallet identity + pseudonym).
To discourage squatting:
This makes squatting expensive and slow, while keeping normal usage frictionless.
3. Make Names Non-Transferable (Soulbound-Like)
4. Add Voluntary Name Forfeit / Release
5. DAO Governance for Impersonation or Abuse Cases
Introduce governance controls for exceptional cases:
Requires a strong quorum / high voting threshold.
Adds a necessary safety valve without making the system centralized.
Why This Approach Works
This is what can solve not only the problem but also easier to implement as well.