Dr. Maxim Orlovsky
Dr. Maxim Orlovsky
After discussion with Andrew Poelstra it became obvious that the previous decision of storing public key tweak information within PSBT as a single value (https://github.com/LNP-BP/rust-lnpbp/issues/86) will be insecure and incompatible...
Copy of discussion from RGBv1 audit: @dr-orlovsky> do you remember why we originally stick to pay-to-contract and not sign-to-contract commitments? @fedsten> there were some issues with the multisig, as the...
RGB genesis must: - encode (with strict_encode) all chain parameters - commit (with commit_encode) only to network genesis block hash This will allow clients to work with arbitrary networks, but...
With 4 invoice formats from https://github.com/LNP-BP/devcalls/issues/25 + compatibility/interoperability with * https://github.com/LNP-BP/LNPBPs/issues/53 * https://github.com/LNP-BP/LNPBPs/issues/54 * https://github.com/LNP-BP/LNPBPs/issues/55 Pay special attention to design criteria and points in https://github.com/LNP-BP/devcalls/issues/25#issuecomment-693450076
With support on LN URL and multiple failback payment methods
Right now RGB contracts may have a single genesis (non-committed) and the rest of transitions must be committed with bitcoin transaction graph. For a decentralized issuance a non-committed multiple issuances...
Pruning procedure is a proposed mechanism for truncating amount of data clients need store for their assets history (and pass between them during asset transfer). The currently considered procedure for...