Just curious knightmb, to quiet all the naysayers, can you point us to the transaction of the donation to wikileaks?
oh come on, are you serious? Cut him some slack. This guy is in no position to have to prove anything. Believe what you want and give him the benefit of the doubt so he can play a "normal" part in this community again. @ knightmb: As much as I wish you to pursue happiness in your own chosen way, playing the "normal" part in this community is over. With all your money and background comes a lot of power and responsibility. You can step up to it, take it in your own hands and build something meaningful, or abandon the chances destiny gave you. Its your choice. But with regards to Bitcoin things will never go back to normal for you. Depends what normal was .... sleeping under an Interstate flyover and cradling a bottle of cheap red to sleep is normal for some folks ... before (and after?) bitcoin.
|
|
|
Multi-sig transactions and/or two-factor authentication can remove most of the risk of a 'Bitcoin card' ... so that the irreversibility is not a problem, except in an infinitesimally small number of cases, an acceptable level of risk.
|
|
|
So will any of this be Open Source?
Seeing as it is called OpenPay ... and the brain-storming seems to be free-to-air .... just wondering.
|
|
|
Can I ask you what kind of resources a electrum server uses or rather what kind of resources I should dedicate to it to have it running stable.
The HOWTO is instructive http://gitorious.org/electrum/server/blobs/master/HOWTOI thought this was a consideration .... Important notice: This is a *very* long process. Even on fast machines you can expect it to take hours. Here are some benchmarks for importing ~173.000 blocks (size of the Bitcoin blockchain at the time of this writing):
System 1: ~9 hours. * CPU: Intel Core i7 Q740 @ 1.73GHz * HDD: very fast SSD System 2: ~55 hours. * CPU: Intel Xeon X3430 @ 2.40GHz * HDD: 2 x SATA in a RAID1.
|
|
|
All your monies are tainted already, I thought everybody knew that? .... they don't call it filthy lucre for nothing!
"Render unto Caesar what is Caesar's .... " you know the rest.
|
|
|
I'm not questioning the tech tbh, but more whether people would prefer this over mobile phones (a social problem) despite improved security. Phones can do way more than this device so I'm not sure. I think fungibility will come into it ... money transfer with a phone will not be very private and difficult for the average user to make it so (particularly with the aggressive, predatory data-miners like google listening in). From what I can see using money on these cards can easily be as good as cash, electronic cash. Also seems like a 'hardware wallet' concept like this can be secure enough to extend to a "savings card" and a "spending card" .... wouldn't want to leave more than a hundred btc on a phone.
|
|
|
So are you going to swear to us that you keep no logs of incoming and outgoing transactions? And that you too won't disappear suddenly? Obviously you aren't quite as anonymous as a Tor operator, so you can't bill your service as equivalent in terms of privacy.
I never said there were no logs kept. Any incentive to remain honest for a hidden service collecting bitcoins instantly disappears when they see that their customer holdings exceed the revenue they could expect from fees over X years. Go for it, I'll happily pass. That's a good point, is there a way to exclude a human from the process? Something like open source botnet, that has sole purpose to act as giant mixer. Done, it's called bitcoin
|
|
|
This is more a question about the design philosophy of the server than specifics;
Why SQL database?
|
|
|
I have two questions:
- ¿How are you supposed to laundry bitcoins if only tainted coins owners use your service? - If you want to mix coins: why perfectly clear bitcoins users should use your service?
Because "If you've done nothing wrong, you've got nothing to hide" is a load of BS. Do you really want your boss (who pays you in bitcoins because we're imagining a hypothetical future in which bitcoins are mainstream) finding out that you're spending your paycheck on porn? Is that the sort of future you really want? If you've done nothing wrong they've got no reason to look .... is the obvious corollary to the old statist chestnut ... and the antidote of course. Presumption of innocence .... was the basis of all common law until he present era of big, fat, nosey state, we are all criminals now under the presumption of guilt doctrine.
|
|
|
Capital controls are symptomatic of failed/failing states.
Capitalism and free markets can not be denied, they just trash the state system trying to control them and move on to the next (better?) experiment ....
|
|
|
But you need to be really careful here. The fact that transaction is signed doesn't mean that it is valid. If you cannot fully trust payind side, you shouldn't receive such transaction offline... People who write rubber checks are not a new phenomena ! There could even be an off-line market in "Junk signedTx", where such things are traded at discount to face value in the off-chance delinquent accounts are eventually made good by people looking to resurrect their financial reputations.
|
|
|
Assassination markets ftw.
lol. ... we will have justice and law, even if it kills us!
|
|
|
Sorry, I thought we were speaking just about browsing regular websites through the .bit domains. In this point of view it is just another dns. And your connection to http server is as vulnerable to middle man as always. I know that lot of other data can be also stored in blockchain.
No sorry, you are still wrong because it can provide for fully-autonomous (i.e. local look-up of regular .bit domains) also. You are correct that data can be stored in the namecoin blockchain, unlike bitcoin. It is not in any way shape or form, "just another DNS" ... but yes it can do regular DNS as one small part of its total functionality. How about that?
|
|
|
From my reading about the issues with ECC now, I'd expect this problem to go away soon - as soon as RedHat legal gets off their asses and say something about it The patent is already shown to not be valid in this case ... and even if for some stupid reason some typically zero intelligence judge did say the patent covers this, well it expires this year anyway from what I've read.
Ok, sounds promising. This tiny little EC copyright issue has been a PITA getting bitcoin projects built cleanly on RH platforms ... way out of proportion to the issue. PS: nice work with the package, btw.
|
|
|
BTW : I wrote a doc on how to build and install electrum from source on Fedora 15 (probably work on other RH-derivatives also). # Set-up dev. env # # use yum-ex and get packages PyQt4 PyQt4-devel # or on command line
$ sudo yum install PyQt4 PyQt4-devel
# separately do same for packages python-setuptools python-pip
$ sudo yum install python-setuptools python-pip
# Install python modules ecdsa slowaes (crypto stuff)
$ sudo easy_install ecdsa $ sudo easy_install slowaes
# Fetch the electrum project from gitorious # $ git clone git://gitorious.org/electrum/electrum.git
$ cd electrum
# build locally QT-icons into electrum/lib/
$ pyrcc4 icons.qrc -o lib/icons_rc.py
# build and install electrum python module
$ sudo python setup.py install
### go home and play :)
$ cd
$ electrum
|
|
|
We need this in several places for Fedora (other RH-derivative) uses ... I can probably contribute.
|
|
|
ThomasV : how extensible is Electrum? I know it is written in python, correct? Is the code quite 'modular'? Background: doing some build testing for Open-Transactions and there is a build that supplies a client API as a python module. If your env is set-up correctly you can simply do a then calls to the "_otapi.so" library of client commands can be made from the python program. Also there is suite of scripts (for financial transactions, contracts, asset issuance, etc) already built on top of the client API that maybe leveraged (and more being built). Thnx.
|
|
|
namecoin is just another DNS system. This is a common misconception also it seems, and wrong in several ways. By running a local Namecoin process you hold a complete database of .bit sites locally (as in right there on your hard-drive) so never have to send DNS traffic out over the internet (where it can be easily monitored by ISP, etc) to look-up the IP addresses of the sites you need/want to get to. In this way XXXX.onion addresses that have ".bit" look-up locally can be found without having to tell the whole world you are browsing to XXX.onion. It is a true decentralised DNS that allows for fully-autonomous domain name look-up, if you set it up right .... and therefore, absolutely not "just another DNS system." No other DNS system comes close to this amount of privacy (for the user) feature.
|
|
|
|