Generally refers to the entire .bit open-source project.
Refers to each individual account, such as alice.bit, bob.bit.
Another name for a .bit account.
Each blockchain address can be uniquely mapped to a .bit account for easy identification of the address's ownership and to optimize user experience. This feature is called .bit Alias.
See .bit Alias for more details.
Each main account can distribute its own SubDID, similar in form to child.parent.bit. SubDID can be used in any community to enhance community cohesion.
See .bit SubDID for more details.
The process of obtaining a .bit account by paying a fee to the .bit contract.
Holding a .bit account requires paying a certain fee annually, and the fees vary depending on the length of the account name.
The resolution records of each account are stored on the blockchain and require a fixed storage space, so a certain storage fee must be paid. The storage fee will be refunded after the account expires and is reclaimed.
Any .bit account can act as an inviter. When you register an account, you fill in a .bit account as the inviter, and you can get certain discounts; when someone else registers an account and fills in your .bit account as the inviter, you can also get certain rewards.
Any product (such as a wallet) that integrates .bit registration services can be called a channel. If a user completes the registration through the channel, the channel can get a certain proportion of the registration fee.
An organization or individual that provides users with a registration interface and payment method.
Refers to the time on the blockchain, which is usually slightly behind the real-world time and does not pass uniformly like real-world time.
Each account has an owner who owns the ownership of the .bit account and can modify the owner and administrator.
Each account has an administrator who has the management rights of the .bit account and can modify the resolution records of the account.
Each piece of data associated with a .bit account, such as a BTC address or a Twitter account, is called a resolution record.
The .bit contract is deployed on Nervos, a public chain with smart contracts based on the Cell (UTXO) model.
Cell is the most basic unit of Nervos. Cell is a concept abstracted from the UTXO model of Bitcoin and can carry many different types of data: tokens, code, JSON, etc.
According to different uses, the Cells used by .bit have different names:
- AccountCell: the basic unit carrying the .bit account, and a primary account has an AccountCell.
- IncomeCell: the Cell that carries the CKB balance within the .bit ecosystem, which is often used in commission rebates, reward scenarios, etc.
- BalanceCell: the Cell that carries the .bit account balance.
View all Cell types: Cell Protocol v1
A digital string that meets the SLIP-0044 specification, used to represent a token or public chain.
In .bit, the coin_type is mainly used in the resolution records of the data container to distinguish between different public chain addresses.
View the complete SLIP-0044
An Ethereum network identifier that complies with the EIP-155 specification. Used to distinguish between different EVM-compatible chains/networks.
View the full list of
chain_idnetworks: ChainList