Dear Polkadot community,
This proposal requests to add dotID as a username authority for the .id suffix on Polkadot People Chain.
dotID is operated by Adam / ECH0.RE, a long-time Polkadot ecosystem contributor, validator operator, and OpenGov-approved People Chain registrar on both Polkadot and Kusama. Referendum #1803 granted ECH0.RE registrar status with 99.99% approval.
Reference: https://polkadot.subsquare.io/referenda/1803
dotID is an identity-focused platform for the Polkadot ecosystem: https://dotid.app
It provides a complete end-to-end flow for People Chain identity without requesting any fee: users can manage their on-chain identity, verify signals such as social accounts and e-mail, complete KYC verification, request Reasonable or KnownGood judgements, and explore identities through a public directory.
To the best of my knowledge, dotID is currently the only automated platform offering all these features free of charge.
Beyond the web application itself, dotID also actively monitors on-chain identities across the ecosystem. This includes identifying outdated, low-quality, suspicious, or potentially malicious identities, and helping keep the identity layer cleaner and more useful for users.
Adding the .id suffix would complete this identity flow with a human-readable username layer. Users, projects, teams, and organizations could receive curated .id usernames directly through dotID.
The .id username request would be integrated directly into the dotID.app workflow, alongside identity management, verification and judgement requests.
The .id suffix is naturally associated with identity and public profiles. It is also aligned with the dotID name, as .id can be read as “dot ID”.
Does this affect .dot usernames?
No. This proposal only concerns authority over usernames using the .id suffix. It does not affect other username suffixes such as .dot.
Is this competing with .dot?
No. There is no intended competition with .dot. The purpose of .id is to provide a dedicated namespace for verified or curated on-chain identities, aligned with dotID’s existing identity and verification workflow.
Does this affect on-chain identities or judgements?
No. This proposal does not modify the identity system, registrar judgements, or existing identities. It only grants dotID authority to issue usernames using the .id suffix.
Will .id usernames be forced on users?
No. Users must request or accept a username. The goal is to integrate .id username requests into the dotID.app workflow.
Why dotID?
dotID is already an OpenGov-approved People Chain registrar and currently provides the only automated end-to-end platform for identity management, verification, Reasonable / KnownGood judgement requests, and identity directory exploration.
dotID wants to be in charge of giving out .id usernames on Polkadot People Chain. It is run by Adam from ECH0.RE, who is a long-time helper and was already approved to manage identities on Polkadot and Kusama. dotID helps users handle their on-chain identity for free, including checking social accounts and email. It also finds bad or old identities to keep things clean. The .id usernames would be a new, human-readable part of this system. This does not change .dot usernames or existing identities. People have to ask for a .id username.
Dear Polkadot community,
This proposal requests to add dotID as a username authority for the .id suffix on Polkadot People Chain.
dotID is operated by Adam / ECH0.RE, a long-time Polkadot ecosystem contributor, validator operator, and OpenGov-approved People Chain registrar on both Polkadot and Kusama. Referendum #1803 granted ECH0.RE registrar status with 99.99% approval.
Reference: https://polkadot.subsquare.io/referenda/1803
dotID is an identity-focused platform for the Polkadot ecosystem: https://dotid.app
It provides a complete end-to-end flow for People Chain identity without requesting any fee: users can manage their on-chain identity, verify signals such as social accounts and e-mail, complete KYC verification, request Reasonable or KnownGood judgements, and explore identities through a public directory.
To the best of my knowledge, dotID is currently the only automated platform offering all these features free of charge.
Beyond the web application itself, dotID also actively monitors on-chain identities across the ecosystem. This includes identifying outdated, low-quality, suspicious, or potentially malicious identities, and helping keep the identity layer cleaner and more useful for users.
Adding the .id suffix would complete this identity flow with a human-readable username layer. Users, projects, teams, and organizations could receive curated .id usernames directly through dotID.
The .id username request would be integrated directly into the dotID.app workflow, alongside identity management, verification and judgement requests.
The .id suffix is naturally associated with identity and public profiles. It is also aligned with the dotID name, as .id can be read as “dot ID”.
Does this affect .dot usernames?
No. This proposal only concerns authority over usernames using the .id suffix. It does not affect other username suffixes such as .dot.
Is this competing with .dot?
No. There is no intended competition with .dot. The purpose of .id is to provide a dedicated namespace for verified or curated on-chain identities, aligned with dotID’s existing identity and verification workflow.
Does this affect on-chain identities or judgements?
No. This proposal does not modify the identity system, registrar judgements, or existing identities. It only grants dotID authority to issue usernames using the .id suffix.
Will .id usernames be forced on users?
No. Users must request or accept a username. The goal is to integrate .id username requests into the dotID.app workflow.
Why dotID?
dotID is already an OpenGov-approved People Chain registrar and currently provides the only automated end-to-end platform for identity management, verification, Reasonable / KnownGood judgement requests, and identity directory exploration.
Threshold
Threshold