# X-Talk NFT Liquidity Provision

&#x20;The ability to mint and own an NFT on Chain A and selling the NFT on OpenSea and/or Chain B and/or Ethereum Marketplace (More Marketplaces to be added). The NFT will automatically be burned / custom actioned when the NFT changes ownership on the chain(s) or marketplace(s). This allows the similar NFT to be used on various platforms while preserving the utility and permissions.&#x20;

## **Example:**&#x20;

The ability to mint an NFT on Binance Smart Chain, list it on OpenSea Ethereum Marketplace with a Smart Contract on L1X. The NFT will be automatically burned when it changes ownership on the Binance Smart Chain or Ethereum OpenSea Marketplace. The NFT will be usable on the Game on the Binance Smart Chain while this is listed on OpenSea Ethereum Marketplace.&#x20;



### Technical Workflow

<figure><img src="https://2881198403-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4R4yL4HyysdEvMsBOUt3%2Fuploads%2FpKFCxIfmQye2b8B7eK6z%2Fimage.png?alt=media&#x26;token=0250ccc9-01e2-450f-8cdd-d457f35a873c" alt=""><figcaption><p>Figure 19 X-Talk NFT Liquidity Provision Workflow</p></figcaption></figure>



###  Workflow explained

1. User assigns NFT rights to the L1X MultiSig smart contract on the Binance Smart Chain.&#x20;
2. User initiates the Smart Contract on the L1X Chain that makes the Execution Manager ready in terms of listening to the MultiSig contract initiation events.&#x20;
3. Execution Manager informs the Rule Engine about Transaction Type. In this use case, it’s ‘L1X\_Advertisement’.&#x20;
4. Rule Engine verifies the event and forwards it to the Rule Processor.&#x20;
5. Rule Processor filters and sends relevant information to the Rule Database.&#x20;
6. Rule Database gives the response for the associated function call.&#x20;
7. Rule Engine sends an event for an empty struct to the Execution Manager with function/rules such as Mint, Transfer, Collect Fees, and its relevant variable/function parameter details.&#x20;
8. Execution Manager requests Execution Register to store the information about NFT transfer to the MultiSig.&#x20;
9. Execution Register stores the event information and informs Execution Manager.&#x20;
10. Execution Manager invokes the user and L1X to sign the MultiSig on the Ethereum blockchain network.&#x20;
11. L1X MultiSig Smart Contract triggers an event once the MultiSig is signed by the user and L1X.&#x20;
12. Rule Engine sends the corresponding event for the transaction struct to the Execution Manager.&#x20;
13. Execution Manager updates the Execution Register to store information that L1X MultiSig on Ethereum blockchain network is signed by the user and L1X.&#x20;
14. Execution Registers informs Execution Manager about information storage.&#x20;
15. Execution Manager invokes L1X MultiSig Smart Contract on Ethereum blockchain network to mint NFT on OpenSea Marketplace.&#x20;
16. Event is triggered once NFT is successfully minted on OpenSea Marketplace.&#x20;
17. Rule Engine sends the corresponding event for the transaction struct to the Execution Manager.&#x20;
18. Execution Manager provides the information about successfully NFT minting on OpenSea Marketplace to Execution Register. &#x20;
19. Execution Register stores the information and updates Execution Manager.&#x20;
20. User is informed about successful NFT advertisement and listing on Ethereum OpenSea marketplace.
