User Manual

⚓Onboarding:

Objective:

Make a PIL and standardize the licensing process across all IP assets listed

Steps:

Standard Registration via Story Protocol:

  • Genesis Creators to register the initial IP Asset using Story Protocol’s SDK with an ideally a project reference link (e.g. from Kickstart).

  • Creators are encouraged to proceed asset registration here. Creators are also required to attach a License of selection. License is also required prior to remixing.

  • User Action: The Lister attaches the appropriate license to their IP asset by selecting predefined license terms or entering custom terms.

  • Platform Response: The platform interacts with the [Licensing Module] to attach the selected license terms to the IP asset.

  • Upon completion, users can view ERC-721 IP Asset details using the official explorer by inputting the ID. This function is not provided separately.

🌱Standard Listing:

Objective:

Any IP assets are required to be listed in order to access the infrastructure provided for token exchanges.

Steps:

  1. Verification of License Appropriateness

    • Platform Response: The platform performs a verification check to ensure the license terms comply with platform standards, and return with feedbacks

  2. Dispute Status Check

    • Platform Response: The platform queries the [Licensing Module] and the [Dispute Module] to check if the IP asset is involved in any disputes.

    • UI Feedback: If the asset is under dispute, the Lister is notified, and the asset cannot be listed until the dispute is resolved.

  3. Finalizing the Listing

    • User Action: The Lister confirms the listing details and selects the appropriate IP asset for listing.

    • Platform Response: The platform finalizes the listing process, ensuring all checks are passed.

    • Explorer View: Upon successful listing, the user can view the details of the NFT using the search box provided by inputting the IP ID.

💰Token Exchange:

Objective:

To support any IP assets generated by registered with Story to be traded

Steps:

  1. Navigating to the Token Exchange

    • User Action: Log into the DelphinFi Platform and view the IP Asset listings

    • Platform Response: The platform will display the trade view and an asset detail page with Buy & Sell functions.

  2. Initiating Buy & Sell Action

    • User Action: The user clicks on the “Buy” or “Sell” button from the trade viewer or asset detail page.

    • Platform Response: The platform initiates the process to fetch the price feeder for the transaction.

  3. Fetching IP Asset Pricing Details

  • Front End Action:

    • The front end feeds the IP ID into the system.

    • It reads from the price feeders using the _Curve() function, which calls getPrice() to obtain the current price.

    • Configuration: The input array stores key parameters for _Curve() configuration.

  • Platform Response: The platform retrieves the current price of the IP asset using the price feeders and displays it to the user.

  1. Checking User Balance

  • User Action: The user confirms their intention to proceed with the transaction.

  • Platform Response: If the user has sufficient funds or assets, the transaction proceeds. If not, an error message is displayed indicating insufficient balance.

  1. Viewing Transaction in User Profile

  • User Action: The user navigates to their profile to view their transaction history and current holdings.

  • Platform Response: The platform updates the user’s profile to reflect the completed transaction, showing the new balance and asset ownership status.

🧬1:1 Remix:

Objective:

Create and mint new derivative IP-Asset from initial IP-Asset.

Steps:

  1. Initiating the Remix Process

    • User Action: The user clicks on the “Remix” button to start the remix process.

    • Platform Response: The platform begins the verification checks for the selected IP asset.

  2. Verification Checks

  • Check Appropriate License:

    • License: Commercial

    • License: Commercial Remix

    • Platform Action: The platform checks if the selected IP asset has the necessary commercial and commercial remix licenses attached.

  • Check Dispute Status:

    • No Dispute

    • No Judged Unfavorable Dispute

    • Platform Action: The platform verifies that the IP asset is not involved in any disputes and has no unfavorable judgments.

  • Check User FIN:

    • Platform Action: The platform checks if the user has at least 1 FIN (a unique identifier or token required for the remix process).

    • UI Feedback: The user is notified if any of these checks fail, and the remix process cannot proceed until all conditions are met.

  1. Minting the Remix IP Asset (IPA)

  • User Action: Upon successful verification, the user confirms their intention to proceed with minting the new IP asset.

  • Platform Response:

    • The platform mints the new IPA on behalf of the user.

    • License Inheritance or Customization:

      • The new IPA either inherits the parent IPA’s license or has a customized license attached as specified by the user.

    • The platform transfers the newly minted IPA to the user’s address in exchange for ETH.

      • Burning Parent FIN:

        • The FIN from the parent IPA is burned to ensure uniqueness and prevent duplication.

      • Minting Child FIN:

        • A new FIN is minted for the child IPA, free of charge, with a new price curve.

PreviousModular InteractionNextContract Functions

Last updated