Skip to content
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.

Depreciate OP_RETURN commitments for contract deployments #107

Closed
dr-orlovsky opened this issue Aug 5, 2019 · 0 comments
Closed

Depreciate OP_RETURN commitments for contract deployments #107

dr-orlovsky opened this issue Aug 5, 2019 · 0 comments

Comments

@dr-orlovsky
Copy link
Contributor

After discussion with @giacomozucco it was decided to depreciate OP_RETURN commitments for contract deployments. OP_RETURN is a legacy scheme required only for the compatibility with hardware wallets (see #62 for some discussion on the topic relating proofs). So while it is important for the proofs to be compatible with hardware wallets, it is not the case for the contracts, which may be rather deployed with HSMs.

@dr-orlovsky dr-orlovsky added this to the RGB-v0.5.0 milestone Aug 5, 2019
@dr-orlovsky dr-orlovsky self-assigned this Aug 5, 2019
@dr-orlovsky dr-orlovsky added this to To do in RGB via automation Aug 5, 2019
@dr-orlovsky dr-orlovsky moved this from To do to PR being prepared in RGB Aug 5, 2019
RGB automation moved this from PR being prepared to Done Aug 5, 2019
@dr-orlovsky dr-orlovsky removed this from Done in RGB Apr 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant