> For the complete documentation index, see [llms.txt](https://l1x-sdk.gitbook.io/l1x-foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/x-talk/x-talk-workflow.md).

# X-Talk Workflow

![Figure 5 Use Case – NFT Advertisement on Ethereum OpenSea Marketplace](/files/17L5TWVLJWBQL9lIKWWy)

**Workflow:**

1. User assigns NFT rights to the L1X MultiSig smart contract on the Binance Smart Chain.
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.
3. Execution Manager informs the Rule Engine about Transaction Type. In this use case, it’s ‘L1X\_Advertisement’.
4. Rule Engine verifies the event and forwards it to the Rule Processor.
5. Rule Processor filters and sends relevant information to the Rule Database.
6. Rule Database gives the response for the associated function call.
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.
8. Execution Manager requests the Execution Register to store the information about NFT transfer to the MultiSig.
9. Execution Register stores the event information and informs Execution Manager.
10. Execution Manager invokes the user and L1X to sign the MultiSig on the Ethereum blockchain network.
11. L1X MultiSig Smart Contract triggers an event once the MultiSig is signed by the user and L1X.
12. Rule Engine sends the corresponding event for the transaction struct to the Execution Manager.
13. Execution Manager updates the Execution Register to store information that L1X MultiSig on Ethereum blockchain network is signed by the user and L1X.
14. Execution Registers informs Execution Manager about information storage.
15. Execution Manager invokes L1X MultiSig Smart Contract on Ethereum blockchain network to mint NFT on OpenSea Marketplace.
16. Event is triggered once NFT is successfully minted on OpenSea Marketplace.
17. Rule Engine sends the corresponding event for the transaction struct to the Execution Manager.
18. Execution Manager provides the information about successfully NFT minting on OpenSea Marketplace to Execution Register.
19. Execution Register stores the information and updates Execution Manager.
20. User is informed about successful NFT advertisement and listing on Ethereum OpenSea marketplace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/x-talk/x-talk-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.