BlocpodNFT platform: creator commerce with on-chain provenance and governed paid actions

Bottleneck

Creator commerce on a public ledger has a control problem, not a feature problem. Money, ownership and licences move on every action, and most platforms rely on the operator’s word that fees were split correctly, royalties were paid and a release was safe. Verifying any of that manually means reading transactions by hand.

Blocpod needed a platform where every consequential action is bounded by policy in code, every financial output is separately verifiable, and readiness to release is a generated fact rather than an opinion.

System

The platform covers minting, listings, funding, purchase, transfer, licensing, premium media, paid actions and portable provenance bundles. Wallet keys are encrypted at rest; both stored testnet addresses were re-derived from the current code during verification. A schema migration (version 36) was run against a copy of the production database before any live transaction.

Two live marketplace journeys were executed on a funded testnet from the verified commit. The second one confirmed a distinct 5% platform fee output alongside the exact seller payment and the 3% creator royalty. A fresh deterministic audio inscription verified its origin bytes and HTTP range delivery, and a previously confirmed inscription re-verified a BRC-95 Atomic BEEF receipt.

Control

• Authority policy in code. Which actions an identity may take is enforced by tests named for the boundary they protect: authority-policy, action-lock, paid-actions, access-policy-license.
• Separate money outputs. Platform fee, seller payment and royalty are independent transaction outputs, so anyone can check the split without trusting the operator.
• Release truth, not release notes. release-truth.json records the commit, container digest, schema version, every test command with counts, and the open gates. Status at verification: not-ready.
• Defects published with the evidence. The verification found three defects (a non-repeatable proof script, a missing category validation in the same script, a development environment with no platform fee address) and recorded them next to the passes.

Result

The numbers in the sidebar are from the verification bundle dated 2026-08-14. What matters more than the counts is the shape of the proof: a machine-readable record that says what passed, what did not, and what still blocks release. Two funded-testnet gates remain open (independent provider agreement, and a named BRC-100 wallet acceptance record), and they are listed rather than hidden.

That is the standard Blocpod applies to client systems: evidence that survives the person who produced it.