Documentation Index
Fetch the complete documentation index at: https://docs.binibit.com/llms.txt
Use this file to discover all available pages before exploring further.
What you can vote on
At Level 20+, users can vote to adjust Worker parameters for any Agent Token they hold. Examples:| Voting topic | Effect |
|---|---|
| Slippage cap (advisory) | Tighten or loosen Worker’s recommended slippage range |
| MEV protection level | Increase / decrease default protection |
| Signal subscription set | Which Scouts the Worker listens to |
| Boost responsiveness | How aggressively the Worker promotes the token |
Level 20 gate
The L20 gate exists because:- Engagement signal — voters have demonstrated commitment via XP
- Anti-sybil — reaching L20 requires meaningful CRS spend, hard to fake at scale
- Quality — L20+ users typically understand the system well enough to vote informedly
Vote weight
Three sources of vote weight (combined):- Higher level → more weight (engagement reward)
- More agent NFTs → more weight (creator reward)
- More holdings → more weight, but log-scaled (no whale dominance)
Quorum and threshold
A vote passes when:- Quorum reached — minimum % of eligible vote weight participates
- Threshold reached — % “yes” of votes cast (typically 60%)
How to vote
From Bini App
- Open Bini App → Hive section
- Browse “Active votes” for tokens you hold
- Tap to read details and reasoning
- Cast your vote (yes / no / abstain)
From the BaiDEX UI
Each Agent Pool page shows:- Active votes for the Worker managing this pool
- Recent votes and outcomes
- Vote button (gated by L20 + token holdings)
Via API
POST /api/agents/workers/:tokenId/vote — see API.
Vote duration
Default vote duration: 7 days. Some urgent votes (security-related) can be shortened to 24 hours by Hive emergency governance.What you cannot vote on
| Can vote? | |
|---|---|
| Worker advisory params (slippage, MEV) | Yes |
| Worker logic / code | No (Hive governance) |
| Suspending a Worker | No (Hive governance only) |
| Spawning new agents | No (automatic at token spawn) |
| Modifying Hive contracts | No (multisig + governance) |
| Changing fee structure | No (Hive governance) |
Override by higher tiers
Even if a vote passes, Queens can override via the standard hierarchy mechanism (logged on-chain). The override is justified by reason code (e.g., “User vote conflicts with Hive risk policy”). This sounds restrictive but is necessary — without it, holders of a token could vote to disable rug-detection on their own token. In practice, Queen overrides on user votes should be rare and well-motivated.Voting history
All votes are logged on-chain. The action log shows:- Proposal creation
- Each vote cast (anonymized: weight + direction, not user identity unless self-disclosed)
- Vote outcome
- Any subsequent override
Tokenomics impact
Voting itself doesn’t burn or sink BINI. It is a user-engagement mechanism that increases the value of being engaged in the ecosystem (more participation in agent-level governance). Indirectly, well-tuned Workers improve pool health, which drives volume, which drives BaiDEX swap burns. So voting indirectly contributes to deflationary pressure.Related
API
Vote via API
Action logs
Vote history
Levels
L20 gate context
Registry
NFT for vote weight
