Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 42. (Read 903150 times)

The following will be posted on the Eligius, BTCGuild and P2pool threads.

How willing are the pool operators to implement this? Is it hard? Any downsides? Please discuss

My position is that every periodic payment should be done using deterministic key pair generation.  Of course this includes all mining payouts.  The way this would work is that instead of generating a normal private/public key pair and giving the Bitcoin address of the public key to your mining pool for payout you would generate an extended private/public key pair and give the extended public key to the mining pool.

An extended public key contains within it the first public key and information on how to generate an entire sequence of public keys that correspond to the same key pair sequence that is generated by the extended private key.  So the mining pool would send your first payment to the first public key, your second payment to your second public key, your third payment to your third public key, etc.

Meanwhile your client can generate the first private key that corresponds to the first public key, the second private key that corresponds to the second public key, etc. so you can claim/spend the BTC when you are ready.

This way every single periodic payment can be sent to a unique public address.  Cool, right?

However, I do not know of a single pool that supports this payment mechanism.  I do not keep up with all the various mining pools having given up mining at the end of the GPU mining era myself.  So, if there is a pool that supports this please let me know.

All miners should demand this from every pool they use and only use pools that support this mechanism.

It is looking more like you would not have to even worry about that as they do not intend to encompass mining pools and services.

There was a very brief interruption of service for about 20% of miners.  One backend lost its bitcoind connection to the other backends (used to virtually eliminate the chance of two pool servers orphaning each other's blocks) and a restart was triggered.  Everything is working normally again, and it should have only impacted about 1 in 5 connections.  If it did affect you, it likely only lasted a few seconds (long enough to reconnect and have the load balancer put you on a different node).

So if you can't say for sure, then how would you enforce a new TOS ?

It will require an affirmitive "I am not a resident of the state of New York" and "I do not run any of my equipment from within the state of New York" before allowing you to register a new account, and existing accounts will have to affirm that within a certain time frame or else the account will be frozen.

I will also be adding IP-range lockouts for known New York IP addresses which will give a splash page stating that New York residents are forbidden from using the pool.

So if you can't say for sure, then how would you enforce a new TOS ?

I'm guessing very, very little.

Saw latest news item, just how much of the current guild hash is in New York would you say ?