The best decentralized identity for your DAO, community, organization, fans.
Sub-accounts have two presentations, They are the same account.
Built for all group
This is our list of classic practical examples for you
Sub-accounts reinforce each member's sense of belonging to the community.
For a well-kept community, giving sub accounts to active members can be an effective way of showing recognition. You can even deny users who do not hold a specific sub-account from joining the conversation via a bot.
Every event you organise, every exchange is worth commemorating, and POAP is born out of this. A .bit sub-account can be issued without a license, and with its useful features, it's a better POAP. who wouldn't want to have a “name.olympic2024.bit” after the Olympics?
The NFT creator can Mint a .bit sub-account for the NFT holder with the same number as the NFT, e.g. Mint "2077.punk.bit" for the holder of Punk #2077. The holder can use 2077.punk.bit or punk#2077.bit as the digital currency receiving address.
PFP+DID allows for a greater variety of personalisation for Web 3.0 users, not to mention the fact that it is a sub-account corresponding to the PFP.
Different voting weights can be assigned depending on the weight of the account.
Want to give a DAO member an identity? Then give him or her a sub-account of the DAO, which will serve as the member's identity and exclusive credentials.
A .bit sub-account with clear DAO branding gives members a stronger sense of identity with the organisation than if they were issued a Token or NFT.
Use your .bit account to issue sub-accounts to your most loyal fans. The previous generation lived in a physical world where they collected signed photos or posters of celebrities; the new generation lives in a digital world where they collect .bit sub-accounts issued by celebrities. Your most loyal fans will use your issued sub-account as a social network nickname to show their affection for you and will also bring you new fans.
The sub-account can be used as an electronic ticket for offline concerts, meet and greets, etc., and is collectible.
Companies can Mint a sub-account for each employee, just like a work email. What's even cooler is that the sub-account is the employee's company identity as well as a cryptocurrency receiving account belonging to the individual employee. Therefore, .bit sub-accounts are perfect for Web 3.0's best teams.
If you are a company or team that uses cryptocurrency to pay employees, Mint .bit sub-accounts for your employees will allow you to pay them in cryptocurrency through a clear .bit sub-account. Instead of that long indecipherable string of addresses. For example: jack.companyname.bit
When Lily owns lily.hermès.bit, it means that Lily is the most privileged guest of hermès. It enhances the brand identity.
The sub-account can be used as an exclusive identity for the customer, and a solid membership system can be established through the sub-account.
Give your most valued customers a .bit sub-account with their name or birthday, which contains both their personalised information and your brand. Is there any other way to strengthen the bond between you and your customers than this?
As the Web3.0 application operations team, we build a bridge between the product and its users by giving them a unique identity for their Mint sub-account.
When you plan to offer users airdrops or certain entitlement rewards, you can obtain a whitelist directly for users who have a sub-account with the organization.
Sub-accounts have totally the same functions as ordinary .bit accounts. Where you can use .bit accounts, you can use .bit sub-accounts.
The cost of minting sub-accounts is almost negligible. The payment is charged only to prevent over-issuing.
Every .bit account can issue their own sub-accounts without permission and number limitation.
Parent-accounts can either choose to issue free sub-accounts through sub-account manage tool provided by .bit, or choose to issue charged sub-accounts through third-party registrars.
A sub-account is a whole new data container that has its own owner/manager. A parent-account can only issue sub-accounts, but it can neither recall them nor conduct data tempering.
If you choose to issue charged sub-accounts, the pricing is totally up to you, and you can get all the profit.
Available in Q2 2022
We call 001.tylor.bit a sub-account of tylor.bit, and tylor.bit a parent account of 001.tylor.bit. Likewise, we call tylor.bit a sub-account of .bit, and .bit a parent account of tylor.bit.
If you own tim.bit, you are recognized as a member of the Web3.0 community; if you own tim.michaeljackson.bit, you are recognized as a huge fan of Micheal Jackson; if you own tim.hermès.bit, you are recognized as an honoured guest of hermès.
Sub-accounts are DID that could build consensus in a specific group and increase their commitment. By issuing sub-accounts to your community/organization/group/fans, you can increase greater group cohesiveness and make them feel belonged.
Want to give identity credentials to DAO members? Issue .bit sub-accounts for them! Sub-accounts of the DAO tells people where they belong more than anything else.
Use your .bit to issue sub-accounts to your fans. They used to collect your signatures and posters. Now they collect sub accounts of your .bit. Big fans of yours would use the sub-accounts as their social media nicknames to show how fond of you they are, which could also bring you new fans.
Imagine if you give your loyal customer a .bit sub-account with his name or birthday in it. It would be the best way of customer bonding that no other method can compete with.
Every activity or AMA you organize is worth memorizing, and that's what POAP was born for. .bit sub-accounts could also do the trick, only in a more convenient way as it could be issued without permission. Who could say no to "name.olympic2024.bit" after they went to watch the game?
If you run a discord or telegram community, you can grant a contributor a .bit sub-account as a way of showing recognition. You can even set up a channel where only the owners of .bit sub-accounts can speak.
Every .bit account can issue their own sub-accounts without permission and number limitation.
Sub-accounts have totally the same functions as ordinary .bit accounts. Where you can use .bit accounts, you can use .bit sub-accounts.
Parent-accounts can either choose to issue free sub-accounts through sub-account manage tool provided by .bit, or choose to issue charged sub-accounts through third-party registrars.
A sub-account is a whole new data container that has its own owner/manager. A parent-account can only issue sub-accounts, but it can neither recall them nor conduct data tempering.
The cost of minting sub-accounts is almost negligible. The payment is charged only to prevent over-issuing.
If you choose to issue charged sub-accounts, the pricing is totally up to you, and you can get all the profit.