-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFT implementation (mint on sale + generate custom file) #211
Comments
As seen on Discord, a RGB implementation on Nodl in on its way. |
To consider : a v1 testnet on Ordinal or Counterparty (depending of the maturity and availability of nodeJS existing packages) to tease the feature and make a PoC before a v2 on test/mainnet with RGB once it's properly assimilated to Nodl hosting |
3-5 days |
TBD
(for now only for products with PDF digital file)
2 step process :
Mint NFT on "collectible" product sale
When I buy a digital file with "collectible" flag, on /order, I have to fill one of my BTC wallet public address for NFT mint purpose.
Once the order is paid, I can download my generic digital file (in all case).
I'll be notified by my wallet once the NFT is minted.
When I go to /claim/{product-id} instead of /product/{product-id} :
On "Claim your collectible" form, I can :
From here, customer, on his/her bitcoin wallet, will generate a signature from his/her public key and a custom message (resource : https://medium.com/@bytether/how-to-sign-a-message-with-a-mycelium-android-wallet-e82fce04860 )
Then, customer fill on the form the same infos (public key, message, signature).
Check the signature :
Once the collectible order is paid :
The text was updated successfully, but these errors were encountered: