Quote from: soy on November 09, 2013, 11:29:14 PM

Quote from: xyzzy099 on November 09, 2013, 10:34:05 PM

Quote from: soy on November 09, 2013, 10:08:23 PM

The payout went smoothly with the new block. I notice it seems less 'spendable', having 26 confirmations already but needing 94 more blocks, than BTC earned elsewhere. Also the clear demarcation of 'Mined'. I wonder if this will prove a problem with that obscure rule that mined bitcoins make one an international money transfer agent if one tries to use it for anything but barter. Bitcoins mined on another pool have not that demarcation.

But the question I wish to ask, is the minimum payout stat changeable on the configuration page? I have Bitcoin-QT on another machine than the one having the cookie storing the receive address. I generated the signed message which included in the encrypted string a lowering of the minimum payout trigger to 0.1000btc but it didn't take. After the initial payout since the signed message configuration change I expected the payout to be lowered but it was not. Is the minimum not changeable below what is dictated by the value equation used by Eligius staff?

A standard bitcoin transaction is spendable after only one confirmation, and fully confirmed after 6 confirmations. When a new block is mined, the coinbase transaction that gives the 25 BTC + transaction fees requires 120 confirmations before it is spendable.

Most pools send the output of the coinbase transaction to a pool-owned address, then pay you in a separate normal transaction. It will appear in your wallet as 'unconfirmed' until one more block is mined (the confirmation). Eligius (and also P2pool) pay miners directly from the coinbase transaction. That's why the transaction shows up a a 'mined' transaction which shows up as 'immature', and takes 120 confirmations to mature.

You can set you minimum payout to anything >= 0.01 BTC. If it didn't work, it probably means that the signature failed. It should tell you whether if it passed or failed a few lines up toward the top of the page.

Thank you for explaining the difference.

Then if I take the hash generated by the signature, paste it in and decode it I should see the message? And if so then it's something else I'm not doing correctly. For instance, I put a minimum diff of 121 for the Mercury on the address. Then later that day I added two more miners who's diff might more correctly be 7 and 2 but didn't change the requested min diff of 121. Would that prevent all config changes from being accepted?

The diff setting does not actually work, but the payout amount setting does. A lot of people seem to have trouble getting the signed message to be accepted... I don't know what causes that problem.