Skip to main content

What is a bucket?

Picture a physical bucket you use to carry things around. Digital buckets serve a similar purpose – they're like containers designed to hold your digital items, such as tokens, logs, and API keys. These buckets are your go-to places for keeping these digital belongings organised and easily accessible. It's a bit like having a designated container for each type of digital item you want to store, making it convenient and structured.

Since there are several blockchain networks available, you might need to store different logs and generate tokens on different networks. Each bucket is specifically linked to a single contract type, ensuring that the stored items adhere to the rules and standards of that contract. We have four main types of bucket contracts:

  1. Data Storage (Onchain Logs): This type of bucket is dedicated to storing on-chain logs, providing a reliable and immutable record of actions and events within the blockchain network.

  2. Fungible Tokens (ERC20): Fungible tokens, adhering to the ERC20 standard, can be stored in this bucket type. These tokens are interchangeable and identical in value, making them ideal for various applications like currency or shares.

  3. NFTs (ERC721): Non-fungible tokens (NFTs) are unique digital assets that can represent ownership of items such as digital art, collectibles, or virtual real estate. ERC721-compliant NFTs can be stored in this bucket.

  4. Multi-Standard Tokens (ERC1155): This bucket type supports multi-standard tokens, adhering to the ERC1155 standard. These tokens can represent both fungible and non-fungible assets within a single contract, offering flexibility for diverse digital asset management.

Each bucket serves as a segregated space for its respective contract type, ensuring that items stored within comply with the associated standards and functionalities.

Additionally, you can invite other users to a bucket. This involves assigning different levels of access to these users. When you grant someone member rights, it allows them to view the contents of the bucket. On the other hand, if you provide admin privileges, they gain more control. Admins can create, delete, and edit tokens, logs, and segments within the bucket. Essentially, it's like giving someone permission to either just see what's inside the bucket or to actively manage and modify its contents.