Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM“<div class="post">Hey,<br/><br/>First off I must say that this is an amazing concept. I have been dreaming of a P2P money system for a LONG time.<br/><br/>You have my complete kudos and respect.<br/><br/>I have a few suggestions:<br/><br/>- When the bitcoin software establishes a connection with a peer (client TCP socket) have the client send the handshake string. Right now you have the server (server TCP socket) send the handshake. My reasons for this are anonymity of course. It is far too easy for ISPs to portscan clients and detect they are running this program.<br/><br/>- Use some sort of encryption during the handshake (sort of goes with the statement/request above) to obfuscate what the software is during DPI (deep packet inspection). I am really thinking about people in non-free (as in freedom) countries such as China/Iran.<br/><br/>- Some sort of an API is needed so that this system can be integrated with websites to provide instant-on services. A simple https receipt mechanism would do wonders. Have the client post each incoming payment to an https url with all of the relevant information and provide status updates. Also an outbound payment mechanism would be nice. So one could automate payments (and batch payments) outbound. Status could be returned via the https receipt interface.<br/><br/>- Static port/Random port. Have a setting to randomly assign the port that it runs on. (also be able to set it statically for very restrictive firewalls).<br/><br/>- UPnP support. Have the client automatically create the port forward on upstream routers. Enabled by default. Can be turned off in the options menu.<br/><br/>- Ability to compile a headless (console only) install for *NIX systems. Also have the ability to just run as a network service. Perhaps with a telnet-able port for control (or even a unix socket would be ok).<br/><br/><img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/></div> text/html