Tracking pending consensus changes

[dr-orlovsky]

This issue is an epic used to track all potential or planned RGB consensus changes in this and underlying libraries. For more about consensus breaking changes and consensus libraries please refer to the https://spec.rgb.tech/devs/breaking-things and https://spec.rgb.tech/consensus-level/system-libraries

• Use secp256k1-zkp for bulletproofs & Pedersen commitments #9
• Use new strict types system and schema #125 (before: Upgrade to Confined encoding from strict encoding)
  • Refactor strict_encoding crate LNP-BP/client_side_validation#97
  • Strict encoding should provide explicit guarantees on collection sizes LNP-BP/client_side_validation#98
  • Provide size-restricted encoders for writing the data LNP-BP/client_side_validation#107
• Solving contract state determinism for metadata #117
• Changes to EmbeddedVM #116
• A fix to "RGB21 NFT" schema bug discovered and discussed in Fix blank transition type rgb-std#6

Bugfixing these issues may also potentially break consensus: fixed and the fix was not a consensus-breaking

• Two anchors randomly fail to merge with ~10% probability LNP-BP/client_side_validation#110