[ANN] Iridium (IRD) - People are Power - Community build crypto

[nanona]

http://irdpool.tk/ stopped working

Yes, it found the block 69500 and then apparently disconnected all workers:

Hash Rate: 0.00 H/sec
Connected Miners: 0

All subsequent blocks (69501-69503) have been found by irdpool.fr

So the network could be a bit slow now since irdpool.tk had around 150kH/s and those are missing now. Unless they had backup pools for automatic switching configured. But I don't see that hashrate appear in any of the other pools yet.

[b95123]

Was the HF successful?

69500 mined by IRDpool.tk

Everything looks fine.

Wallet works. Block size increased. Difficulty adjusts quicker.

[stevebrush]

http://irdpool.tk/ stopped working

Yes, it found the block 69500 and then apparently disconnected all workers:

Hash Rate: 0.00 H/sec
Connected Miners: 0

All subsequent blocks (69501-69503) have been found by irdpool.fr

So the network could be a bit slow now since irdpool.tk had around 150kH/s and those are missing now. Unless they had backup pools for automatic switching configured. But I don't see that hashrate appear in any of the other pools yet.

Yes, HF ok : blocks >= 69501 are version 2, so zawy diff start now ! the diff will adapt faster now

[stevebrush]

http://ird.cashpool.us is ok too

[nanona]

irdpool.de also seems down:

Hash Rate: 0.00 H/sec
Connected Miners: 0

But not sure if this is the same "bug" (?) as with irdpool.tk or if the couple of workers disconnected intentionally.
I think this pool had only a couple of workers before and <1kH/s total hashrate, but I am not sure.

That said, I like it when pools have those diagrams enabled showing among other things the development of the pool's hashrate in the past 24h at least.

irdpool.ru showing additionally an overview of the other pools with some of their stats is of course the icing on the cake (or rather the ice cube on the vodka).

[schyter]

some pools are down

[stevebrush]

###################################################################
Hard Fork is a Success !

Since block 69501, Iridium blockchain run at version 2 with the new difficulty algorithm

Here is at this time the status pool :

https://irdpool.fr : ok
http://ird.cashpool.us : ok
https://irdpool.eu : re-up since 3 minutes
http://irdpool.ru : don't know but looks ok
https://irdpool.de : down for a few days
http://irdpool.tk : down

###################################################################

[ingnz]

some pools are down

After some minutes with problems after the HF https://irdpool.eu is up again!

[stevebrush]

I can now see "big" blocks and some old stucked transactions to be accepted...

[stevebrush]

...
So the network could be a bit slow now since irdpool.tk had around 150kH/s and those are missing now. Unless they had backup pools for automatic switching configured. But I don't see that hashrate appear in any of the other pools yet.
...

Zawy's algo do it well ! it takes only 5 blocks to handle this hashrate hole !!!
And the transaction pool is flushing slowly : stucked transaction are released 

[IRD-PoolOperator]

I'm investigating the issue, something has changed. I'm assuming there's a secret fix the developer has decided not to inform me about again.

[stevebrush]

I'm investigating the issue, something has changed. I'm assuming there's a secret fix the developer has decided not to inform me about again.

No, no secrets.

[mrWatson]

Guys please be peaceful. This is the democracy project. We all should achieve success with this coin.
Seems Steve is not interested in irdpool tk issues. More pools - more power.

[stevebrush]

5 stucked transactions left in mempool... it's on the good way.

[IRD-PoolOperator]

Guys please be peaceful. This is the democracy project. We all should achieve success with this coin.
Seems Steve is not interested in irdpool tk issues. More pools - more power.

Steve is not interested in approximately half the hashrate of the network? Sure that hashrate can go elsewhere. The idea that the developer doesn't seem to care about breaking major chunks of the ecosystem is concerning.

I've re-implemented the pool several times now, with several different forks (including the exact forks other running pools use), with several different forks of the back-end used by the pool forks.

All error messages, and research into them indicate a problem with a hardfork. I will continue my search for the secret fix the developer is withholding (probably located within node-cryptonote-util) for a bit more.

I can attempt to re-implement with entirely new pool software (not the same pool software all current IRD pools run) but this would involve migrating to a completely new DB schema.

I said earlier in this thread when mine77 was shutting down I would continue to run irdpool.tk on the condition it wasn't a major time sink. It now is. I have a actual development work I need to be doing, not reverse engineering someone else's patches.

[stevebrush]

Guys please be peaceful. This is the democracy project. We all should achieve success with this coin.
Seems Steve is not interested in irdpool tk issues. More pools - more power.

Steve is not interested in approximately half the hashrate of the network? Sure that hashrate can go elsewhere. The idea that the developer doesn't seem to care about breaking major chunks of the ecosystem is concerning.

I've re-implemented the pool several times now, with several different forks (including the exact forks other running pools use), with several different forks of the back-end used by the pool forks.

All error messages, and research into them indicate a problem with a hardfork. I will continue my search for the secret fix the developer is withholding (probably located within node-cryptonote-util) for a bit more.

I can attempt to re-implement with entirely new pool software (not the same pool software all current IRD pools run) but this would involve migrating to a completely new DB schema.

I said earlier in this thread when mine77 was shutting down I would continue to run irdpool.tk on the condition it wasn't a major time sink. It now is. I have a actual development work I need to be doing, not reverse engineering someone else's patches.

I assume there is no secret patch.

[nanona]

I will continue my search for the secret fix the developer is withholding

Since IRD pools are popping out of the woods left and right these days, I am wondering how all those new operators are able to do so without "the secret fix the developer is withholding" /s

[stevebrush]

Please, load balance your hashrate between the running pools : Choose the closest to you. you won't earn more or less by mining on a pool with not so much people, just your payments will take a little more time : the time for finding blocs and maturate.

actual status of pools :

irdpool.fr : France ( up and running )
irdpool.eu : France too ! ( up and running )
ird.cashpool.us : US ( up and running )

irdpool.ru : RU (edit : don't know if it's ok as a very low miners are there looks ok, it's written on it )

irdpool.de : DE ( out )
irdpool.tk : CA ( out, still I like MTL )

[IRD-PoolOperator]

Guys please be peaceful. This is the democracy project. We all should achieve success with this coin.
Seems Steve is not interested in irdpool tk issues. More pools - more power.

Steve is not interested in approximately half the hashrate of the network? Sure that hashrate can go elsewhere. The idea that the developer doesn't seem to care about breaking major chunks of the ecosystem is concerning.

I've re-implemented the pool several times now, with several different forks (including the exact forks other running pools use), with several different forks of the back-end used by the pool forks.

All error messages, and research into them indicate a problem with a hardfork. I will continue my search for the secret fix the developer is withholding (probably located within node-cryptonote-util) for a bit more.

I can attempt to re-implement with entirely new pool software (not the same pool software all current IRD pools run) but this would involve migrating to a completely new DB schema.

I said earlier in this thread when mine77 was shutting down I would continue to run irdpool.tk on the condition it wasn't a major time sink. It now is. I have a actual development work I need to be doing, not reverse engineering someone else's patches.

I assume there is no secret patch.

I found the secret patch, and to quote the developer of the pool you feature in your signature: https://github.com/zone117x/node-cryptonote-pool/issues/14

I'm closing this issue and removing stated support for Fantomcoin. This project has no future plans to actively support any coins that don't work by default because the clone coin devs make changes which break the pool software yet make no effort to patch the pool to work with their changes.

For this pool to add support for modified cryptonote coins then the devs/communities behind those coins will have to fund a bounty to make it worth while for devs of this project.

The solution was to switch to a pool fork that explicitly supports Fantomcoin, by default the fork irdpool.fr and irdpool.eu run does not work with this HF and the developer has stated he will not support it. There is your secret patch.

Let it be no secret, Stevebush for whatever reason seems to hate me and seems to be actively attempting to fuck with irdpool.tk. It's getting the point where I feel I need to audit any code that gets pushed out.

[stevebrush]

I found the secret patch, and to quote the developer of the pool you feature in your signature: https://github.com/zone117x/node-cryptonote-pool/issues/14
The solution was to switch to a pool fork that explicitly supports Fantomcoin, by default the fork irdpool.fr and irdpool.eu run does not work with this HF and the developer has stated he will not support it. There is your secret patch.
Let it be no secret, Stevebush for whatever reason seems to hate me and seems to be actively attempting to fuck with irdpool.tk. It's getting the point where I feel I need to audit any code that gets pushed out.

Damned ! I'm trapped !   (Are you sure?) I repeat, there is no patch, no hidden secret, just work. I tested the HF, like others and fix the smalls issues without copy/paste, this is why it's written modded by steevebrush in the pool signature. The first time I try the hard fork 2 month ago, my pool crashed. I did not want it to start again. that's all.
By the way, I did not hate you : Hard fork is a success, stucked transactions are deblocked : not to bad for some git pull and copy/paste. 
Good luck.