GaryRowe
I wrote an article about mitigating this attack vector a while back which might be useful: http://gary-rowe.com/agilestack/2013/07/03/preventing-depend...
It's available under MIT licence: https://github.com/gary-rowe/BitcoinjEnforcerRules
bitcoind sendtoaddress <bitcoin address> <amount>
Works anywhere in the world, not just USA.
Perhaps if someone has a bit of spare cash left over from the day job they could pay someone else to build their project for them (subject to stringent code review). Sort of like Rentacoder but more fine grained.
And for the avoidance of FUD: https://en.bitcoin.it/wiki/Myths
It is worth pointing out that Bitcoin does not require an investment to use it. Merchants can price their goods in bitcoins using a real-time exchange rate to limit their exposure to changing prices.
Since transactions propagate (without confirmations) within a few seconds the merchant can accept the payment and later cash out to, say, USD/GBP/EUR via the exchange or some other mechanism (e.g. direct to a credit card). Alternatively, if part of their supply chain takes payment in bitcoins (e.g. a hosting service for their website, or a supplier of goods) then they can simply pay their overheads with them.
Disclaimer: I am currently long on bitcoins and am using them as part of my long term retirement fund.
I can be found on gary-rowe.com.
1) Building an asset base that provided me with an unearned income equal to whatever my needs are at the time (e.g I need $1000 per month to live, I make an asset that generates $1000 per month without any significant effort on my part)
2) To achieve 1) I would be investing my time and energy in learning web based technologies. Specifically: Java 1.6+, Ruby, RESTful web services, XML, JSON, AJAX, Spring, Maven, GITHub, SVN and so on.
3) To achieve 2) I would spend my evenings writing code for my own medium sized project (e.g. travel review site) with no intention of selling it. My work would involve learning how to make things work efficiently on the web so that my own involvement was kept to zero, with the system continuing to work perfectly.
4) To achieve 3) I would work closely with people who really know how to code for the web. I wouldn't worry about how "cliquey" or anal they were. I would ask them questions and listen carefully to their answers - particularly if I didn't understand them.
Hopefully this will help you, but if you'd like more information then feel free to contact me via www.gary-rowe.com.