search

EOSIO / eosjs-fcbuffer

Serialization library geared towards immutable data storage such as blockchains.
27 stars 18 forks source link

the decode result is still unreadable #8

Open oday0311 opened 5 years ago

oday0311 commented 5 years ago

i am trying to decode the action data with 90a762a661d33055e021d2b161d3305501000000000000000448415348000000fb015468652046414952455354205361746f7368692d7374796c6520446563656e7472616c697a65642043727970746f20436173696e6f204275696c74206f6e20454f532c20757365206861736820746f20647261772077696e6e696e67206e756d6265727320746f2067756172616e746565206162736f6c75746520466169726e6573732c204e6f204368616e636520666f72204368656174696e6720617420416c6c212047656e65726f757320726577617264732c206869676820726566657272616c20626f6e7573212068747470733a2f2f656f73686173682e77696e3f7265663d656f73686173686167656e74265f723d3238623332623935

definitions = { account_name: 'fixed_string32', // CustomType: built-in type message: { // struct fields: { from: 'uint64', to: 'uint64', quantity: 'uint128', memo: 'string' // built-in type } } }

"from":"3186074846210831409","to":"4119727365518276665","quantity":"58757049346750096509997622369421765687","memo":"3,210,177,97,211,48,85,1,0,0,0,0,0,0,0,4,72,65,83,7"

from and to should be name, but i convert the uint64 in eos , the name can not match, also the memo seems in wrong result?

oday0311 commented 5 years ago

@jcalfee, can you give me more info

jcalfee commented 5 years ago

I think "from" and "to" should be of type name instead of uint64 .. I have not looked at this in a while. It was replaced in eosjs 2.0 ..