adshares/ads

log_account: tx.data has 128 redundant bytes

Closed this issue · 1 comments

In response for log_account is returned tx.data object. It has encoded transaction data and 128 NULL bytes.

Example

0F01000000000003000000D87E9B5B0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    uint8_t ttype {TXSTYPE_SAV};///< command type
    uint16_t abank{0};          ///< source node
    uint32_t auser{0};          ///< source user
    uint32_t amsid{0};          ///< msg id
uint32_t ttime{0}; ///< time

Why is NULL data appeneded to tx.data?

It is a placeholder for actual account data that is filled by the node before transactions is confirmed by the network. Maybe it shouldn't be returned in this context