|
Sold another DiRT3 code, but I think I have another one to dig out. If anyone wants it, let me know and I'll make sure I have it before asking for BTC.
|
|
|
|
|
I would jump on this if I didn't already have it... if nothing else, both Braid and World of Goo are GREAT games and well worth it!
|
|
|
|
your selling these too cheap! :-P
Feel free to offer more then.  |
|
|
|
|
I had a fairly large "Unpaid Reward" (2-3 BTC) on Ti/3 and I'm still waiting for it to be generated. An ETA would be nice to put my mind at ease.
|
|
|
|
I'm calling it now. People using this method incorrectly are going to cause the bitcoin economy to lose another 1-2% of its coins. I can't wait for the lawsuit threads.
It should be yet another method, not the only method. I have copies of my wallets backed up and encrypted in three local locations and also on a webserver in another continent. Here's something else to add "just in case." Not that I have too many bitcoins, really, but better be safe NOW rather than learn the hard way later. |
|
|
|
Very nifty, jrwr! I tried it with a compressed, encrypted wallet.dat and even with six times redundancy it fit on one page of letter and scanned back nicely. Much fun.  As far as program/data obsolescence is concerned, it wouldn't be a problem because there should be plenty of time to switch to something else if/when the program will no longer work. I hear of people/companies who are stuck with lots of data on inaccessible floppies. Why didn't they backup/copy the data from the floppies when they were on their way out in the first place?!  |
|
|
|
|
I take it UK is out permanently then?
|
|
|
|
|
Make sure you've enabled UnofficialOverclocking.
Yes, the answer is to SKIP the 500MHz range.
|
|
|
|
The bitcoin will be back to around 17.5$/BTC after we rollback all trades that have happened after the huge Bitcoin sale that happened on June 20th near 3:00am (JST).
Service should be back by June 20th 10:00am (JST, 01:00am GMT) with all the trades reversed and accounts available.
One account with a lot of coins was compromised and whoever stole it (using a HK based IP to login) first sold all the coins in there, to buy those again just after, and then tried to withdraw the coins. The $1000/day withdraw limit was active for this account and the hacker could only get out with $1000 worth of coins.
Apart from this no account was compromised, and nothing was lost. Due to the large impact this had on the Bitcoin market, we will rollback every trade which happened since the big sale, and ensure this account is secure before opening access again. https://support.mtgox.com/entries/20208066-huge-bitcoin-sell-off-due-to-a-compromised-account-rollback |
|
|
|
your limited to withdrawing $1,000 worth of bitcoins a day
I've had success withdrawal more than that as long as I do multiple withdrawal requests. Each one spit back at my "limit reached" but I was able to do several successive withdrawals with no problems. |
|
|
|
There is no load balancing. btcguild.com => US central server, AFAIK.
Exactly. In fact, for several days there was a message on the main BTC Guild page saying NOT to use btcguild.com as US Central was overloaded. |
|
|
|
I lost several hours of mining because your servers went down  Regardless of which pool you are in, you should always set up backup miners. I love that BTC Guild has multiple servers because then my backups can be on BTC Guild itself! In my case, I had each card hashing on UK and NL, so when UK went down, they automatically switched full-speed to NL. Also, if one server has idle issues, the other worker picks up the slack. This is quite easy to do. You simply start two workers per device. You can prioritize them if you wish with poclbm/-f or Phoenix/AGGRESSION. I have mine running on Phoenix with equal aggressions, so it splits 50/50. On the other hand, the frames trick for poclbm will allow you to give one pool 99%+ of your hashes and another pool < 1%. If Pool A goes down, Pool B gets 100%. Even the biggest pool has had connection errors, DDoS, and other problems, so the responsibility is on you to prepare things wisely on your end so that everything is smooth and automated. And the pool operators will do everything they can as well, of course. For me, especially since I didn't have any real downtime, our recent luck more than makes up for any complaints: Luck in past 24 hours 724013 shares (+21.2%)  |
|
|
|
|
Page 83, I have the actual magazine right in front of me. Arrived in today's mail.
|
|
|
|
|
I don't know if this has much (anything) to do with it, but you do know that AGGRESSION is for Phoenix not poclbm?
|
|
|
|
EDIT: Turns out that stats weren't updating correctly prior, so I did not notice from the stats that my miner was actually NOT submitting shares. Idles had caused Phoenix 1.48 to mine at 0MH/s yet again [I blame this on phoenix more than idles]. So, stats are working fine after reset, but phoenix sucks eggs. If it wasn't for phatk, I would dump it completely.
You might try 1.50 -- it was supposed to fix/reduce this issue. |
|
|
|
|
As long as you don't mind waiting a while for the transaction, it shouldn't be a problem.
Ele, any chance of having luck and/or personal 24-hour generation in the API?
|
|
|
|
|
Show Posts
