BZeUSD Stablecoin
<div class="post-category"><span class="cat-badge cat-tokens">Tokens</span></div>
<p class="lead"><strong>BZeUSD is the settlement stablecoin of the 1BZ ecosystem. It is the unit of account for subscriptions, escrow, and marketplace settlement, and it is exchangeable one-for-one against USDT on Polygon through Uniswap.</strong></p>
<h2>Overview</h2>
<p>BZeUSD wraps USDT with a thin settlement layer that lets the DZIT system issue credits, hold escrow, and execute the 70/20/10 revenue split without repeated bridge fees. Users buy BZeUSD once and reuse it across every node.</p>
<h2>Key components</h2>
<ul><li>Polygon ERC20 pegged to USDT</li><li>Escrow contract `0x3Cc7...` for workflow settlement</li><li>Primary buy path: Uniswap BZeUSD/USDT pair</li><li>Used for DZIT top-ups, tier purchases, and marketplace checkouts</li><li>No mirrored off-chain balance — the chain is truth</li></ul>
<h2>Related</h2>
<ul><li>[DZIT Token](/post.php?slug=dzit-token)</li><li>[BZeUSD Escrow Settlement](/post.php?slug=escrow-settlement)</li><li>[DX Node](/post.php?slug=dx-node)</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