 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
People have been "Goxed" again! I predict a bottoming out at $50 however Mt Gox will pull the plug at $70 and blame it on a technical glitch this time.
Should you listen to me? Of course not!
CoinMan
|
|
|
|
|
To prevent "penny-flooding" denial-of-service attacks on the network.
|
|
|
|
|
Has the IOS app project been abandoned? I'm jailbroken on IOS 5.1.1 and all I can get the mtgox mobile app to do is launch the splash screen. I can't get it to do anything else to get started scanning qr code, etc.
Thanks,
CoinMan
|
|
|
|
|
LOL...I can't stop laughing at this! Thank God for CosbyCoins!
|
|
|
|
I can not believe you people are still making decisions based on the order book...
+1 (so many losers, so few winners) |
|
|
|
|
I'd give them back. This year sure has seen the quality of this community go right down the shitter..but I digress.
CoinMan
|
|
|
|
I'll be looking at ways to solve [51% attack] going forward, even though I think the current situation will resolve itself soon.
1. Merged mining. 2. Merged mining. 3. Alert user if nethash drops by c. 50%... oops! this happened already. See #1. 4. Merged mining. 5. Tighten timestamp accuracy requirement. Make miners run ntpd. 6. Design a new getwork/pool protocol that gives clients/members control of policy. 7. Alert user if a reorg with many hidden or old blocks occurs. Pardon me if SC already does any of these. All merged mining would do is skyrocket solidcoin difficulty above bitcoin difficulty, except taking a long, long time to do so. An increase of supply of that size will also drop sc price below ixcoin or even i0coin price! I do not support merged mining for any cryptocurrency - it simply doubles the chance of disaster. +1 Merged mining at this point only makes sense with namecoin to me. |
|
|
|
Keep a copy of the current wallet.dat
Yes..of course, that's really all you need wallet.dat everything else can be deleted (bitcoin.conf optional if you even have it). I meant an additional copy, not just keeping .bitcoin/wallet.dat I get it...I should be more clear next time so that you won't have to  I'm starting to think the wallet.dat may be corrupt - hope he has a good backup somewhere before the power went out with the coin in it already  |
|
|
|
|
Ugh. Sorry to hear that. Do you have a prior copy of your wallet.dat backed up somewhere? Perhaps somehow your wallet.dat is now corrupt.
|
|
|
|
Keep a copy of the current wallet.dat
Yes..of course, that's really all you need wallet.dat everything else can be deleted (bitcoin.conf optional if you even have it). |
|
|
|
|
With the bitcoin client closed. Delete all the files except for bitcoin.conf and wallet.dat. Open bitcoin client and let it redownload the blockchain.
CoinMan
|
|
|
|
|
In a rough estimation after viewing some graphs it sure is interesting to note that in the last 5 days BTC has dropped about 20% in value vs USD and that SolidCoin (now 6 days old), is pushing almost 900Gh/s in hashing power and it's price in BTC has been gaining serious ground all week.
I would certainly think that an influx of BTC used to purchase SC could be assisting in the price drop of BTC relative to the USD (and other fiats)...especially if you consider the possibility that the SC might be bought up with BTC that has otherwise been sitting around in wallets doing nothing.
What are your thoughts?
CoinMan
|
|
|
|
|
We need to have a 400 hour block party. I love this pool but this streak of bad luck really sucks. I hope we're on the other side and enjoying GOOD LUCK SOON!!!!
|
|
|
|
Anyone have any ideas on bringing the value of BTC back up?
Buy $40,000 USD worth of Bitcoins - that should do the trick instantly. |
|
|
|
|
Watching this fork....interesting.
|
|
|
|
I continue to have problems connecting to eu or eu2. Never seen this new error message before but it seems to be happening every time it tries to submit a found hash. I can see that stats show no shares going to the servers. I can mine solo and on slushes pool and don't see this problem. Help me Mr. Sam? serv1 19/07/2011 15:54:52, Unexpected error:
Traceback (most recent call last):
File "/home/user/poclbm/HttpTransport.py", line 50, in loop
rv = self.send(result)
File "/home/user/poclbm/Transport.py", line 89, in send
is_block = belowOrEquals(h[:7], self.true_target[:7])
TypeError: 'NoneType' object is not subscriptable |
|
|
|
I just switched the problem GPU's to eu2 and the idle problem went away. CoinMan I've been too busy lately to pay attention to why one of my mining machines with 2 GPU's are showing about 100 MH/s lower hashrate consistently in each of their respective worker accounts. When I checked the machine itself I can see that I am receiving a lot of Warning: job finished, miner is idle. messages on both the GPU's in this machine. I switched these GPU's over to slushes pool and then I don't have this problem. I switch them back to triplemining, the problem reappears. I have a 2nd mining machine with 3 GPU's, they each have their own worker accounts too and while the hashrate does fluctuate these GPU's are not ever getting this idle message. I just upgraded to the most recent poclbm miner to see if that changed anything...it did not. All my GPU's are 5850's and running with the same command line on both of these dedicated machines: .poclbm.py -d X -v -w 128 -f 0 http://username:password@eu.triplemine.com:8344Any guidance is appreciated. I would much rather point my other miners back to this pool. But I can't readily see why the continue to go idle. I did try various adjustments to the -f setting and also added the -a setting with a couple different value adjustments and these changes had no positive effect. Thanks, CoinMan |
|
|
|
I've been too busy lately to pay attention to why one of my mining machines with 2 GPU's are showing about 100 MH/s lower hashrate consistently in each of their respective worker accounts. When I checked the machine itself I can see that I am receiving a lot of Warning: job finished, miner is idle. messages on both the GPU's in this machine. I switched these GPU's over to slushes pool and then I don't have this problem. I switch them back to triplemining, the problem reappears. I have a 2nd mining machine with 3 GPU's, they each have their own worker accounts too and while the hashrate does fluctuate these GPU's are not ever getting this idle message. I just upgraded to the most recent poclbm miner to see if that changed anything...it did not. All my GPU's are 5850's and running with the same command line on both of these dedicated machines: .poclbm.py -d X -v -w 128 -f 0 http://username:password@eu.triplemine.com:8344Any guidance is appreciated. I would much rather point my other miners back to this pool. But I can't readily see why the continue to go idle. I did try various adjustments to the -f setting and also added the -a setting with a couple different value adjustments and these changes had no positive effect. Thanks, CoinMan |
|
|
|
|
