Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¸<div class="post">Sorry to keep replying to myself but I am posting these little snippets as I stumble across them.&nbsp; I am currently documenting the -dropmessagestest command line switch and I see a minor improvement you may want to add to the code.&nbsp; Currently if a message is dropped as a result of this switch, a debug message is printed to the log indicating a message was dropped.&nbsp; It would probably be pretty useful to print the contents of the dropped message to the log as well.&nbsp; This way if one of the dropped messages really does break bitcoin, you can see what message caused the problem.&nbsp; It would also allow you to later re-create the problem by adding a filter on the incoming network stream blocking messages like the one that broke it the first time so that you can verify that you have fixed the issue later on.<br/><br/>If you think it is a good idea I can probably add this myself as well.<br/><br/>-Buck</div> text/html