<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>DX is the Dzit Exchange, a discounted crypto trading venue within the 1BZ ecosystem. It offers voucher-based discounts on stablecoin conversions and on DZIT credit top-ups.</strong></p>
<h2>Overview</h2>
<p>Hosted at https://dx.1bz.biz, DX lets Pro and higher tiers convert BZeUSD, USDT, and DZIT at reduced spreads. Vouchers issued through BizNode campaigns and the affiliate program redeem here.</p>
<h2>Key components</h2>
<ul><li>BZeUSD / USDT / DZIT pairs</li><li>Voucher redemption engine</li><li>Polygon-native settlement</li><li>Consumes small DZIT gas per trade</li><li>Tier-gated discount schedule</li></ul>
<h2>Related</h2>
<ul><li>[DZIT Node](/post.php?slug=dzit-node)</li><li>[BZeUSD Stablecoin](/post.php?slug=bzeusd-token)</li><li>[Affiliate Incentives](/post.php?slug=affiliate-incentives)</li></ul>
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
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 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