BOTLabs Announces web3name at Paris Blockchain Week

BTE BOTLabs Trusted Entity GmbH (BT.E) announced the launch of web3name, an application for creating a personalized name to represent a digital identity, at Paris Blockchain Week, Coin Journal reported in a press release.

This name can be linked to addresses on the KILT network and across the Polkadot ecosystem.

Adding Additional Layers of Verification

Users can also connect SocialKYC credentials—such as Twitter, Twitch, GitHub, email, and other accounts—to their identity, introducing additional verification layers. Creating a web3name for a limited time is free of charge.

A Unique Digital Identity for the Web3 Era

Each identity can have only one web3name, but users may create multiple separate identities, each with its own web3name—for example, a work identity, a collector identity, a gaming identity, and so on.

On KILT, a digital identity is built on a Decentralized Identifier (DID), a unique alphanumeric string tied to the user and any credentials they choose to attach to that identity.

Once a user registers a web3name, it remains theirs. No one else can claim it unless the owner voluntarily relinquishes it back into the web3name pool. There are no additional fees or renewal charges.

Identity Linked to a KILT Address

That identity can be connected to your KILT address and to any or all of your addresses across the Polkadot ecosystem, making it easier for others to reference you. Support will later expand to chains outside the Polkadot ecosystem.

Bridges and Validators

web3name can be easily associated with any number of addresses on any blockchain within the Polkadot ecosystem using the KILT Sporran wallet (or any wallet that supports polkadot.js API extensions), although the system is anchored on the KILT blockchain.

Enhancing, Not Replacing, Addresses

web3name is designed to strengthen identity. It is meant to complement an address, not replace it. While a web3name can link to an address, it is not recommended as a full substitute for an address because:

  • A user may choose to relinquish their web3name, at which point another user with a different address could claim it, and
  • A single name/identifier can be associated with multiple addresses.