j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMh<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=611.msg6642#msg6642">Quote from: gavinandresen on July 30, 2010, 01:18:06 PM</a></div><div class="quote">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. "type" or "variety" or some other synonym will cause fewer problems later.<br/></div><br/>Can you be more specific? All mainstream programming language seem sensibly insensitive to abitrary string contents, JS included. String content can certainly include language-reserved keywords and parsing tokens.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=611.msg6642#msg6642">Quote from: gavinandresen on July 30, 2010, 01:18:06 PM</a></div><div class="quote">Since each entry refers to a transaction, I'd suggest adding a "tx_id" SHA256 hex-encoded transaction id. 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"> uint256 tx_hash = transaction.GetHash();<br/> string tx_id = tx_hash.GetHex();<br/> mapJSONResponse.push_back(Pair("tx_id", tx_id));<br/></div></div><br/>Added, thanks for the suggestion.<br/></div> text/html
https://whatsonchain.com/tx/542dffbe68bda126e3fc3c54ebbbcbeee70501d974e9b460062dda8dbf8ffeaf