But if I have to run bitcoin daemon, this would mean that I would be headed to an online wallet? BlockExplorer and Blockchain.info are nowhere near reliable enough to use as a blockchain database tool for use for ecommerce. If you don't want to run bitcoind, then perhaps: - Bit-Pay -- https://bit-pay.com/ - Mt. Gox Pay Now -- http://bitcointalk.org/index.php?topic=85520.0 - Paysius - or the other hosted merchant methods?
|
|
|
Right now I have 20gh of personal mining rigs and singles. I have more 10 singles ordered, most should be here when they ship out the next batch. I will only sell bonds that can be covered by what I'm currently running. All bonds will go towards singles until something better comes out.
Can the equipment be commercially insured against theft (& fire)?
|
|
|
And to recommend how anyone, particularly someone running Windows, with more than pocket change worth of funds on their exchange should be using two factor authentication. How do you go about two factor authentication, when using a local wallet / BTC client? Personally I use an encrypted wallet, and run a client inside a VM which is on an encrypted truecrypt container which I only mount to run bitcoin. Still, everything occurs at my computer locally. Do you have something else in mind when you advocate two factor authentication? Well, that comment was describing how two factor authentication (which Mt. Gox offered first with Yubikey, and as of a few hours ago now supports Google Authenticator as well) is needed for using Mt. Gox, especially on Windows, but really all platforms, to be protected from these password-only thefts. For a local wallet / BTC client there's no concept of two factor, and thus there needs to be a level of security appropriate for the risk. For larger amounts, there's a secure method -- an air gapped system used for transacting. When M of N transactions are implemented, that will help to lessen the risk of theft as well. For now, what you have is probably much more secure than what most do, but it still is vulnerable if your host is compromised, say from a 0-day. Or let's say some thieving software engineer at ATI slipped in a wallet stealer into their GPU driver binaries. We'ld probably never know until after the wallets are gone. (Your VM image probably wouldn't run the ATI binary driver so you'ld probably be safe from that specific vulnerability.)
|
|
|
Found it, thank you so much. I love the command line, I forgot about that find command. Worked like a charm.
In case anyone else has this issue, ... do you remember which directory it was in?
|
|
|
P.S. my PC is very secure.
Which version of Windows are you running? I assume you mean: which version of Linux? He said it's very secure, so obviously he's not running Mac OS X or Windows. No I meant Windows. I'm guessing it was Windows, and wanted a good opportunity to explain how one running Windows cannot make the statement "my PC is very secure". And to recommend how anyone, particularly someone running Windows, with more than pocket change worth of funds on their exchange should be using two factor authentication.
|
|
|
Will this be in the bunker?
|
|
|
In another thread where there was a Mt. Gox account that got compromised, TT had just made some suggestions: Withdrawal to bitcoin address is the exchange function/API call that is most prone to theft. Other withdrawal methods have at least some level of traceability and/or reversibility.
Therefore, I propose the following solution: 1) create a completely separate right for both the web and the API for withdrawal to bitcoin address, separate from all the other withdrawal methods. 2) allow the owner of the account to have a whitelist of bitcoin addresses to which it is allowed to withdraw from both the web AND the API. 3) require two-factor authentication for adding or removing addresses to and from the whitelist. [Update: Mt. Gox just added this.]
This simple feature means that even in the event of an attacker gaining access to the user's web dashboard or the user's API keys, the attacker will not be able to withdraw bitcoins to addresses of his choice.
Simple fix to a significant security risk.
And in yet another thread where there was a GLBSE account that got compromised, TT made his appeal to them as well: Please, exchanges, implement this SOON. You cannot implement it soon enough.
|
|
|
P.S. my PC is very secure.
Which version of Windows are you running?
|
|
|
I'm having trouble logging into glbse. I have reset my password and created a new one but the site says that my username/password is still incorrect.
Ya, it is awkward. After you get the reset, your first attempt to login will be rejected even with the new password. Then you get a second try where you need to enter the Captcha. Should let you in then. If not, try the reset again and repeat the above.
|
|
|
So now I am the proud owner of penny stock with a huge investment of about 0.2 btc LOL,
Isn't that an incredibly liberating concept? You didn't pay $8 or $32 per trade, ... you bought a single "share" with a market price of 0.2 BTC and paid about 0.2 BTC to acquire it. Disintermediate Wall Street!
|
|
|
Step one, make sure you have a backup of wallet.dat. Step two [to use a binary of the blockchain from elsewhere], in the ~/.bitcoin there should only be three files. your wallet.dat and the two Blk*.dat Also, make sure you are using the most recent release of the client.
|
|
|
My question is that aren't we all overpaying for shares and bonds on GLBSE? Paying 100% PPS makes no sense because the investors take all the risk, while owners lock in capital. Your answer may be "whatever the market will bear" and my reply would be the market is dumb.
Idle bitcoins seem to be burning a hole in people's wallets. So there's an oversupply of bitcoins that people want to "put to work", and a shortage of "investment" opportunities. Just too many bitcoins chasing too few opportunities. I had seen the string of IPOs and figured there would be lots of rotation into the "IPO"s, and the older issues would suffer. Hasn't really happened. What is wild to remember is that an issue that stays at the same value but the exchange rate goes up 5%, means that the issue essentially went up 5% (relative to the dollar) as well.
|
|
|
- http://www.riderbee.comInteresting, they justify their fees (10% to the rider, 20% "commission" to the driver) due to payment processing fees and PayPal fees (because everyone knows how big of a pain in the ass those PayPal fees can be!) - http://www.riderbee.com/faqSo for a $10 trip. Rider pays $11 ($10 + 10% fee) Driver gets $8 ($10 less 20% commission) RiderBee gets $3 (30%) of the amount. PayPal fees ... For the $11 paid by the rider, $0.30 + 2.9% so $0.62 For the $8 paid to the driver, (probably using mass payments, 2%) = $0.16 So the PayPal fees for a $10 trip are $0.78, or 7.8% cost. RiderBee is paying maybe 8% (roughly ... +/- a couple %) to PayPal because Bitcoin is not yet widely used.
|
|
|
Less than a year ago: So why didn't we encrypt it up the wazoo and require that you type six passwords to unlock it? Well, two major reasons:
First, losing your wallet or forgetting your password is (arguably) as big a threat as theft. There is a reason every online service has some 'recover/reset lost password' feature.
- http://gavinthink.blogspot.com/2011/06/why-arent-bitcoin-wallets-encrypted.html
|
|
|
|