You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: