-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
51% prevention #315
Comments
I think this is a bad idea. It will do nothing if a pool has nefarious
|
I agree, not a good idea. |
make it optional, i know it doesnt solve the problem of nefarious pools, it would solve the problem of damaging a coins image by a non-nefarious pool hitting >51% too often. to solve the problem of nefarious pools we need this implemented in miner software aswell |
not adding. stratum is a server software. it should have 0 responsability with a 51% of hashrates. it is up to the OP to disable registrations on the frontend. |
going over 51% can happen quickly with low block time coins and disabling registration does not do much quick enough. I dont see why not have this option. |
Not sure why going over 51% is even an issue. 51% attack? Then it's a On Mon, Mar 17, 2014 at 8:42 AM, gaby64 notifications@github.com wrote:
|
the issue is with the fear of 51%, pool operators go posting on coin threads saying to switch, no action is taken. it would be great to have an automatic option. |
The automatic option is p2pool. On Mon, Mar 17, 2014 at 10:35 AM, gaby64 notifications@github.com wrote:
|
im not talking about an option for miners, this is an option for pool operators we all wish miners would work in the interest of the coin they mine, but thats not actually the case, multipools and miners looking for quick profit dont pay attention to pool network hashrate percentage. |
im sorry but this is a feature i refuse to add. a bad pool op will disable it anyway. and secondly it would cause constant disconnects for users so they wouldnt be happy |
we need something that can temporarily disconnect workers to reach a target maximum hashrate on every difficulty adjustment.
pseudo code
target = 0.35
poolnethashperc = poolhashrate / networkhashrate
if poolnethashperc > target
{
if poolnethashperc > 0.50
{
while poolnethashperc > target
{
randnum = rand
disconnect(worker[randnum])
disable(worker[randnum], 10) //minutes
poolnethashperc = poolhashrate / networkhashrate
}
}
else
{
newpoolnethashperc = poolnethashperc * 0.9
while poolnethashperc > newpoolnethashperc && poolnethashperc > target
{
randnum = rand
disconnect(worker[randnum])
disable(worker[randnum], 5) //minutes
poolnethashperc = poolhashrate / networkhashrate
}
}
}
The text was updated successfully, but these errors were encountered: