-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] - Misleading unsafeHashableScriptData
#474
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
You can use
|
But I don't think it matters if you're creating the data from scratch (programatically) rather than by deserialisation from a bytestring. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
External
Area
Other HashableScriptData
Describe the feature you'd like
We have been successfully using
unsafeHashableScriptData
however its description recommends NOT to use it:However it is unclear how to construct a
ScriptRedeemer
fromScriptData
if we shouldn't useunsafeHashableScriptData
- in general, if usage ofunsafeHashableScriptData
is discouraged, it is unclear how to go fromScriptData
toHashableScriptData
.Please either change the description of
unsafeHashableScriptData
or provide other (safe?) means going fromScriptData
toHashableScriptData
.The text was updated successfully, but these errors were encountered: