Skip to content

OP_RETURN transactions now start with OP_FALSE always right? #111

@stevenzeiler

Description

@stevenzeiler

When parsing the tokenized action this library never takes into account the fact that data scripts now always are OP_FALSE OP_RETURN. Rather the library always assumes that the script begins with OP_RETURN which causes breaking behavior since the Feb, 2020 upgrade.

Buffer.from(parts[1], 'hex').toString('ascii'),

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions