Dr. Maxim Orlovsky
Dr. Maxim Orlovsky
After @yojoe note, > A public key Pi appears multiple times in a scriptPubKey. (Although I don’t know of any example, this seems to be possible, else we wouldn’t have...
Discussion: https://t.me/rgbtelegram/13775 > Probably we can upgrade LNPBP-4 with Merkle tree, such that we can move up to 64k of assets for the same UTXO w/o increasing the size of...
Consider removing bulletproof data from single-use-seal commitments: this will add scalability with aggregation over history + zk upgredabiliy and replacability Update: during dev call on the 23rd of Sept 2020...
Right now only parties owning some of RGB contract state (i.e. able to spend an UTXO with some assigned RGB state data, i.e. close a seal over next state) can...
(updated) I think the best way for RGB versioning is to have LN-like set of features, with even/odd differentiation, and commit to it in a Schema. This version will define...
1. DBC tweak individual keys (pay-to-contract)/signatures (for sign-to-contract), taking `container` and message, and producing `commitment` (tweaked container version) and modified container, where the tweak information is added. Next, container is...
Schema: https://github.com/LNP-BP/LNPBPs/blob/master/lnpbp-0020.md What was changed: - [ ] Removed dust limit - [ ] Multiple inflation rights with better control over total inflation - [ ] Epoch-based burn and burn-and-replace...