Skip to content
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

Verifier string parse/encode incompatibility #1235

Open
kralverde opened this issue Jun 15, 2023 · 0 comments
Open

Verifier string parse/encode incompatibility #1235

kralverde opened this issue Jun 15, 2023 · 0 comments

Comments

@kralverde
Copy link
Contributor

Currently, verifier strings are limited to 80 characters. Making a null tag vout for a verifier uses OP_PUSH (

script << OP_RVN_ASSET << OP_RESERVED << ToByteVector(vchMessage);
). Reading the verifier hardcodes an allotment of 1 byte for length (
vchAssetData.insert(vchAssetData.end(), scriptPubKey.begin() + OFFSET_THREE, scriptPubKey.end());
). The last 1-byte OP_PUSH is 0x4b (75 dec) making this de-facto the longest verifier string as longer will error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant