I went back through
$BUCKET today, and one thing I missed the first time is probably one of the most important:
🔒 970M of the 1B supply was seeded into locked liquidity at genesis.
There is no withdrawal path for the LP principal.
That alone changes the risk profile quite a bit.
What also stood out to me:
🧩 The token contract itself is very simple
• 1B fixed supply
• no owner
• no mint
• no pause
• no blacklist
• no tax switch
• no proxy/upgrades
So the bigger risks are in the surrounding protocol and operator, not the token contract itself.
💸 There is an actual working product behind it
BUCKET trading fees are used to buy tokenized stocks/crypto that get distributed to holders.
How it works:
• minimum eligibility: 65,000
$BUCKET
• your share accumulates
• once it reaches $2, it gets delivered automatically
• no staking
• no claim button
📊 The numbers are what really caught my attention
DeFiLlama currently shows roughly:
• $130K cumulative protocol fees
• $98K in holder revenue
That’s not projected APY or theoretical yield.
That’s actual fee activity.
🛠️ A lot has been built since I first looked
• v2 payout engine
• Stockback
• live launchpad
• XCORP
• buyback/burn system
• whitepaper + transparency pages
And Bucket Labs LLC is now registered in North Carolina.
🌐 The bigger thesis is interesting
The goal is not just earning from
$BUCKET volume.
The ecosystem is trying to create other rails that can feed value back in:
• Stockback
• the launchpad
• XCORP
XCORP already routes part of its pool fee toward
$BUCKET holders.
That part is still early, but it’s a lot more interesting than a token that only depends on its own chart.
⚙️ There is also an important control surface
The payout keeper runs off-chain about every 5 minutes and signs with the protocol owner key.
That same key controls:
• Treasury buys/withdrawals
• FeeVault sweeps
• keeper operations
If the keeper stops, fees can still accumulate — but Drops pause.
⚠️ And the LLC does not magically decentralize that
There is still:
• one owner key
• no multisig
• no timelock
Their own docs say moving the key behind a multisig is a next step.
That’s one of the biggest improvements I’d still like to see.
🧪 There is history worth knowing too
• a lending-vault experiment lost 0.3565 WETH on Aug. 27
• it remains halted while the root cause is investigated
• SB Security is auditing the launchpad
• SB Security is not auditing the entire Bucket stack
Those are important distinctions.
📌 So no, this is not an “everything is perfect” post.
What caught my attention is the combination of:
• simple fixed-supply token
• heavily locked liquidity
• functioning product
• measurable fees
• actual holder distributions
• continued development
• outside security review underway
And importantly, the risks are actually documented.
That’s why I went back down the
$BUCKET rabbit hole.
Worth digging into yourself.
robinhood:0xbc9e7b1c5c0081f4ae85e71ec95703d3dec9ffad
0xbc9E7b1c5C0081f4aE85e71eC95703d3dEC9ffaD