XLS20 NFT Upgrader #76
ma06rii
started this conversation in
Ideas (pre standard proposal)
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
XLS20 NFT Upgrader
Key terms
IOU token - A custom issued token currency on the XRP Ledger, more information about tokens can be found here
XLS14 NFT - A proof of concept standard proposed for Non-Fungible Tokens (NFTs) on the XRP Ledger, more information can be found here
XLS20 NFT - A proposed standard for native support of NFTs on the XRP Ledger, more information can be found here
What are we doing?
The XLS20 upgrade to the XRP Ledger represents a significant step forward in ledger capabilities and enables the support of NFTs as representations on the ledger.
From our research NFTs exist in a number of ways on the current ledger, but mostly in the form of XLS14, IOUs, and much less so XLS19 tokens.
The developer team at Peerkat would like to propose a tool to initially facilitate the upgrade of XLS14 and IOU tokens to the new XLS20 standard, with a view to allowing other developers to extend this tooling.
This idea is open to suggestions/feedback and open to anyone who would like to contribute.
Proposal
Overview
The proposed approach is akin to swapping one token for another.
As a headline, token holders are responsible for upgrading their own NFT in their wallet. They will have a specific address to send the NFT to, which would ideally be hosted and managed by the original XLS14 or IOU token issuer. The token holder would be able to send their tokens using a wallet service such as Xumm App or any other XRPL wallet. The token holder will be responsible for checking and accepting an offer for the new XLS20 token.
Many NFT projects have chosen to create their own issued token (IOU) currencies to represent their NFTs. The idea is that the community can engage in their projects whilst awaiting for the XLS20 NFT standard.
Please see diagram below which describes the proposed upgrade process for XLS14 or IOU tokens:-
Configuration settings
Prior to running the upgrader service, the administrator who is hosting the service (ideally this will be the original issuer of the XLS14 or IOU token), will need to setup initial configuration settings using environment variables as follows :-
Service detail
1. Log all transactions received to the brand upgrader wallet account
2. Log all new XLS20 NFTs minted
3. Log all transaction creating a “SellOffer” for XLS20 NFTs
4. Log all transactions that send “Payment” of XLS14 NFT or IOU tokens back to the original "Issuer" XRPL account
5. Log all “Payment” transactions received to request for XLS14 token or IOU token to be returned
Internal criteria checks
A series of tasks could be performed before the upgrader service executes an action via the XRPL. This is to ensure that valid transactions have been received and appropriate resources are available to complete a request. Below is an list of example tasks which could be performed, but this list is not exhaustive :-
Default memo messages
The memo messages below must be included when sending payments to the NFT upgrader service XRPL wallet. These are defined messages that must be used by everyone who would like to use this upgrade implementation. The messages will help the NFT upgrader service complete the correct tasks for the intended actions. The payments are usually initiated by a token holder who would like to trigger certain actions regarding upgrading their XLS14 NFT or IOU token.
Considerations
Token “Issuers” can use the NFT upgrader service dashboard to help communicate “SellOffer” IDs to token holders. It can also help provide transparency and token holder trust in the upgrade process.
A public register can be used to maintain a list of verified ‘brand upgrader details’ for different projects. This can help token holders find accurate information. This register can be created by a third party or included in existing lists such as the xrp.community.
A third party could develop an Xumm xApp dedicated to supporting token holders through the upgrade process. This could help support a user-friendly experience for token holders when upgrading.
A possible downside of this approach is that token holders are required to trust that the administrator of the NFT upgrader service will burn the received XLS14 NFTs or IOU tokens by sending it to a blackholed account, which will most likely be the original "Issuer" account of the token. If this service is run by the initial ”Issuer” of the XLS14 NFT or IOU token, it is assumed they would want to maintain the integrity of their project.
Please note that this proposed implementation may not be suitable to support upgrading all XLS14 NFTs. A token holder could check if their XLS14 or IOU token is upgradeable by looking up a public register of projects offering or running the “NFT Upgrader Service”.
Sologenic will be providing their own dedicated ‘swap’ service to upgrade XLS14/SOLO tokens. More information about this ‘swap’ service can be found here.
Beta Was this translation helpful? Give feedback.
All reactions