It's a good idea to let the users decide which payment method will be used.
But ... I'd be a lot more happy if the pool becomes more stable and has less downtime. A lot of hashing power is lost due to disconnects, idle miners and complete takedowns :/ Please, work on that - I really like eligius.st

I run the whole bitcoin client in a truecrypt partition of about 1GB size. This is synced to dropbox. I have no concerns about security this way.

Sorry, this command line does not work:
No device specified or device not found, use DEVICE=ID to specify one of the following

But putting the arguments -u to the end works:

Let's see what happens the next few hours. Thanks!

I tried mineco.in right away. But I get a little bit nervous: after about 160 shares my stats are still showing that I didn't submit any shares at all (and still mining @0Mhash/s).

Are the stats so slowly refreshing? After all the page tells me that the hashrate should be calculated over the last 10 minutes.

Oh and Wuked: the contact link on your page points to a thread in a forum that is locked for newbies :/

Unfortunately I can't post to the "mining" forum, "eligius" thread. Maybe someone can forward this message to it?

I am having problems with eligius - every few minutes (really very often!) I get the following messages:

[22/06/2011 00:31:32] Warning: work queue empty, miner is idle
[22/06/2011 00:31:40] Disconnected from server
[22/06/2011 00:32:08] Failed to connect, retrying...
[22/06/2011 00:32:17] Connected to server

I am running on linux, have to graphic cards installed. One is mining with eligius, one with deepbit (just to compare the pools). And I run only into troubles with eligius, no matter which card I use. Phoenix says something like 0.9% stale, while eligius shows me ~4% stales. Probably because of the disconnects.

Is there any parameter I can use to improve my askrate? Right now, I use:


Thanks for your help!

Thanks - I'am wondering how I could miss this information ... but the wiki explains it all.

Hi,

please consider the following example:
* I bought 10 BCs from ten different people. The ten necessary transactions are scattered through the blockchain (I bought some bitcoins years ago, some just days ago).
* Now I spend the ten BCs and send them to a new owner

I am wondering how the ownership of the ten coins are verified by the nodes. Are there lookup tables for each account implemented, so all nodes just know that my account owns 10 BCs. Or do they look for the ten different transactions in the whole blockchain and search the history? (It certainly could be done both ways, but which one is actually used in current implementations?)

Now, what happens, when I received the 10 BCs with 10 different adresses? Does my client know, that it has to create ten transactions with ten different signatures to get the 10 BCs to the new owner? Or can the 10 BCs be combined somehow?

Thanks for your help!