-
Notifications
You must be signed in to change notification settings - Fork 167
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
Bitcoin Cash #2763
Comments
Hi Monsterbitar - |
Sure, on BCH we have Bitcoin Cash Metadata Registries: https://github.com/bitjson/chip-bcmr The equivalent of the Contract Address would be the CategoryID, the transaction for the output that was spent while creating the original token, which all child tokens also carry (their identity explaining what token they are). The equivalent of the TokenID I guess is the tokens commitment field, which for NFTs is the unique number in the minted serie identifying the specific NFT for that CategoryID. Or something like that, I actually don't know this from the back of my hand yet, here's the full spec for cashtokens: https://cashtokens.org/docs/spec/chip |
As practical examples, here's the mining of BLISS: https://explorer.salemkode.com/tx/5a4f6b25243c1a2dabb2434e3d9e574f65c31764ce0e7eb4127a46fa74657691 And here's an overview of the issued BLISS tokens: https://explorer.salemkode.com/token/5a4f6b25243c1a2dabb2434e3d9e574f65c31764ce0e7eb4127a46fa74657691 (Bliss uses the authchain, so on-chain BCMR records) |
Last year I used nft.storage to upload some art to IPFS for a project of mine, and today while I was going over my old notes I tried to update by adding more art, but it turns out that the version I used last year is now "classic" and no longer operational.
(as in, there's a banner at the top saying I can't use it to upload more stuff)
So I tried using the new version, but when I try to upload it requires that I say what chain my contract resides on, and as it turns out I don't have a special magic contract, just native Cash Tokens on the Bitcoin Cash (BCH) chain.
... but since I can't choose that, I can no longer use nft.storage.
The text was updated successfully, but these errors were encountered: