Change Details

Right now, we have cashtab-specific parsing of OP_RETURN in cashtab. Desired end state is generic parsing of OP_RETURN for all spec'd OP_RETURN use on the eCash network, also with a standard way of handling unknown spec or off-spec usage. Cashtab has the most mature parsing, so we use it as a starting point. Add OP_RETURN and EMPP parsing to ecash-lib. Suggest an interface for ParsedOpReturn, a general type for parsing a string OP_RETURN as returned in a chronik `Tx`

Right now, we have cashtab-specific parsing of OP_RETURN in cashtab. Desired end state is generic parsing of OP_RETURN for all spec'd OP_RETURN use on the eCash network, also with a standard way of handling unknown spec or off-spec usage. Cashtab has the most mature parsing, so we use it as a starting point. Add OP_RETURN and EMPP parsing to ecash-lib. Suggest an interface for ParsedOpReturn, a general type for parsing a string OP_RETURN as returned in a chronik `Tx` We intentionally do not bump the version of ecash-lib, as this is still WIP. Will hold off until we have a portable and useful full parseOpReturn function.

Right now, we have cashtab-specific parsing of OP_RETURN in cashtab. Desired end state is generic parsing of OP_RETURN for all spec'd OP_RETURN use on the eCash network, also with a standard way of handling unknown spec or off-spec usage. Cashtab has the most mature parsing, so we use it as a starting point. Add OP_RETURN and EMPP parsing to ecash-lib. Suggest an interface for ParsedOpReturn, a general type for parsing a string OP_RETURN as returned in a chronik `Tx` We intentionally do not bump the version of ecash-lib, as this is still WIP. Will hold off until we have a portable and useful full parseOpReturn function.