DZIT Token
<div class="post-category"><span class="cat-badge cat-tokens">Tokens</span></div>
<p class="lead"><strong>DZIT is the gas credit token of the 1BZ ecosystem. Every paid interaction between nodes — LLM calls, notarizations, mints, verifications — burns a small amount of DZIT on the caller's behalf.</strong></p>
<h2>Overview</h2>
<p>DZIT is an ERC20 on Polygon deployed at `0x4B37...`. It is purchased with BZeUSD via the DZITSystem contract at `0x1481...`, which routes part of the payment to an escrow and part to operations.</p>
<h2>Key components</h2>
<ul><li>ERC20 on Polygon, 18 decimals</li><li>Purchased in credit tiers from Starter ($10) to Ultra ($10,000 + 50% bonus)</li><li>Burned per API call across the network</li><li>Tracked per DZID identity</li><li>Settled through the 70/20/10 split</li></ul>
<h2>Related</h2>
<ul><li>[BZeUSD Stablecoin](/post.php?slug=bzeusd-token)</li><li>[Commercial Tiers](/post.php?slug=credit-tiers)</li><li>[70/20/10 Revenue Split](/post.php?slug=dzit-revenue-split)</li><li>[DZIT Node](/post.php?slug=dzit-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