BZeUSD Escrow Settlement
<div class="post-category"><span class="cat-badge cat-security">Security</span></div>
<p class="lead"><strong>The BZeUSDEscrow contract at `0x3Cc7...` on Polygon holds funds for multi-step workflows and marketplace bundles. It is the financial safety net that makes cross-node commerce safe for both buyer and seller.</strong></p>
<h2>Overview</h2>
<p>When a caller initiates a bundled purchase or a workflow chain, BZeUSD is transferred into escrow. The DZIT engine then releases funds leg by leg as providers deliver proof-of-service, applying the 70/20/10 split at each release.</p>
<h2>Key components</h2>
<ul><li>Polygon contract `0x3Cc7...`</li><li>Reserve on purchase, release per leg</li><li>Tied to WFID for workflow chains</li><li>Provider releases require proof-of-service</li><li>Automatic refund on timeout</li></ul>
<h2>Related</h2>
<ul><li>[Workflow Chains (WFID & Escrow)](/post.php?slug=workflow-chains)</li><li>[Proof-of-Service Receipts](/post.php?slug=proof-of-service)</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