You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created a coin with FORKNOTE and installed the forknote-pool which is running perfectly except for one small issue... All of the payments generated to miners have a 0.00 value.
I have checked the miners wallet and the transaction are going into the wallet just fine. As well as the transactions being logged on the miner and admin pages.
Why is forknote-pool not paying out as expected?
I have the following payment configuration in the pool config.json file;
My forknote coin uses this configuration;
Any insight as to why the pool is generating 0.00 value payments would help!
I'd like to request that this issue be reopened... I set the pre-mine to be 10% of the total coin supply.
If I take the two, MONEY SUPPY and GENESIS_BLOCK_REWARD values from my coin.conf file and put them one on top of the other you can see that the Genesis Block (pre-mine) is only 10% of the Money Supply.
`
I used the Create CryptoNote page on the forknote website to build my config. http://forknote.net/create
I can also view the wallet that I had the pre-mine coins go into and it reflects to proper ~179 million coins. Just to double check I ran through the whole coin creation process again using this settings;
And again, the pool is generating 0.00 transactions out to the miners. Even though I can see the miners should be receiving much more.
Is there something I need to change in the pool, since my coin decimal point is 10 instead of the default 12? Outside of the setting for coinUnits?
I misread. Sorry. coinUnits indeed is the property controlling the decimal point. You probably have something misconfigured in the pool config, because this is definitely not the result you should see
I was able to resolve this issue by going back through the settings and changing the COIN.CONFIG from the http://forknote.net/create to more closely mimic what was setup in the default coin settings. i.e. coin decimal point and coin supply.
I think this is still an issue that needs to be looked at but my problem is resolved.
Activity
pmitchev commentedon Mar 3, 2018
You have 100% premined coin. The only rewards miners will get is from tx fees
Edit: If the reward is less than 0.000, it probably shows just up to 3 decimal points
2acoin commentedon Mar 4, 2018
I'd like to request that this issue be reopened... I set the pre-mine to be 10% of the total coin supply.
If I take the two, MONEY SUPPY and GENESIS_BLOCK_REWARD values from my coin.conf file and put them one on top of the other you can see that the Genesis Block (pre-mine) is only 10% of the Money Supply.
`
MONEY_SUPPLY=
17910000000000000000
GENESIS_BLOCK_REWARD=
1791000000000000000
`
I used the Create CryptoNote page on the forknote website to build my config. http://forknote.net/create
I can also view the wallet that I had the pre-mine coins go into and it reflects to proper ~179 million coins. Just to double check I ran through the whole coin creation process again using this settings;
And again, the pool is generating 0.00 transactions out to the miners. Even though I can see the miners should be receiving much more.
Is there something I need to change in the pool, since my coin decimal point is 10 instead of the default 12? Outside of the setting for coinUnits?
pmitchev commentedon Mar 4, 2018
I misread. Sorry. coinUnits indeed is the property controlling the decimal point. You probably have something misconfigured in the pool config, because this is definitely not the result you should see
blueavenue commentedon Mar 4, 2018
Try to set maxTransactionamount bigger than minPayment in config.json
2acoin commentedon Mar 8, 2018
I was able to resolve this issue by going back through the settings and changing the COIN.CONFIG from the http://forknote.net/create to more closely mimic what was setup in the default coin settings. i.e. coin decimal point and coin supply.
I think this is still an issue that needs to be looked at but my problem is resolved.