1BZ Ecosystem Overview
<div class="post-category"><span class="cat-badge cat-ecosystem">Ecosystem</span></div>
<p class="lead"><strong>The 1BZ Ecosystem is a decentralized network of twelve interoperable nodes that together deliver AI business automation, blockchain identity, IP protection, document workflows, and marketplace services. Each node is a standalone service that speaks to the others via DZIT credits and standardized handles.</strong></p>
<h2>Overview</h2>
<p>The ecosystem is anchored by the main hub at https://1bz.biz and orchestrated by BizNode at https://biznode.1bz.biz. Services settle on Polygon using the BZeUSD stablecoin, meter usage in DZIT gas credits, and reward participation with 1BZ governance tokens.</p>
<h2>Key components</h2>
<ul><li>BizNode — AI business operator that automates sales, support, and content</li><li>DZIT — identity (DZID) and credit issuance on Polygon</li><li>CopyGuard, IPVault, SmartPDF — IP protection, monetization, delivery pipeline</li><li>Fax, BizChannel, UBC — communications, ad marketplace, publishing</li><li>DX and FV — discounted crypto trading and identity verification</li><li>NodeMonitor — the shared LLM gateway, Qdrant KB, and API router</li></ul>
<h2>Flow</h2>
<p>CopyGuard (protect) -> IPVault (monetize) -> SmartPDF (deliver) -> DZIT (settle) -> BizNode (automate). Fax uses CopyGuard for ownership proof. All services burn DZIT gas.</p>
<h2>Related</h2>
<ul><li>[BizNode Node](/post.php?slug=biznode-node)</li><li>[DZIT Token](/post.php?slug=dzit-token)</li><li>[NodeMonitor Gateway](/post.php?slug=nodemonitor-gateway)</li><li>[70/20/10 Revenue Split](/post.php?slug=dzit-revenue-split)</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