Quote from: almightyruler on October 05, 2019, 02:58:47 AM

Quote from: HashEngineering on October 01, 2019, 03:51:46 AM

The halving is every month (based on 30 second blocks). After 64 months, the halving number appears to return to 0 based on the undefined behavior of a 64bit number being right shifted 64 bits.

According to the C++ language, this operation has undefined results -- this means that the result could be different on different machines/CPU's.

If there are differences this could lead to forks or clients and apps that do not sync past 5529600.

So I see IFC's reward has wrapped around like I thought it may.

It's definitely important to avoid undefined behaviour in consensus code, and it will need to be addressed at some point, but I'm wondering whether anyone has actually forked away because their CPU does something different to the majority of IFC clients? Has anyone running a non x86 CPU had problems?

I know of at least one other coin which has gone beyond 64 bits, and we didn't need to fix the consensus code... but that community was not as large as IFC. There's also the question of whether the IFC community wants to "restart" rewards, or prefers it to stay at 0 indefinitely.

IFC has been completely mined, this is the consensus, so there will be no reward to reappear, the current consensus is to dig fees.