Put multiple data together and use .bit to index them. One piece of data can be stored in more than one .bit.
Assign a .bit for a piece of data as its alias. One piece of data can only have one alias.
When you transfer assets to an address in wallets/exchanges that have integrated .bit alias, you can see the .bit alias of that address, and verify if the address is the correct one.
When you make a large-amount transfer, wallets/exchanges only display part of the .bit alias of the address. You need to complete the .bit alias to continue with the transfer.
When you send a transaction to a smart contract with wallets that have integrated .bit alias, you can easily verify if the .bit alias shown in the wallet matches the one published in the project's official website.
In Q2 2022, you can set a .bit alias for smart contracts addresses on the following public chains: Ethereum, Binance Smart Chain, Polygon.
When you use DApps that have integrated with .bit alias, your .bit account is displayed wherever your DApps currently display addresses.
The leading architecture of .bit makes it possible for you to set .bit alias for the following data:
1. Normal addresses of any public chain;
2. Contract addresses of EVM compatible chain;
3. Public keys of any asymmetric cryptography system.
When you set a .bit alias for normal addresses/public keys/contract addresses, you have to provide the corresponding private key. This means the only person who can set a .bit alias for the data is the person who owns the data.