Show Posts
|
Pages: [1] 2 »
|
I've leased Methric1 (SHA256 720.00 GH/s) for 1hr and it immediately went off.
|
|
|
rMin2d1mN1sgwe6MNzi2wGkhcJBUA6j23e
|
|
|
I like this question. I like this one even better: what triggered the drop later?
|
|
|
I'm happy you like the idea.
How do we get some traction? I'd love to see this implemented.
|
|
|
Do you know what would be really useful? If every post in Speculation board had the current price added automatically. This way one could easily place people's statements in price context.
If for example someone would post that they expect drop to $1 the forum would add information that the price at the time of posting was $6.
I understand that adding this is change that might not happen for various reasons, but nevertheless - what do you think?
|
|
|
The minimum recommended fee is BTC 0.0005. Below that, all the other nodes might reject your transaction, which is what is happening in your case.
I tried to send with no fee but the send button was grayed out so I couldn't click it... So it's forcing me to set a fee, but I was able to set it to 0.00000001 and send it successfully. I've noticed that too. It doesn't require non-zero value, simply a value. Zero works fine.
|
|
|
How about the "Teetominnie" ? Thought process: 10^-8, Ten2theminusEight, T2-E Teetominnie  Take me to your dealer 
|
|
|
Yea the walls could be bogus but I haven't seen anything like that for a long time.
Well obviously that's because mtgoxlive changed the scale to be the same for BTC/USD sides of the graph. Before, even when BID side was 3 times higher than the ASK side, they displayed the same height. Now it's adjusted to reflect the actual ratio and you don't have to calculate yourself. Yes, now it is much better than before (bid side was plotted in BTC and ask side was plotted USD). Now the asks are also plotted in BTC (the ask axis labels are still in USD). My preferred option would be to see both sides plotted and labeled in USD (with the BTC amounts in the mouseovers). Then one can see how much USD can be cashed in/out to reach a price point, at a glance and without using mouseovers. Well, now that both bid and ask are scaled you have BTC and USD axes scaled properly. That means 1000 BTC equals 11000 USD (or whatever the current rate is). Just take a closer look. You can read left graph from right axis and vice versa.
|
|
|
I too think that using SI is the way to go. 10 nano it is.
|
|
|
Can we get the voice to read one more decimal place (i.e.: 10.13 instead of 10.1)? Or can there be such setting?
Or even better yet, can you make it read as many digits as in 'audio' parameter?
|
|
|
mind linking the thread?
I don't think our minds have evolved enough. Bravo!
|
|
|
Good job! Now 'audio' and 'volume' can be really confusing 
|
|
|
bots are cheating. - humans can't trade WHILE away from the computer.
... I don't think bots can either... You sir made me laugh out loud in public 
|
|
|
Because now he can be sure that exploit will be fixed quick
It would be better to contact Mtgox and let them know you will release that info in short time.
|
|
|
I have released a new Prodnet release with your Spanish, Italian and Polish translations. Thanks a lot!
The other translations could follow next week (if they are ready), after the Bitcoin Conference.
Polish translation looks like it has been run through an automated translator.
|
|
|
My single digit claim has been processed correctly in ~1.5h
|
|
|
Moving and deleting both leave a chance for undeleting. You may want to copy the file to your secure drive and then wipe the original with some secure delete tool that will delete it and then overwrite that location on disk with new bits. This way the file can no longer be undeleted.
|
|
|
The solution is simple and is called transaction fees. If you do not want to wait e.g. 10 times longer for the next block, you will have to increase the fee accordingly to motivate the miners to run their machines again.
Is there a way to estimate wait time for transfering x coins with y fee?
|
|
|
Comments anyone?
Maybe providing a brief description of how users can backup their mobile wallets? Doesn't really need to be secure, I think most are more worried about bugs wiping them atm than having their mobile stolen. Some info about wallet backup is contained in http://code.google.com/p/bitcoin-wallet/source/browse/trunk/READMEI've heard you can use TitaniumBackup to backup app-private data. I'm afraid I can't find the wallet file in data folder, in fact it is empty. Could anyone give me a hint where to look?
|
|
|
I know that by default the wallet.dat is stored in C:\Users\YourUserName\Appdata\Roaming\BitCoin
To secure this wallet, do I remove the wallet.dat (eg. ctrl + x the file) away from C:\Users\YourUserName\Appdata\Roaming\BitCoin and then put it in an encrypted folder on multiple HDs to prevent theft? If I do this then do I copy the wallet.dat back into the default folder to add BTC to the wallet, then remove the wallet again and encrypt the updated version?
So basically if I open the Bitcoin app, since there is no wallet.dat will it just show up as having 0 BTC unless I manually copy the wallet.dat back over to the default directory?
You may want to consider secure wiping the file instead of just deleting it. Also you don't need to open your wallet if you send coins to it, they will reach it even if it is stashed away in a safe box.
|
|
|
|