1BZ Governance Token
<div class="post-category"><span class="cat-badge cat-tokens">Tokens</span></div>
<p class="lead"><strong>1BZ is the governance token of the ecosystem. Holders vote on protocol parameters, tier pricing changes, and treasury allocations.</strong></p>
<h2>Overview</h2>
<p>1BZ is distinct from DZIT (gas) and BZeUSD (settlement). It is distributed to long-term participants — node operators, premium subscribers, and major affiliates — rather than sold outright.</p>
<h2>Key components</h2>
<ul><li>ERC20 on Polygon with voting extension</li><li>Distributed via participation rewards, not public sale</li><li>Governs tier pricing, split ratios, and listing policies</li><li>Quarterly on-chain proposals</li><li>Held alongside DZIT and BZeUSD by active operators</li></ul>
<h2>Related</h2>
<ul><li>[DZIT Token](/post.php?slug=dzit-token)</li><li>[BZeUSD Stablecoin](/post.php?slug=bzeusd-token)</li><li>[E2P Engagement Token](/post.php?slug=e2p-token)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u