IPVault (NFT Monetization Node)
<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>IPVault turns protected intellectual property into tradable NFTs with built-in resale rights. It is the monetization layer that follows CopyGuard in the 1BZ ecosystem IP pipeline.</strong></p>
<h2>Overview</h2>
<p>Hosted at https://ipvault.1bz.biz, IPVault mints ERC-721 tokens bound to CopyGuard receipts, embeds royalty splits at the contract level, and offers a marketplace where creators can list full rights, limited licenses, or usage slots.</p>
<h2>Key components</h2>
<ul><li>Royalty-bearing NFT contract on Polygon</li><li>Integration with CopyGuard ownership receipts</li><li>Built-in resale marketplace</li><li>DZIT gas for mint and listing, BZeUSD for settlement</li><li>Optional SmartPDF delivery bundle for buyers</li></ul>
<h2>Related</h2>
<ul><li>[CopyGuard Node](/post.php?slug=copyguard-node)</li><li>[SmartPDF Node](/post.php?slug=smartpdf-node)</li><li>[Market Making & Bundling](/post.php?slug=market-making)</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