rgb-archive / rust-rgb-2019 Goto Github PK

Depends on rgb-archive/spec#57 once it will be included into the spec

When implementing some RGB proofs, it seems the txid has a circular dependence when the pay-to-contract scheme is used. The proof references the on chain Tx to which it is bound in the bind_to field

My understanding:
->bind_to references original_txid in proof
-> proof used to tweak public keys of some outputs
-> Tx output public keys have changed, therefore SHA256d(Tx) = new_txid != original_txid
-> bind_to is changed to now reference new_txid
-> etc.

As far as I can tell, the current behaviour is not explicitly defined. Should the bind_to field be omitted when tweaking the keys and verifying commitments?

According to the specification https://github.com/rgb-org/spec/blob/master/01-rgb.md#transfer-proofs

By using an MMR (Merkle Mountain Range) or a sparse Merkle Tree it should be possible to obfuscate which assets are being moved in a proof, without making the validation checks too hard.

According to the spec: https://github.com/rgb-org/spec/blob/master/01-rgb.md#address-based-vs-utxo-based

In order to simplify their usage by Bifrost, Kaleidoscope and other dependent services