NFTs & Privacy: Verifiable Credentials (VCs) can enhance NFT ownership verification.
25 May 2023, 15:52
📚🎨 NFTs & Privacy: Verifiable Credentials (VCs) can enhance NFT ownership verification.
With VCs, users can prove their ownership without exposing sensitive details like wallet addresses.
Could NFT projects benefit from implementing VCs? Share your thoughts 👇
Same news in other sources
1Iron FishIRON #3122
25 May 2023, 16:06
Version Update: Iron Fish v1.3.0 has been released!
This release includes an improvement to transaction generation aimed at preventing new transactions from getting stuck or dropping from the network. (https://github.com/iron-fish/ironfish/pull/3932)
Every transaction on Iron Fish includes spend descriptions that help to prove that the sender can spend the notes that they are using in a transaction (https://ironfish.network/learn/whitepaper/transaction#spend-description)
In some cases, a transaction created before the chain re-organizes from a fork become invalid after the chain has changed. This release reduces the likelihood of an invalid spend description in this case by using a 'confirmation range' to generate a spend using a block that is behind the head of the chain and less likely to be changed.
This will help to ensure that transactions remain valid and can be included in the chain quickly.
Other improvements:
Node performance improvements to data serialization
Fee Selectors for send, mint, and burn commands use selected account and confirmations (including changes from a first-time Iron Fish open source contributor, whohideonbug!)
Check out the release notes for all the changes:
Version Update: Iron Fish v1. 0 has been released.
Version Update: Iron Fish v1.3.0 has been released!
This release includes an improvement to transaction generation aimed at preventing new transactions from getting stuck or dropping from the network. (https://github.com/iron-fish/ironfish/pull/3932)
Every transaction on Iron Fish includes spend descriptions that help to prove that the sender can spend the notes that they are using in a transaction (https://ironfish.network/learn/whitepaper/transaction#spend-description)
In some cases, a transaction created before the chain re-organizes from a fork become invalid after the chain has changed. This release reduces the likelihood of an invalid spend description in this case by using a 'confirmation range' to generate a spend using a block that is behind the head of the chain and less likely to be changed.
This will help to ensure that transactions remain valid and can be included in the chain quickly.
Other improvements:
Node performance improvements to data serialization
Fee Selectors for send, mint, and burn commands use selected account and confirmations (including changes from a first-time Iron Fish open source contributor, whohideonbug!)
Check out the release notes for all the changes: https://github.com/iron-fish/ironfish/releases/tag/v1.3.0