Im not sure but personally i think the problem might be with outdated poolscript. If possible try with this newer one that is getting updated, it even officially offers an option for that algo:
https://github.com/UNOMP/node-merged-pool https://github.com/UNOMP/node-merged-pool says :
Notice
This is a module for Node.js that will do nothing on its own. Unless you're a Node.js developer who would like to handle stratum authentication and raw share data then this module will not be of use to you.
Unfortunately, this is not an entire pool software.
Edit: to me it seems like the pool script is not able to properly communicate with the coin daemon so you might want to double check all of the configs.
What makes you think that ?
When I start the pool, it's script tells me the current blockchain height and last block difficulty of Electra. (see 1st picture in OP)
If the pool script is able to retrieve this data, it got it from the daemon so I think they communicate smoothly.
Have you declared any variables specifically for POS/POW ?
Maybe try running the pool again without those config files ? Do you maintain logs in the tail anyway ?
Now this is interesting. I also think there is an issue there, since the coin is in PoW stage and the pool sees it as PoS.
There is no setting anywhere about that. Seems like the pool retrieves the reward type from the coin daemon.
I have removed the magic variables and yeah it doesn't change a thing.
About the algorithm, I know it's supported.
User coolindark runs
http://coinminers.net/ and he offers wywern which is a nist5 coin.
We use the same pool software. He shared his config file and we have the same settings, except for ports and other environment variables.
I think the issue may be coin related. I'm curious as of why is it seen as a POS reward coin.
Here is the output of the coin getinfo :
{
"version" : "v1.0.0.0",
"protocolversion" : 60013,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1950,
"timeoffset" : 0,
"moneysupply" : 1000000026.60937500,
"connections" : 10,
"proxy" : "",
"ip" : "104.131.19.87",
"difficulty" : {
"proof-of-work" : 1.25608541,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1492300332,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"errors" : ""
}
I see both reward type here..
May that be because of a poorly coded coin ? I also know there is one MPOS pool that offers this coin. Maybe uNOMP can't take it ?