We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From the bitcoin ordinal code example: https://github.com/casey/ord/blob/938b5cc97d48d026fd9250eae661d1e87286b377/src/inscription.rs#L439 we will need to push []byte{1} as a mark for contentType for bitcoin inscription, but current script builder AddData will convert this into small number OPcode AddData So in the encode string, instead of 0101(data length 1, data 1) the builder will encode this into 0x51(OP_01)
I'm not sure if we will support the bitcoin ordinal inscription in the future, a push_exact_data would be preferred here
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From the bitcoin ordinal code example:
https://github.com/casey/ord/blob/938b5cc97d48d026fd9250eae661d1e87286b377/src/inscription.rs#L439
we will need to push []byte{1} as a mark for contentType for bitcoin inscription, but current script builder AddData will convert this into small number OPcode
AddData
So in the encode string, instead of 0101(data length 1, data 1) the builder will encode this into 0x51(OP_01)
I'm not sure if we will support the bitcoin ordinal inscription in the future, a push_exact_data would be preferred here
The text was updated successfully, but these errors were encountered: