Can you give me a link to the provider that guarantees 100% uptime for only 40$ per month?

There is a package for memcached:

thx

I can't make payouts. Hot wallet low again?

Yes, it works now. Thank you.

I cant request any BTC or Namecoin payouts anymore. I get the message:

A payout request is already being processed for your account (you may have clicked the link twice).

I waited a few blocks and still the same. Also the Unpaid Rewards counter did not jump back to zero, after i clicked request payout. Can you take a look at this, please. My username is br0ken

This happend to me too once. Now I'm running vpn on router and I enabled Wake-On-LAN on rigs, so I'm prepared next time.

yaaay!

I sent you a pm with my btc address.

8

you should speed up your fans to above 4000RPM so your cards cool of to <80°C. Your cards will live a lot longer with lower temperatures.
try:

note that when you compare hashrates, with "--auto-gpu" cgminer takes a few minutes after restart untill gpus run at full load. It slowly increases clocks in the beginning.

I gave it another hour, but it didn't recover. I copied the blockchain files from another machine and now it works.

Isn't 1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4 forrestv's author donation address, which always gets 0,5% of 50BTC for each block. Some people disabled donation so its a bit less, but pretty stable.

I'm using linux and I'm pretty sure I'm running the correct binary as you can see in my earlier post:


You are correct, it is best to use a empty wallet on that machine and that is what I do.
I tried to delete everything except the blockchain, but still the same problem.
I also tried to run 0.5.2, but its stuck at 170059, too.

broken@rig02:~/bitcoin/bitcoin-0.5.2-linux/bin/64$ ./bitcoind getinfo
{
    "version" : 50200,
    "balance" : 0.00000000,
    "blocks" : 170059,
    "connections" : 8,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 1496978.59502557,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1331211591,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : "WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade."
}

I think 0.6.0rc1 broke my blk0001.dat,  blkindex.dat or something else not located in .bitcoin/ (is there something else?)
When I get home I will also delete these files. (I have a 170190+ blockchain here that I will try first, before downloading the whole thing again)

I'm pretty sure I'm running bitcoin 0.6.0rc2. But i guess rc1 broke my bitcoin db somehow.
Im currently testing on another machine, where I switched directly from 0.5.2 to 0.6.0rc2 at block 167000. But still have to download 1000 blocks. If this works ill just copy the database to the other machine.

edit:

Does p2pool still work with 0.5.2 or is 0.6.0rc2 absolutely necessary?
I knew I shouldn't have upgraded to a unstable version on a productive system.

I upgraded from rc1 to rc2 and bitcoin is still stuck at 170059.

It cant manage to upgrade to bitcoin-0.6.0-rc2. It always seems it still starts rc1.

# The files are apperently different

broken@rig02:~/bitcoin$ ls -la bitcoin-0.6.0rc1-linux/bin/64/ | grep bitcoin
-rwxr-xr-x 1 broken broken 4247696 2012-02-07 19:46 bitcoind
-rwxr-xr-x 1 broken broken 8891013 2012-02-07 19:46 bitcoin-qt

broken@rig02:~/bitcoin$ ls -la bitcoin-0.6.0rc2-linux/bin/64/ | grep bitcoin
-rwxr-xr-x 1 broken broken 4251824 2012-02-29 21:59 bitcoind
-rwxr-xr-x 1 broken broken 9053450 2012-02-29 21:59 bitcoin-qt

# Bitcoin is stopped
broken@rig02:~/bitcoin$ ps -ef | grep coin
broken     2165     1  0 Feb14 ?        02:40:52 ./namecoind -daemon

# Starting bitcoin
broken@rig02:~/bitcoin$ cd bitcoin-0.6.0rc2-linux/bin/64/
broken@rig02:~/bitcoin/bitcoin-0.6.0rc2-linux/bin/64$ ./bitcoind -daemon
bitcoin server starting
************************
EXCEPTION: 11DbException      
Db::put: Cannot allocate memory      
bitcoin in ProcessMessage()

# Bitcoin is now running
broken@rig02:~/bitcoin$ ps -ef | grep coin
broken     2165     1  0 Feb14 ?        02:40:53 ./namecoind -daemon
broken    15663     1 10 09:45 ?        00:00:12 ./bitcoind -daemon

# Its the correct binary
broken@rig02:~/bitcoin$ readlink -f /proc/15663/exe
/home/broken/bitcoin/bitcoin-0.6.0rc2-linux/bin/64/bitcoind

# Bitcoin gives error and is stuck at 170059
broken@rig02:~/bitcoin/bitcoin-0.6.0rc2-linux/bin/64$ ./bitcoind getinfo
{
    "version" : 60000,
    "protocolversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 170059,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 1496978.59502557,
    "testnet" : false,
    "keypoololdest" : 1322670639,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "errors" : "WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade."
}

Anyone have a idea how to upgrade?

use it like this:

wget -O- http://192.168.1.235:9327/patron_sendmany/200.00 | more

Thank you very much, DeathAndTaxes edit: and kjj.
I understand it now and set my miners to /1000

Lets assume a diff=650 is worth something like ~0.002 BTC

Person A has default settings (diff~650) and starts hashing.
Person A finds 10 shares with diff > 650 (eg. 9x ~650 and one share ~13000) in 24h
There is one block found just now.
Person A get a payout of 0.02 BTC.

Person B sets diffuculty to 6500 and has same hasrate as person A
Person B found 1 shares > 6500 (eg. ~13000 ) in 24h
Person B gets a payout of ~0.02BTC

Person C is cheating and starts hashing.
Person C finds a share with difficulty 13000.
Person C connects and sets difficulty to 13000 and submits share.
Person C starts hashing with a new address.
Person C finds a share with difficulty 650.
Person C connects and sets difficulty to 650 and submits share.
Person C starts hashing with a new address.
Person C finds 8 more diff 650 shares in the same way.
Person C gets payed out to 10 different addresses 9x ~0.002 BTC and 1x ~0.04 BTC.

Only solution that comes to my mind is, that a user (identified by address) needs a history of maybe 12h before he can change his difficulty.

Can someone explain, how the new "miners can volunteer to raise their share difficulty"-protocol change works? I don't understand how cheating is prevented.

Can't you just mine in secret and for example find a difficulty 1000 share, and then connect to the p2pool network and send: "hey, my address is 1abcsomething and I'm mining difficulty 1000 and here is a share"? And then afterwards mine in secret a difficulty 650 share and connect to the p2pool network and send: "My address is 1xyzsomethingdifferent and I'm mining difficulty 650 and here is a share"?

How can you define a difficulty in advance, if you can simply reconnect with a new identity?

I'm sure I'm missing something here. Please enlighten me