... NOMP won't change the reward structure without the user making changes to the core. And it sure as hell won't adjust the rewards to a random percentage...
Because I hate it when some asshole tries to call me a liar...
It is NOMP (more specifically node-stratum-pool) that sets the 20%:
https://github.com/zone117x/node-stratum-pool/blob/master/lib/transactions.js#L136With line 136 set to 5 (
as it was originally coded) --- 9/5=1.8:
cad32a4f10a5b2cb931a1949b796efee0adb28334dfc74c2d37bc44f2f5e96ca
1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
7.2 CRW
1JgvdM83xF7FyQMcrYyigtf9uqgbVe14wc
1.8 CRW
With line 136 set to 6 --- 9/6=1.5:
2c2f45f6dd56522b8e719fc5ddff86507bcd17fddf1687f9a3503b1739bd1241
1GoCtfbodeZCrgfj3a1B8h1pDebxp5vgGJ
7.5 CRW
1GUhjtP8QFUVctnFHEyvxCcoE9NJTwx7Rw
1.5 CRW
Next time you want to disparage someone, I suggest you pick someone that can't read enough code to prove you wrong....
Alright so NOMP is using outdated code which affects the reward structure. When structured properly like it is in UNOMP. This isn't possible without some intentional changes, which in turn benefit the miner. A misunderstanding on my part. This is a bug in NOMP. Not UNOMP. My apologies, I got defensive because I've dealt with miners purposely restructuring code for their benefit before. Both of us are in the wrong here but there's no need for namecalling... One thing I was working toward was giving miners FULL rewards during non-enforcement periods. So you will be able to benefit during version upgrades. But once enforcement enables, NOMP will need changes or it will produce invalid blocks it seems.