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
Another proposal by @lorisleiva was to include the metadata with no processing/clean up under the compression section, to make it easier for users to get the exact metadata needed for instructions such as verify_creator that take MetadataArgs as an argument.
Then maybe the normal API could return a trimmed string, and under compression.metadata it could be the raw untrimmed version which should help with hashing? Just a thought, I know it doesn't resolve the talk about \0
Another proposal by @lorisleiva was to include the metadata with no processing/clean up under the compression section, to make it easier for users to get the exact metadata needed for instructions such as
verify_creator
that takeMetadataArgs
as an argument.Then maybe the normal API could return a trimmed string, and under compression.metadata it could be the raw untrimmed version which should help with hashing? Just a thought, I know it doesn't resolve the talk about \0
Originally posted by @danenbm in #93 (comment)
The text was updated successfully, but these errors were encountered: