Affiliate Incentives
<div class="post-category"><span class="cat-badge cat-marketplace">Marketplace</span></div>
<p class="lead"><strong>Affiliates earn the 20% referral leg of every transaction they source into the 1BZ ecosystem. Incentives are automatic, on-chain, and persistent — once a referral is recorded, every future call by that customer routes 20% to the referrer.</strong></p>
<h2>Overview</h2>
<p>Affiliate tracking is a Pro-tier feature. It is exposed through the bot's affiliate commands and the dashboard's affiliate page. Referrals bind to DZIDs, so a customer who switches devices still carries their referrer.</p>
<h2>Key components</h2>
<ul><li>Referral binding by DZID (not cookie)</li><li>20% of every call, every tier, forever</li><li>Paid in BZeUSD on settlement</li><li>E2P participation bonuses for top affiliates</li><li>Tier-gated — Pro and above</li></ul>
<h2>Related</h2>
<ul><li>[70/20/10 Revenue Split](/post.php?slug=dzit-revenue-split)</li><li>[E2P Engagement Token](/post.php?slug=e2p-token)</li><li>[Pro Tier ($100)](/post.php?slug=tier-pro)</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