Topic: [ANN] Iridium (IRD) - People are Power - Community build crypto - page 119. (Read 149780 times)
September 20, 2017, 01:32:53 AM
So no update from ird.globalpool.cc ?
September 20, 2017, 01:25:56 AM
Sorry for the delay, irdpool .tk has resumed receiving blocks (up to mine77) after restarting the daemon as per developer instructions. Pool fee dropped to 0% until blocks are being consistently mined.
September 20, 2017, 12:40:05 AM
Why does it take so much time to find a block on the pool?
September 19, 2017, 10:06:08 PM
Dev, with all due respect you seem to be rather disengaged from your project. There have been ongoing problems for more than a day now, yet all we have from you is one post 12 hours ago (and more than 12 hours AFTER the blockchain got stuck) saying that the pool operators need to restart / resync, and the code needs fixing.
I have to agree. What I can share from the mine77 pool server logs is that people are mining blocks, but then the iridiumd daemon is rejecting them. It seems very similar to what is reported here from another CryptoNote coin, as the sequence of messages in my daemon log are the same (too-big-block, then repeated block not accepted due to bad tx).
Code:
DAEMON 2017-Sep-19 19:00:06.899784 INFO [Blockchain] Block is too big: 25507 bytes, exptected no more than 25199 bytes
POOL:: 2017-09-19 19:15:52 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:15:52.326135 INFO [Blockchain] Block has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:18:17 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "valid" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:18:17.977028 INFO [Blockchain] Block <4eb47cab000946155c1d5ccf171c2aa5caaa7db29eecfb3246f5bd187fdd0221> has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:25:37 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
etc.
POOL:: 2017-09-19 19:15:52 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:15:52.326135 INFO [Blockchain] Block
POOL:: 2017-09-19 19:18:17 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "valid" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:18:17.977028 INFO [Blockchain] Block <4eb47cab000946155c1d5ccf171c2aa5caaa7db29eecfb3246f5bd187fdd0221> has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:25:37 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
etc.
Blobsize from transactions exceeding limit.
https://github.com/cryptonotefoundation/cryptonote/blob/master/src/CryptoNoteCore/Blockchain.cpp#L373
September 19, 2017, 06:15:47 PM
I see mine77 pool is mining blocks. Is everything back to normal again?
It would be nice if the dev makes an announcement to explain the situation.
It would be nice if the dev makes an announcement to explain the situation.
things are sort of back to normal. i've received 2 payouts today, but things still don't look quite right.
edit: 4 now. things are cranking at what appear to be pre-disturbance speeds. no idea if it'll stick.
September 19, 2017, 06:05:47 PM
I see mine77 pool is mining blocks. Is everything back to normal again?
It would be nice if the dev makes an announcement to explain the situation.
It would be nice if the dev makes an announcement to explain the situation.
September 19, 2017, 06:01:41 PM
I find it odd and unsettling that mine77 is the only pool to have found any blocks since this has all begun. 77 accounts for less than half the hash power of the network, but no other pools have found any blocks.
Also, the times since last block of the network and of 77 don't match up.
https://imgur.com/CGYQq3D.jpg
Last network block 16 mins ago, but last 77 block 7 mins ago?
Also, the times since last block of the network and of 77 don't match up.
https://imgur.com/CGYQq3D.jpg
Last network block 16 mins ago, but last 77 block 7 mins ago?
September 19, 2017, 04:07:24 PM
Dev, with all due respect you seem to be rather disengaged from your project. There have been ongoing problems for more than a day now, yet all we have from you is one post 12 hours ago (and more than 12 hours AFTER the blockchain got stuck) saying that the pool operators need to restart / resync, and the code needs fixing.
I have to agree. What I can share from the mine77 pool server logs is that people are mining blocks, but then the iridiumd daemon is rejecting them. It seems very similar to what is reported here from another CryptoNote coin, as the sequence of messages in my daemon log are the same (too-big-block, then repeated block not accepted due to bad tx).
Code:
DAEMON 2017-Sep-19 19:00:06.899784 INFO [Blockchain] Block is too big: 25507 bytes, exptected no more than 25199 bytes
POOL:: 2017-09-19 19:15:52 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:15:52.326135 INFO [Blockchain] Block has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:18:17 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "valid" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:18:17.977028 INFO [Blockchain] Block <4eb47cab000946155c1d5ccf171c2aa5caaa7db29eecfb3246f5bd187fdd0221> has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:25:37 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
etc.
POOL:: 2017-09-19 19:15:52 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:15:52.326135 INFO [Blockchain] Block
POOL:: 2017-09-19 19:18:17 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "valid" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:18:17.977028 INFO [Blockchain] Block <4eb47cab000946155c1d5ccf171c2aa5caaa7db29eecfb3246f5bd187fdd0221> has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:25:37 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
etc.
September 19, 2017, 03:32:04 PM
It's stuck again...please dev we all like your project, but we can't mine a few blocks a day...please fix asap..otherwise many will move to other coins!
Agreed.
Dev, with all due respect you seem to be rather disengaged from your project. There have been ongoing problems for more than a day now, yet all we have from you is one post 12 hours ago (and more than 12 hours AFTER the blockchain got stuck) saying that the pool operators need to restart / resync, and the code needs fixing.
You've been fortunate enough to gain a decent amount of miner participation for this project, but it's a minute-by-minute decision for all of us to either mine IRD or one of the many, many other options out there. For example I have 10KH/s pointed at IRD right now that could be earning $25-30 a day on ZEC instead. We're taking a chance on you and your project that ultimately the payoff will be more than we can get elsewhere with established coins that are on exchanges. Your absence when there are serious issues is making that decision questionable at best.
I'd hate to see this project die, but if you don't get involved and at least update us on what's being done to fix the ongoing problems, you'll lose the miners and community rapidly.
September 19, 2017, 03:01:05 PM
It's stuck again...please dev we all like your project, but we can't mine a few blocks a day...please fix asap..otherwise many will move to other coins!
September 19, 2017, 02:42:22 PM
Your site has well managed information about it.It may help you for the long race.Hoping that there will be no race in which IRIDIUM will be defeated.
September 19, 2017, 02:33:55 PM
Nothing is working here back to mining b2bcoin that is also very low supply.
Will return once pool fixed, hoping soon
Will return once pool fixed, hoping soon
September 19, 2017, 01:27:00 PM
I too am getting "Pool Connection Lost" errors on Mine77
ports 7777 and 7788
ports 7777 and 7788
Which miner? I still get them if I use xmr-stak-amd (tried it on 4 different rigs and all available ports) but sgminer-gm-nh works fine on port 7777. Weird as I'd been using xmr-stak-amd for a couple of days with no problems until the pool daemon was restarted earlier today.
I am using stak's miner as well, the Nvidia version.
It was working perfectly before. My errors also began after the daemon's restart on the pool.
Not familiar with the Nvidia version, but I assume you have the same options. Try turning TLS off and using port 8888 or 7777.
I actually tried all available ports. Nothing is working. Stak's CPU miner is also giving me the same error. This is the first time I get this error and I don't know what could be the problem. I switched to mining AEON now and both miners (CPU and GPU) are working fine.
September 19, 2017, 01:14:27 PM
I too am getting "Pool Connection Lost" errors on Mine77
ports 7777 and 7788
ports 7777 and 7788
Which miner? I still get them if I use xmr-stak-amd (tried it on 4 different rigs and all available ports) but sgminer-gm-nh works fine on port 7777. Weird as I'd been using xmr-stak-amd for a couple of days with no problems until the pool daemon was restarted earlier today.
I am using stak's miner as well, the Nvidia version.
It was working perfectly before. My errors also began after the daemon's restart on the pool.
Not familiar with the Nvidia version, but I assume you have the same options. Try turning TLS off and using port 8888 or 7777.
September 19, 2017, 01:06:47 PM
I too am getting "Pool Connection Lost" errors on Mine77
ports 7777 and 7788
ports 7777 and 7788
Which miner? I still get them if I use xmr-stak-amd (tried it on 4 different rigs and all available ports) but sgminer-gm-nh works fine on port 7777. Weird as I'd been using xmr-stak-amd for a couple of days with no problems until the pool daemon was restarted earlier today.
I am using stak's miner as well, the Nvidia version.
It was working perfectly before. My errors also began after the daemon's restart on the pool.
September 19, 2017, 12:13:55 PM
I too am getting "Pool Connection Lost" errors on Mine77
ports 7777 and 7788
ports 7777 and 7788
Which miner? I still get them if I use xmr-stak-amd (tried it on 4 different rigs and all available ports) but sgminer-gm-nh works fine on port 7777. Weird as I'd been using xmr-stak-amd for a couple of days with no problems until the pool daemon was restarted earlier today.
September 19, 2017, 12:06:48 PM
I too am getting "Pool Connection Lost" errors on Mine77
ports 7777 and 7788
ports 7777 and 7788
September 19, 2017, 11:45:06 AM
Everything seems fine on mine77.
September 19, 2017, 11:32:13 AM
Yep. This coin is death.
what happen this coin ?i think Cryptonight is good for new coin ?
September 19, 2017, 11:24:25 AM
Now getting endless "Pool Connection Lost" errors on Mine77, the one pool that was actually working. Anyone else?
ETA: Port 8899.
ETA: Port 8899.
I'm mining same port, no trouble
Don't bother it's stuck again.
Jump to: