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

[stevebrush]

Compiling a post poned version of the wallet...

[nanona]

Yes, the block 48001 has been mined by the old chain... irdpool.tk

Soi hard fork has fail... yes, I will postpone it

Well, if a quick fix could be applied the HF could still succeed. The race isn't decided after one block.
But I guess it is better to analyze slowly what happened and go for another HF date/block.

irdpool.tk is the current chain, so people might want to switch there. Certainly until the other pools have switched back to the previous client.

[stevebrush]

Yes, the block 48001 has been mined by the old chain... irdpool.tk

Soi hard fork has fail... yes, I will postpone it

Well, if a quick fix could be applied the HF could still succeed. The race isn't decided after one block.
But I guess it is better to analyze slowly what happened and go for another HF date/block.

irdpool.tk is the current chain, so people might want to switch there. Certainly until the other pools have switched back to the previous client.

Yes, of course, I will analyse this.
I will go for another HF date/block. I start the old daemon on my pool, so it's mining on the old blockchain too and compile working wallets.

[COINTRADINGTIPS]

Looking great. I am looking for windows wallet and exchange listing. On which exchanges you are planning to list and when.

[LsL]

pool alive again, block 48008 , well done guys

[b95123]

So now both wallets, old and new won't work. Is it right?

[stevebrush]

wait please, I'm on it.
I restarted the new blockchain to see if blocks are discovered. the new blocks should be version 2 while olds version 1
if blocks are mined with the new protocol, there are chances...
for the wallets, it's not really a problem,  I will fix this soon.

[nanona]

wait please, I'm on it.
I restarted the new blockchain to see if blocks are discovered. the new blocks should be version 2 while olds version 1
if blocks are mined with the new protocol, there are chances...
for the wallets, it's not really a problem,  I will fix this soon.

It's better to continue on v1. irdpool.tk is already at 48005, while uvac.fr is again stuck with the new daemon.
Even if you manage to fix it, we will then have uvac doing a contentious HF, fighting against irdpool.tk
Some people who switched back to irdpool.tk might have called it a day already and gone to sleep or to work, so that chain will continue no matter what.

[stevebrush]

wait please, I'm on it.
I restarted the new blockchain to see if blocks are discovered. the new blocks should be version 2 while olds version 1
if blocks are mined with the new protocol, there are chances...
for the wallets, it's not really a problem,  I will fix this soon.

It's better to continue on v1. irdpool.tk is already at 48005, while uvac.fr is again stuck with the new daemon.
Even if you manage to fix it, we will then have uvac doing a contentious HF, fighting against irdpool.tk
Some people who switched back to irdpool.tk might have called it a day already and gone to sleep or to work, so that chain will continue no matter what.

You're right, daemon restarted to V1 on uvac.fr

[nanona]

You're right, daemon restarted to V1 on uvac.fr

uvac.fr is orphaning all blocks it found previously before 48000.



Edit: And all blocks are empty since 48002, no tx inside.

[IRD-PoolOperator]

Just intermittently checking the thread and saw this hard fork attempt. It's best to send me PMs, I don't check the thread daily. It sounds like there's been issues, so I'm waiting until I get instructions from the developer on how he wants to proceed.

[stevebrush]

Just intermittently checking the thread and saw this hard fork attempt. It's best to send me PMs, I don't check the thread daily. It sounds like there's been issues, so I'm waiting until I get instructions from the developer on how he wants to proceed.

Nice! I was trying to reach you without success since 1 week...

It was not really an issue, your pool mine the first block after the HF, so it fail because your pool run the non-prepared daemon.
We alert miners, so they switch to my pool but some stay at yours...

I will schedule another HF, so a new daemon will be build for this. I will contact you soon.

[stevebrush]

You're right, daemon restarted to V1 on uvac.fr

uvac.fr is orphaning all blocks it found previously before 48000.
Edit: And all blocks are empty since 48002, no tx inside.

yes, I know. the poll database doesn't like the v2 attempt !
everything should be ok after block 48007 confirmation.
I will see witch block rewards are in the wallet and pay miners by hand :-)
compiling wallets now...

[nanona]

It was not really an issue, your pool mine the first block after the HF, so it fail because your pool run the non-prepared daemon.

That can't possibly be the reason. Upgraded nodes would never validate blocks mined by the old nodes!
So no matter what old nodes do, they would stay on the old chain and not interfere with the new chain.
The problem was rather that the new nodes never forked, i.e. there was never a new chain.
Something went wrong with the upgraded nodes and it has nothing to do with the old nodes.

If one old node could prevent an HF from happening then there would not be any HFs anywhere on any chain  

compiling wallets now...

I know why I didn't delete my VM with the old wallet yet

[stevebrush]

It was not really an issue, your pool mine the first block after the HF, so it fail because your pool run the non-prepared daemon.

That can't possibly be the reason. Upgraded nodes would never validate blocks mined by the old nodes!
So no matter what old nodes do, they would stay on the old chain and not interfere with the new chain.
The problem was rather that the new nodes never forked, i.e. there was never a new chain.
Something went wrong with the upgraded nodes and it has nothing to do with the old nodes.
If one old node could prevent an HF from happening then there would not be any HFs anywhere on any chain  

That's what I through...
and that's whats happen : the seeds nodes never validate the olds block : wrong version, and the wallets and the node of the pool too after restarting it. The pool crashed when the node received the 48001 block.
I will check the logs tomorrow, it's late here now...
finishing compiling and goto bed.

[stevebrush]

Wallets released at the habitual place... just missing the linux version... coming soon
https://github.com/iridiumdev/Iridium-wallet/releases/latest

[aleksa768]

wallet is stuck on the 40001 block and not synchronized

[loatchoat]

wallet is stuck on the 40001 block and not synchronized

I think you should try to delete the Iridium folder in Roaming and re-sync
My wallet GUI is still in sync

[stevebrush]

wallet is stuck on the 40001 block and not synchronized

40001 or 48001?
In that case, download the NO-HF wallet I just release last night

[loatchoat]

Wallets released at the habitual place... just missing the linux version... coming soon
https://github.com/iridiumdev/Iridium-wallet/releases/latest

It seems pretty stable
My coin arrived at my wallet