How are delimiters determined for custom fields on issue transactions?

Fri, 10 Aug 2018 08:13:35 +0000

The issue commands (issue, issuemore etc) accept custom fields.

I am getting the raw transaction hex for an issuance transaction and decoding it.

When decoding the custom field data, the documentation (https://www.multichain.com/developers/native-assets/) says that the name of a user-defined custom field is null-delimited (i.e. 0x00 0x00). In testing I have encountered at least 4 delimiters that are not null:

0x00 0x0b, 0x00 0x07, 0x00 0x04, 0x00 0x02

Example:

74797065000776656869636c65

74797065 - custom field name (in this case, 'type')

0007 - delimiter

76656869636c65 - custom field value (in this case, 'vehicle')

What are the rules for determining which delimiter is used? Is there a range of hex values that I can treat as delimiters?

Note: I am intentionally not using the 'decoderawtransaction' command.

How to get back data which is present in hexstring back to JSON, the way it was appended using appendrawmetadata

Mon, 13 Jun 2016 08:48:46 +0000

There is a `data` key in the transaction object and its value is a hexstring - 53504b6300010668656c6c6f006f726967696e000468657265. How do you get back the data that I appended in JSON format?

MultiChain Developer Q&A - Recent questions tagged decode

How are delimiters determined for custom fields on issue transactions?

How to get back data which is present in hexstring back to JSON, the way it was appended using appendrawmetadata