Your comments
The problem with Monero Block 1589929 was a combination with a never before seen sync issue of the daemon and a bug in the pool's block unlocker code. Sorry that it took so long to figure it out.
Looking into it.
Thanks for reporting the problem.
Could you try again?
I'm closely monitoring the BTCP pool. I've alreay checked for any potential software/infrastructure issues but there were none.
Checking.
No worries.
Customer support service by UserEcho
The problem with Monero Block 1589929 was a combination with a never before seen sync issue of the daemon and a bug in the pool's block unlocker code. Sorry that it took so long to figure it out.