Topic: Need help for NIST5 - NOMP (Read 103 times)
Yeah, I tried PM to that guy as well reading his post, but he has DM off for Newbiew :-) shy shy !
Roger that, correct no one mined through pool yet. Btw, it's forked from Electra
Ah yes electra did not mine from pool either before it went full POS, if they had a pool i think it was from another guy, so that person probably managed to edit their pool's stratum to have that custom algo 
Roger that, correct no one mined through pool yet. Btw, it's forked from Electra
That's because the algo isn't NIST5.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
Maybe and may not be, it has more than 5000+ blocks already. Mining works file through wallets, it's just the pool that's causing the problem.
Yes that's because all those current blocks were mined from wallet. And mining from the wallet is like mining on the actual algo inside source code, whatever algo it is.
Any coin can be mined from it's original wallet whatever algo it is.
But mining with a pool, it's mining using a stratum. And the stratum requires the algo to be installed in it to properly work.
Nobody mined from a pool yet
That's because the algo isn't NIST5.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
Maybe and may not be, it has more than 5000+ blocks already. Mining works file through wallets, it's just the pool that's causing the problem.
That's because the algo isn't NIST5.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
It's a fork of it, without any name. The original person who made the coin you forked from, made it all wrong.
Coin's Source code: https://github.com/antimonycoin/antimonysource
System: Ubuntu 16.04 Server
Node version: 8.3.0
Mining Algo: NIST5
I am using NOMP + MPOS. Everything works fine, shares are accepted, but at submit block I get following error:
On Googling I found that it has something to do with the Block reward. The coin's block reward is 15, while NOMP block reward has so many zero.
Btw, error on coin daemon is as follows:
On checking the source code, I see that the error is certainly due to additional zeros in block reward:
here's my coin config for Nomp:
System: Ubuntu 16.04 Server
Node version: 8.3.0
Mining Algo: NIST5
I am using NOMP + MPOS. Everything works fine, shares are accepted, but at submit block I get following error:
Code:
0|nomp-server | 2021-04-18 11:54:54 [Pool] [antimony] (Thread 1) Share accepted at diff 37.00292371/40.45611629 by miningexpert9120.mining [::ffff:188.166.161.62]
0|nomp-server | 2021-04-18 11:54:54 [MySQL] [antimony] Share inserted
0|nomp-server | 2021-04-18 11:54:55 [Pool] [antimony] (Thread 1) Submitted Block using submitblock successfully to daemon instance(s)
0|nomp-server | 2021-04-18 11:54:55 [Pool] [antimony] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"7a","ip":"::ffff:188.166.161.62","port":3032,"worker":"miningexpert9120.mining","height":5712,"
blockReward":1500000000,"difficulty":37.00292371,"shareDiff":"107.96353492","blockDiff":3.039774081,"blockDiffActual":3.039774081,
"blockHash":"00000000025f02b08b2449938e15158ee665b98201f491f5bccce9c02a767cb5"}
0|nomp-server | 2021-04-18 11:54:54 [MySQL] [antimony] Share inserted
0|nomp-server | 2021-04-18 11:54:55 [Pool] [antimony] (Thread 1) Submitted Block using submitblock successfully to daemon instance(s)
0|nomp-server | 2021-04-18 11:54:55 [Pool] [antimony] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"7a","ip":"::ffff:188.166.161.62","port":3032,"worker":"miningexpert9120.mining","height":5712,"
blockReward":1500000000,"difficulty":37.00292371,"shareDiff":"107.96353492","blockDiff":3.039774081,"blockDiffActual":3.039774081,
"blockHash":"00000000025f02b08b2449938e15158ee665b98201f491f5bccce9c02a767cb5"}
On Googling I found that it has something to do with the Block reward. The coin's block reward is 15, while NOMP block reward has so many zero.
Btw, error on coin daemon is as follows:
Code:
2021-04-18 11:56:09 ERROR: CheckProofOfWork() : hash doesn't match nBits
2021-04-18 11:56:09 ERROR: CheckBlockHeader() : proof of work failed
2021-04-18 11:56:09 ERROR: CheckBlock() : CheckBlockHeader failed
2021-04-18 11:56:09 ERROR: CheckBlockHeader() : proof of work failed
2021-04-18 11:56:09 ERROR: CheckBlock() : CheckBlockHeader failed
On checking the source code, I see that the error is certainly due to additional zeros in block reward:
Code:
// Check proof of work matches claimed amount
if (hash > bnTarget) {
if (Params().MineBlocksOnDemand())
return false;
else
return error("CheckProofOfWork() : hash doesn't match nBits");
}
if (hash > bnTarget) {
if (Params().MineBlocksOnDemand())
return false;
else
return error("CheckProofOfWork() : hash doesn't match nBits");
}
here's my coin config for Nomp:
Code:
{
"name": "AntiMony",
"symbol": "ANTM",
"algorithm": "nist5"
}
"name": "AntiMony",
"symbol": "ANTM",
"algorithm": "nist5"
}
Jump to: