Story Protocol Explained: IP Registration, Licenses and Royalty Limits

Reviewed and updated: October 19, 2026.

Story connects intellectual-property records, licensing terms and payments to a blockchain. Its useful contribution is a programmable workflow for participating creators and licensees. Registering a work does not, by itself, settle who created it, establish every right needed to license it or detect every use of it on the internet.

What the protocol actually records

The IP Asset Registry identifies an asset through a chain ID, NFT contract and token ID, and associates it with an IP account. That gives applications an addressable record for permissions and relationships. A registry entry is evidence of a protocol action. Treating it as conclusive evidence of copyright ownership would require a separate, unsupported leap.

Story's licensing module attaches terms, mints license tokens and registers derivative relationships. Its Programmable IP License supplies an off-chain legal framework. Read the actual license version and applicable terms: a label such as commercial use is not a complete description of permitted uses, attribution duties, restrictions or remedies.

A creator's preparation worksheet

Question	Evidence to assemble	Why it matters
What is being licensed?	A specific work, version, description and reproducible file reference	A collection name alone can leave the licensed material ambiguous
Who controls the rights?	Creation records, assignments and third-party permissions	Control of an NFT does not establish rights in every included element
Which uses are permitted?	Commercial, derivative, attribution and revenue provisions	Permission to display an image may differ from permission to modify it
Where does money enter?	Payment token, payer, reporting duties and collection process	A routing contract cannot collect revenue it never receives
Who can change the record?	Owner, operator permissions and metadata settings	A mistaken permission can affect later actions

This worksheet is an editorial way to assess a proposed workflow, not a determination of anyone's legal rights. Preserve the underlying documents as well as transaction receipts. Story's metadata module supports URI and hash fields; a matching hash helps check a file's bytes, but does not establish the truth of statements inside the file.

Worked example: one character, two businesses

Imagine an illustrator licensing an original character to a game studio. The drawing includes a purchased font and a photograph supplied by a collaborator. Before registration, the illustrator needs to establish whether those elements can be included in the proposed commercial license. Uploading the composite image does not expand the font license or transfer the collaborator's rights.

Suppose the agreed terms require 10% of a defined revenue base. If that base is $2,000, the contractual calculation is $200. If only $150 reaches the relevant payment workflow, an on-chain receipt for $150 does not prove the entire obligation was paid. The missing $50 is a reporting or collection question. These invented amounts illustrate reconciliation, not Story's fees or a universal royalty formula.

For a derivative chain, examine the selected royalty policy rather than repeatedly applying one assumed rule. Story's Liquid Relative Percentage policy describes percentages that compound through relationships. Other policies can allocate revenue differently. A displayed percentage is incomplete without its policy, revenue base and place in the derivative graph.

AI-assisted work needs its own rights analysis

The U.S. Copyright Office's January 2025 report distinguishes protectable human expression from material generated by AI alone. It discusses human selection, arrangement and modification, and says prompts alone are insufficient under its analysis. This is a U.S. copyright source, not a universal rule for every country or a verdict on a particular image.

Keep a record of human contributions and the tool's usage terms when relevant. Neither successful minting nor an automated license screen resolves all authorship questions. A protocol dispute mechanism and a court proceeding also have different scopes and consequences.

What to verify before signing

Match the network, asset identifier, license terms, fee token and recipient to the intended transaction. Save the terms you relied on and confirm the resulting record after execution. The practical test is whether the system makes permissions and payments easier to inspect—not whether it promises to eliminate infringement or guarantee income.

Sources and scope

Continue reading: Tokenized claims and rights · NFT data and ownership

Editorial update: Added a creator rights-and-payment worksheet; separated registration from proof of ownership and revenue collection; clarified AI copyright scope and royalty-policy differences.