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
{{ message }}
This repository has been archived by the owner on Sep 13, 2018. It is now read-only.
Because FairCoin is a clone of a coin which has been designed for mining, the network runs much smoother with some mining activity. The mining reward has been lowered to a minimum amount (0.00001FAC) to underline that FairCoin is a Proof-of-Stake coin. Unfortunately supportive mining is not possible at this time because the transaction check does not allow such tiny value in the reward transaction and rejects every mined block. To be clear: minting stake blocks is NOT affected, the network runs as good as before the hard fork. Just mining is still not possible.
This bug is easily fixed but results in an other hard fork.
The text was updated successfully, but these errors were encountered:
I guess we never encountered this problem on TestNet because we never mined through the 15555 barrier :( Would a fix be to increase the reward to at least the transaction amount (I believe 0.001) + 0.00001 FAC?
Yes, that's right. I had it on my test plan but it somehow slipped through it...
Yes, right, I already fixed it that way. The reward is again 0.001 FAC.
Because FairCoin is a clone of a coin which has been designed for mining, the network runs much smoother with some mining activity. The mining reward has been lowered to a minimum amount (0.00001FAC) to underline that FairCoin is a Proof-of-Stake coin. Unfortunately supportive mining is not possible at this time because the transaction check does not allow such tiny value in the reward transaction and rejects every mined block. To be clear: minting stake blocks is NOT affected, the network runs as good as before the hard fork. Just mining is still not possible.
This bug is easily fixed but results in an other hard fork.
The text was updated successfully, but these errors were encountered: