E2P Engagement Token
<div class="post-category"><span class="cat-badge cat-tokens">Tokens</span></div>
<p class="lead"><strong>E2P is the engagement-to-participation token of the 1BZ ecosystem. It rewards users who contribute content, answer support questions, verify other operators, and refer new customers.</strong></p>
<h2>Overview</h2>
<p>E2P is emitted by participation events rather than purchased. It can be converted to DZIT credits or staked toward 1BZ governance weight, giving active community members both utility and voice.</p>
<h2>Key components</h2>
<ul><li>Participation emission — posts, reviews, verifications</li><li>Convertible to DZIT at a floating rate</li><li>Stake-able toward 1BZ governance weight</li><li>Tracked per DZID</li><li>Subject to anti-sybil checks via FV verifications</li></ul>
<h2>Related</h2>
<ul><li>[1BZ Governance Token](/post.php?slug=1bz-governance-token)</li><li>[DZIT Token](/post.php?slug=dzit-token)</li><li>[Affiliate Incentives](/post.php?slug=affiliate-incentives)</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