ExtraData returned undecoded by api/v1/transaction-info on node.deso.org (ok on bitclout.com)

Maybe same case as previously in #291 ?

Input same for both nodes:

{
"TransactionIDBase58Check": "3JuETwis9NameGLeEDKhqmo1wu5TsJnhWWPCHr95upor1zHn75d9Xo",
"PublicKeyBase58Check":"",
"Limit": 10,
"LastPublicKeyTransactionIndex": 0,
"IsMempool": false,
"IDsOnly":false
}

Output on node.deso.org (just the ExtraData field):

"ExtraData": {"BuyNowPriceNanos": "\u0000"}

on bitclout.com:

"ExtraData": {"BuyNowPriceNanos": "00"}

Start by reproducing the supplied request against api/v1/transaction-info on node.deso.org and bitclout.com, then trace the endpoint's ExtraData serialization or decoding path. Done means the response returns BuyNowPriceNanos as the decoded "00" representation consistently with bitclout.com.

Written by the indexing model from the issue text.