Monetization

The Blocklet Framework provides a robust, on-chain monetization system. Developers can set prices for their blocklets, define complex revenue-sharing models with contributors, and even create pricing tiers for components used within other blocklets. When a user makes a purchase, they receive an NFT that acts as a verifiable credential of ownership.

Important: Configuration Has Moved While the underlying monetization engine remains the same, the configuration of the payment and nftFactory fields has been moved from the blocklet.yml file to the Blocklet Store's user interface. This change simplifies the publishing workflow and ensures compatibility with the latest on-chain protocols.

The technical details below are provided for developers maintaining legacy blocklets or for those interested in the underlying mechanism.

The payment Object#

The payment object is the core of a blocklet's monetization strategy. It defines the price, how revenue is distributed, and how the blocklet should be priced when used as a component by other blocklets.

payment.price#

This field sets the purchase price of the blocklet. The system currently supports a single token and price per blocklet.

Field	Type	Description
value	number	The cost of the blocklet. Must be greater than 0.
address	string	The DID address of the token used for payment (e.g., the address for ABT).

Example: Setting a Price of 100 Tokens

payment.share#

This array defines how revenue from a sale is distributed among multiple beneficiaries after any component fees have been deducted. It allows for automated, on-chain revenue sharing between developers, contributors, or other stakeholders.

The sum of all value fields in the share array must equal 1, representing 100% of the remaining revenue.

Field	Type	Description
name	string	A descriptive name for the beneficiary.
address	string	The DID address of the beneficiary who will receive the funds.
value	number	The proportion of the revenue to be sent to this beneficiary (e.g., 0.7 for 70%). Maximum of 4 beneficiaries.

Example: 70/30 Revenue Share

payment.componentPrice#

This property is defined within a component blocklet to set its price when it's included in another, parent blocklet. This enables flexible pricing models for reusable components.

Field	Type	Description
parentPriceRange	number[]	An array of two numbers [min, max] defining the parent blocklet's price range for this rule to apply. If omitted, it serves as the default rule.
type	string	The pricing model. Can be 'fixed' for a set amount or 'percentage' for a fraction of the parent's price.
value	number	The fixed amount or percentage value. For 'percentage', 0.1 represents 10%.

Example: Tiered Component Pricing

This component costs a fixed 5 tokens if the parent blocklet costs 50 or less, and 8% of the parent's price if it costs more.

On-Chain Fund Distribution#

When a user purchases a composite blocklet (a blocklet that includes other components), a smart contract on the OCAP Chain executes to distribute the funds automatically and transparently. The process prioritizes component developers, ensuring they are paid first before the remaining funds are distributed to the parent blocklet's beneficiaries.

This entire process is now orchestrated by the Blocklet Store during the purchase flow.

nftFactory Field#

This field holds the DID of the asset factory responsible for minting the purchase NFT. This NFT serves as the user's proof of purchase and ownership.

This value is now always generated and set by the Blocklet Store during the blocklet publish process. Developers should not set this field manually in blocklet.yml.

Understanding monetization is key to distributing your blocklet. To ensure your blocklet's metadata is authentic and tamper-proof, proceed to the Security & Resources section.