Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Probably best to disable receiving by IP unless you specifically intend to use it.&nbsp; This is a lot of surface area that nobody uses that doesn't need to be open by default.<br/><br/>In storefront cases, you would typically only want customers to send payments through your automated system that only hands out bitcoin addresses associated with particular orders and accounts.&nbsp; Random unidentified payments volunteered to the server's IP address would be unhelpful.<br/><br/>In general, sending by IP has limited useful cases.&nbsp; If connecting directly without a proxy, the man-in-the-middle risk may be tolerable, but no privacy.&nbsp; If you use a privacy proxy, man-in-the-middle risk is unacceptably high.&nbsp; If we went to all the work of implementing SSL, only large storefronts usually go to the trouble of getting a CA cert, but most of those cases would still be better off to use bitcoin addresses.<br/><br/>I uploaded this change to SVN rev 156.&nbsp; The switch to enable is "-allowreceivebyip".<br/><br/>Senders with this version will get the error "Recipient is not accepting transactions sent by IP address".&nbsp; Older version senders will get "Transfer was not accepted".<br/><br/>I used a different name for the switch because "-allowiptransactions" sounds like it includes sending.&nbsp; If there's a better name for the switch, we can change it again.</div> text/html