Large JSON image payload saves strange chars before and after hex [closed]

+1 vote

Hello,

i save an large JSON Payload with an png image in the MultiChain. Unfortunately the response hex is modified with some strange Charactes at the begin and at the end and between is the image. The example charactes are

"Ëð]œtóGoˆL‚‚£î•à_;‘Oºú~âF⥹²ÆVjG0D LS[§Nœl·.ÞkÀ4‹Ô'4€=Öwm÷úب5±¿¾µ &¼¯»×c’Ö(Oô¼ìYº­fð«|‰óÇ՗!á@ɲ¯ù¹âIýⴓAQzIÅiX=Ž®jâ’ÿÿÿÿ7v©“@L]Úï gÀ¥! ¼OŸì¢h£"ˆ¬spkq°aCý;[â< /²È±û‚îuýÓNspkeIãâ~6`x‰ª=ÞKö=äuspkk1527673616703ujM¦N"

an then the image is starting.

"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAA+gAAAFACAYAAAAvc1ZOAAAgAElEQVR4Xu3dC7h271wn8O+QEoX0T2kmYqQDIUVRkZBI0UEq1RU6jYmmcphKVCZJ05Rihk7G0EkSQsohUpFMGR0mSQ6VFJ...."


the response hex from this transaction looks like this than:

Ëð]œtóGoˆL‚‚£î•à_;‘Oºú~âF⥹²ÆVjG0D LS[§Nœl·.ÞkÀ4‹Ô'4€=Öwm÷úب5±¿¾µ &¼¯»×c’Ö(Oô¼ìYº­fð«|‰óÇ՗!á@ɲ¯ù¹âIýⴓAQzIÅiX=Ž®jâ’ÿÿÿÿ7v©“@L]Úï gÀ¥! ¼OŸì¢h£"ˆ¬spkq°aCý;[â< /²È±û‚îuýÓNspkeIãâ~6`x‰ª=ÞKö=äuspkk1527673616703ujM¦Ndata:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAA+gAAAFACAYAAAAvc1ZOAAAgAElEQVR4Xu3dC7h271wn8O+QEoX0T2kmYqQDIUVRkZBI0UEq1RU6jYmmcphKVCZJ05Rihk7G0EkSQsohUpFMGR0mSQ6VFJ....v©“@L]Úï gÀ¥! ¼OŸì¢h£"ˆ¬

BR,

 

UPDATE:

Was something completely different. These characters in every hex response. When the payload is to big multichain returns an object with a txid and vout. With the gettxoutdata you can get the larger response than.

 

closed with the note: Found the solution
asked May 30 by A
closed May 31

1 Answer

0 votes
I'm not sure what you're doing, but you should convert the entire data to hex before publishing it in the chain and should only use and see its hexadecimal representation in MultiChain's APIs. Can you show a transcript of the API call you are using to publish it?
answered May 31 by MultiChain
...