Api returns wrong state
NorbertBodziony opened this issue · 1 comments
NorbertBodziony commented
Here is example of incorrect message returned from API 465
is valid and correct but 466
seems like there is error in memo
and memohex
fields
465:
block_height: 965936
datetime: 1599640236
position: 0
txid: "e963885bacf4abdef0f601a31aea86e3e3a52f4990cc00436d6636729ff69dc8"
amount: 0
address: "zs1j5udj8n6yquks5pv00aqg86dhhjpr7fq2906zqqpn0jktfg654qmcz9tm4gslutpjnwkzaemgsk"
memo: null
memohex: "ff05116cec3c9f25f401fc57615cf70ba8bc559a35d939d4278cd6ce38196967318c5aaf57fd9da84478067953a96f20e169061a4c72a91486ea0b918ba52738641c015f58925f0000000000000000000000000000000000000000000000000000000000000000000000000000000073757065726d616e000000000000000000000000017a73313732656d38726d66786d617577736476777436786d37676e7437746d71356b6a68786434636d3568676c6b676176766b766b647136746636687876386436737432373530716c71326637790000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
__proto__: Object
466:
block_height: 966466
datetime: 1599680076
position: 0
txid: "0bde9dd9002a151fcc457c9e1c3c34ea9b166396d194eab3b2d99d31912e8a96"
amount: 0
address: "zs1j5udj8n6yquks5pv00aqg86dhhjpr7fq2906zqqpn0jktfg654qmcz9tm4gslutpjnwkzaemgsk"
memo: "0xff0539e827203bf48a263e8b6d078df57e29ee2dc838917e7d472f8c18877de4e5f569e35088317753d10ce7f821eb843e890d4b2be0eb6457329691649d5f3d4dae005f592e2c00000000000000000000000000000000000000000000000000000000000000000000000000000000626f73746f6e7a636173686c6974650000000000017a7331756b33376b356d63346b337163707939686a78773976323330346d61376461666a7138633036653338787a66393876356a6e363270747371686b676e766a38383579703579723637646e7"
memohex: "3078666630353339653832373230336266343861323633653862366430373864663537653239656532646338333839313765376434373266386331383837376465346535663536396533353038383331373735336431306365376638323165623834336538393064346232626530656236343537333239363931363439643566336434646165303035663539326532633030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030363236663733373436663665376136333631373336383663363937343635303030303030303030303031376137333331373536623333333736623335366436333334366233333731363337303739333936383661373837373339373633323333333033343664363133373634363136363661373133383633333033363635333333383738376136363339333837363335366136653336333237303734373337313638366236373665373636613338333833353739373033353739373233363337363436653700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
__proto__: Object
adityapk00 commented
I think this looks correct to me.
For 456: The memo was sent using the hex feature, so it was sent as a binary memo
For 466: The memo was sent as a string, so the "memohex" field is showing the binary-hex version of the string. Hex (30) => Decimal(48) = Ascii code for "0", which is the first char in the memo.