Bucket Token (BUT): project purpose, mechanism and token context
This profile examines the documented purpose, operating model and token context of Bucket Token. It identifies which points are supported by the reviewed record and which current details still require confirmation. This structure is designed to keep entity-specific evidence, dated limitations and practical verification needs visible rather than hiding them behind generic market language.
Purpose in the reviewed sources
For the project-level scope, the available sources state: Bucket docs describe a decentralized stablecoin protocol on Sui. That evidence helps define Bucket Token, while leaving price, adoption and present operating scale outside the conclusion. The scope is intentionally narrow so that the article does not turn an issuer description into an independent performance claim.
The operating description is more specific on one point: Users deposit collateral to borrow USDB, and BUT is identified as a native protocol token. Its present implementation still needs a current check because technical and product terms are mutable. Readers should compare the described mechanism with the latest official release and the exact deployment they intend to use.
Mechanism described by the project
The sources describe an additional part of the design: Bucket Protocol is a decentralized stablecoin protocol on Sui where users deposit collateral and borrow USDB. The point is informative about mechanism, not a promise of financial outcome or uninterrupted availability. This protects the distinction between how a system is described and what a user can enforce or execute today.
Identity verification matters here because names, tickers, wrapped assets and older deployments may overlap. The record states: Users supply collateral to mint/borrow USDB. BUT is the native protocol token used in the Bucket ecosystem; the protocol docs describe borrowing, collateral and stablecoin mechanisms. Users should confirm the active chain, contract and official interface for Bucket Token. A matching name is not enough when different contracts or representations can trade under similar labels.
Supply and token context
On token role or economic design, the sources report: Documented token utility: Native protocol/ecosystem participation; Governance or incentive functions as documented by Bucket's token system. Any missing supply, allocation, emission, vesting or burn figure remains unresolved rather than being inferred. Supply and allocation statements are treated as dated disclosures rather than permanent properties of the asset.
A related design detail is: Official docs describe the Sui protocol, USDB, collateralized borrowing and BUT/DEBUT token pages. Real-world use can still depend on contract controls, external services, liquidity paths and settlement or withdrawal rules. Technical purpose and operational safety are separate questions, and the available evidence may answer only the first.
Contracts, versions and interfaces
The evidence set contains one additional project-specific point: Bucket Protocol identified; individual founders not confirmed. It is presented as documented context, not as a recommendation or prediction. Project-reported milestones and capabilities remain attributed to the project unless independent evidence confirms them.
Current status depends on what can be confirmed at the time of use. The dossier supports this point: Bucket docs describe a decentralized stablecoin protocol on Sui. If later official records change contracts, terms or deployments, the newer record takes precedence. Historical documentation remains useful context, but it is not automatically evidence of the current operating state.
What the sources do not establish
The evidence establishes the following while leaving other fields open: Users deposit collateral to borrow USDB, and BUT is identified as a native protocol token. Current activity and market conditions should not be inferred from that statement. Explicit gaps tell readers which checks remain necessary and keep the sourced facts distinct from assumptions.
For the last evidence item, the sources state: Bucket Protocol is a decentralized stablecoin protocol on Sui where users deposit collateral and borrow USDB. The practical next step is a current check of chain, contract, official interface and material dependencies. If official sources conflict, the discrepancy should remain visible until a dated authoritative record resolves it.
Key takeaways
- Bucket docs describe a decentralized stablecoin protocol on Sui.
- Users deposit collateral to borrow USDB, and BUT is identified as a native protocol token.
- Bucket Protocol is a decentralized stablecoin protocol on Sui where users deposit collateral and borrow USDB.
- Users supply collateral to mint/borrow USDB. BUT is the native protocol token used in the Bucket ecosystem; the protocol docs describe borrowing, collateral and stablecoin mechanisms.
- Documented token utility: Native protocol/ecosystem participation; Governance or incentive functions as documented by Bucket's token system.
YearBull Rank timeline
YearBull Rank now for bucket-token: #9602.
Rank change (reference points).
Reading rule: lower numbers mean higher placement.
- 7d window (2026-10-21): #5408 → #9602 (down by 4194).
- 30d window (2026-09-28): #5982 → #9602 (down by 3620).
Orderflow context: stable placement often correlates with stable participation. If the curve improves but won’t hold, treat it as flow-driven.
Cycle note: sideways periods still reshuffle relative placement. If 7d and 30d disagree, treat it as a transition window.
Risk framing: minor drift can still matter at scale. If the curve whipsaws, treat the rank as fragile.
Market structure: fragmentation can make rank more reactive. If the line range widens, access or routing may be changing.
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. Smaller numbers mean the coin sits higher in the YearBull list.
