Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM™<div class="post">Couple of quick suggestions:<br/><br/>Using the key name "class" will cause problems for, at least, JavaScript, and probably other languages where "class" is a reserved word.&nbsp; "type" or "variety" or some other synonym will cause fewer problems later.<br/><br/>Or, maybe better, get rid of that field and just report credits as positive numbers and debits as negative.&nbsp; And add a separate "generated" field (boolean true or false).<br/><br/>Since each entry refers to a transaction, I'd suggest adding a "tx_id" SHA256 hex-encoded transaction id.&nbsp; Then listtransactions would play nicely with the refundtransaction JSON-RPC extension (and maybe a future gettransactiondetails that let you get transaction parents, which block the transaction was in, and so on).<br/><br/>Code to get that would look something like:<br/><div class="codeheader">Code:</div><div class="code">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; uint256 tx_hash = transaction.GetHash();<br/>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; string tx_id = tx_hash.GetHex();<br/>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; mapJSONResponse.push_back(Pair("tx_id", tx_id));<br/></div></div> text/html