Transaction

e7e9d09ceee2e941c8cbc8b9957322b3cb0da2399e8889a10b9c03e4ea54a036
2024-03-21 21:32:47
0.00000011 BSV
(
0.00487277 BSV
-
0.00487266 BSV
)
10.3 sat/KB
1
74,001
1,067 B

2 Outputs

Total Output:
0.00487266 BSV
  • j"19HxigV4QyBv3tHpQVcUEQyq1pzZVdoAutM.<div class="post">I like that in libraries for the external API's, but you can probably tell from the code that I'm not a fan of it for interior functions.&nbsp; Big obligatory comment headers for each function space out the code and make you hesitate about creating a small little function where the comment header would be bigger than the function.&nbsp; They're some trouble for maintenance, as changes to the function then require duplicate changes in the comment header.&nbsp; I like to keep code compact so you can see more code on the screen at once.<br/><br/>To add them now at this point, what would be written would just be what's obvious from looking at the function.<br/><br/>The external API we have, in rpc.cpp, the usage documentation is in the help string.<br/><br/>Sorry to be a wet blanket.</div> text/html
    https://whatsonchain.com/tx/e7e9d09ceee2e941c8cbc8b9957322b3cb0da2399e8889a10b9c03e4ea54a036