From aabb44c2e0189cdeb16bd67a315e05bdac7b129b Mon Sep 17 00:00:00 2001 From: Dusan Morhac <55763425+dudo50@users.noreply.github.com> Date: Sat, 21 Sep 2024 19:37:09 +0200 Subject: [PATCH] Update xcNFT.md --- applications/xcNFT.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/applications/xcNFT.md b/applications/xcNFT.md index 81f9154937b..f5f3c929cf1 100644 --- a/applications/xcNFT.md +++ b/applications/xcNFT.md @@ -36,21 +36,22 @@ xTokens has the following advantages compared to other fungible asset-sharing mo We wanted to create a process of sharing cross-chain non-fungible assets with other chains that is light, efficient, and simple. Our initial design consisted of simple sequence steps shown below: -![Sequential-diagram](https://github.com/user-attachments/assets/50a3e635-3d0a-404e-b978-18434274ca3e) +![Sequential-diagram](https://github.com/user-attachments/assets/a5a3560a-356c-4f8f-bbe2-e3c478fbd1a5) Once the user triggers the function to mint a non-fungible asset, the xcNFT module triggers Parachain A to mint a non-fungible asset if the user is authorised. Once minted, Parachain sends a cross-chain message to Parachain B through the Horizontally Relay Routed Message Passing (HRMP) protocol. If everything succeeds, the user is notified of a success with an event. The process was then designed further with a simple state diagram visible below - that essentially displays the same functionality mentioned above in a more graphical way. -![State-diagram](https://github.com/user-attachments/assets/a0a0b676-2a75-4c98-80b0-d10a5965fccb) +![State-diagram](https://github.com/user-attachments/assets/e7c27924-e7bd-4c88-9c28-4fece68a851e) **Built with emphasis on UX** -UX PoC +UX PoC Our [proof-of-concept](https://github.com/paraspell-research-foundation/xcNFT-Pallet/tree/main) solution was built to be easy to interact with for both developers and users. Events handle debugging of cross-chain messaging, so users are notified if the cross-chain message fails to execute the expected task. The destination selection logic is much simpler - users just type in the destination Parachain ID. **How module infrastructure looks at the current PoC state:** -![Current PoC](https://github.com/user-attachments/assets/42f22745-d18f-443e-9731-a2c9efc2ef77) + +![Current PoC](https://github.com/user-attachments/assets/7066c39c-3cff-4a9f-983c-667fc40b6362) Currently, our [proof-of-concept](https://github.com/paraspell-research-foundation/xcNFT-Pallet/tree/main) solution stores lots of unnecessary data (Both on the origin and destination chain) to ensure the uniqueness of each asset, this will however be greatly improved once the module is reconstructed to use NFTs and Uniques modules for non-fungible asset management. @@ -58,7 +59,7 @@ Currently, our [proof-of-concept](https://github.com/paraspell-research-foundati (Notice xcNFT rebrand from xNFT) -![After PoC](https://github.com/user-attachments/assets/526c06bc-135a-4ca8-8f71-a6f546fe0465) +![After PoC](https://github.com/user-attachments/assets/feea0805-a1e4-46f9-9fc4-fe7d4975c342) All non-fungible and collection related data will now be handled by NFTs and Uniques pallet which for non-cross-chain transfers will be interacted with directly and for cross-chain transfers will be interacted with through specialized parsing functions meant to parse cross-chain instruction into specified calls on destination chains. The module will also include many additional cross-chain and non-cross-chain functions further enhancing usability for developers and users. @@ -145,7 +146,7 @@ We have already built a functional demo / proof of concept for the xcNFT pallet We have also submitted a paper regarding this concept to [Brainz 2024 conference](https://brains.dnac.org/2024/) that specifies in Blockchain related research. This paper got accepted and we will present it on the conference in Berlin in person. -brainz 2024 +brainz 2024 ## Development Roadmap :nut_and_bolt: