Dr. Maxim Orlovsky
Dr. Maxim Orlovsky
Initial Alekos idea: > **Zero Knowledge**: Make RGB more private by adding some kind of zero-knowledge protocol > * **CA (Confidential Assets)** > * **MW (Mimble Wimble)**
Design a meta-scripting language to encode complex contracts that have more unique or convoluted behaviours. * **Scripting language**: Design the scripting language * **Template**: Integrate the language into an RGB...
Users can redeem tokens by spending a UTXO which was present on the blockchain before a specific date (block height)
A proposal was originally discussed in https://github.com/bitcoin/bips/pull/1239 and than on a mailing list https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019761.html
A number of protocols utilizes pay-to-contract and/or sign-to-contract public key tweaks. Inclusion of the tweak information into outputs (for pay-to-contract) or inputs (for sign-to-contract) as a security measure requires presence...
BIP32 does not work with uncompressed public key; thus, all BIP32-related fields must explicitly require that the public key for the map key value must be serialized in compressed format
This is re-base and refactoring of #589 on top of current master with the released Schnorr signature implementation. Still a WIP. Opening PR to make sure I am on the...
According to https://github.com/LNP-BP/rust-lnpbp/tree/master/elgamal
After @yojoe suggestion, we should reserve a byte in RGB Schema for specifying bulletproof implementation which should be used for validating contracts issued under the schema. For now, it has...