Infinite Coin 1919 Version (Restoration of the Original Chain)
source code
https://github.com/WilliamXuu/infinitecoin
Execution document
https://github.com/WilliamXuu/infinitecoin/releases
Author: William Xu
Block download (synchronized to 5529012)
https://mega.nz/#!gzwFUSAD!2Pow5A3fE4iDZG5gPxesuxoXV_GGyD8vDN6yIkjkTgA
Infinite Currency Block Browser
https://chainz.cryptoid.info/ifc/
Infinite Bitcoin Forum Theme
https://bitcointalksearch.org/topic/ann-infinitecoin-update-to-188-visit-infinitecoincom-356065
Infinite Currency Babbitt Forum Column
https://www.chainnode.com/forum/372
Note: In addition to downloading source code and execution files on the website, the blocks before 5529599 can also be downloaded in the infrastructure group.
Perfect restoration
Error-clearing blocks are synchronized from 5529599 to 188 1910 1918, and will be synchronized to the correct link. However, in case of emergency, it is recommended that you use 1919.
Topic: [ANN] INFINITECOIN - UPDATE TO 1.8.8 visit INFINITECOIN.COM - page 65. (Read 155187 times)
Through a week of hard work and the help of IFC fans, Perfect solution to IFC crisis.
Thank you all for helping IFC.
The main chain is now generated by the wallet of version 1919, and the old wallet can be resynchronized from 5529599 to avoid the remaining error blocks with additional issuance.
Previous versions of wallets still have the vulnerability of additional issuance, so I recommend that they not be used anymore.
Thank you all for helping IFC.
The main chain is now generated by the wallet of version 1919, and the old wallet can be resynchronized from 5529599 to avoid the remaining error blocks with additional issuance.
Previous versions of wallets still have the vulnerability of additional issuance, so I recommend that they not be used anymore.
Thanks to all the IFC fans who participated in this bug fix, you are the best 
Infinite currency, IFC version 1.9.1.9 wallet has gone beyond the wrong block, miners mining machines are running, continue to develop one person one mining machine plan! Just dug up a fortunate mine, so big, ha ha ha!
Error blocks have been successfully repaired, version 1.9.1.9 wallet has gone beyond the error blocks, miners mining machines are running, continue to develop a one-person-one-miner plan!
About infinitecoin overflow vulnerability has been successfully fixed
1 Delete error block and sync from 5529599
2 Using the 1919 version
3 Upgrade your wallet version and full-node version
Source code
https://github.com/WilliamXuu/infinitecoin
Wallet download
https://github.com/WilliamXuu/infinitecoin/releases
Author: WilliamXu (WilliamXu1)
Infinitecoin block 5529012 download
https://mega.nz/#!gzwFUSAD!2Pow5A3fE4iDZG5gPxesuxoXV_GGyD8vDN6yIkjkTgA
InfiniteCoin Blockchain Explorer
https://chainz.cryptoid.info/ifc/ （Syncing）
Known 1919 version of the full node
addnode=8.209.73.126
addnode=47.108.82.81
addnode=47.252.81.22
addnode=47.245.52.188
addnode=149.129.174.246
addnode=140.143.207.19
addnode=95.179.221.207
addnode=220.179.77.92
addnode=139.180.137.140
addnode=222.71.191.210
addnode=118.24.129.200
addnode=47.92.211.243
addnode=115.212.200.109
addnode=39.99.33.79
1 Delete error block and sync from 5529599
2 Using the 1919 version
3 Upgrade your wallet version and full-node version
Source code
https://github.com/WilliamXuu/infinitecoin
Wallet download
https://github.com/WilliamXuu/infinitecoin/releases
Author: WilliamXu (WilliamXu1)
Infinitecoin block 5529012 download
https://mega.nz/#!gzwFUSAD!2Pow5A3fE4iDZG5gPxesuxoXV_GGyD8vDN6yIkjkTgA
InfiniteCoin Blockchain Explorer
https://chainz.cryptoid.info/ifc/ （Syncing）
Known 1919 version of the full node
addnode=8.209.73.126
addnode=47.108.82.81
addnode=47.252.81.22
addnode=47.245.52.188
addnode=149.129.174.246
addnode=140.143.207.19
addnode=95.179.221.207
addnode=220.179.77.92
addnode=139.180.137.140
addnode=222.71.191.210
addnode=118.24.129.200
addnode=47.92.211.243
addnode=115.212.200.109
addnode=39.99.33.79
In the field of encrypted electronic money, there is a buzzword: "Bitcoin is Gold, Litecoin is Silver, Infinitecoin is Copper", which means "bit gold, Wright silver, infinite copper".
I am very happy that we have solved the problem.
Thanks to everyone who paid for it.
Thanks to everyone who paid for it.
Hello, fans of IFC, the whole node of 1.8.8 has a vulnerability, please upgrade the full node of IFC to 1.9.1.9, and finally thank all the fans who contributed selflessly to IFC in this IFC vulnerability fix!
Congratulations to IFC for successfully solving the bug. Now you need to upgrade the 1.9.1.9 version of the whole node. Synchronize from before the 5529599 block to eliminate the additional blocks.
Block generated by 64-bit Linux 1.8.8 version
Infinitecoin block 5529012 download
https://mega.nz/#!gzwFUSAD!2Pow5A3fE4iDZG5gPxesuxoXV_GGyD8vDN6yIkjkTgA
Infinitecoin block 5529012 download
https://mega.nz/#!gzwFUSAD!2Pow5A3fE4iDZG5gPxesuxoXV_GGyD8vDN6yIkjkTgA
The 1919 version of the bug fix has been successfully released
Source code
https://github.com/WilliamXuu/infinitecoin
Source code
https://github.com/WilliamXuu/infinitecoin
Uh oh. Making this code "effective immediately" will break consensus on existing clients, and will cause a hard fork. If peers disagree on rewards they will probably ban each other (as they should), which will split the network. The fork point really should have been set at a future block, so people had time to upgrade.
I understand why it's being done, but the point I am making is that the blockchain fork should have been activated at some future block number, to give people a chance to upgrade.
Because you've changed consensus code I think you may also have problems with people syncing, since the fork point will be set to the first 64 bit halving (block 5529600). People who have already synced past this point (which is anyone who has run the IFC client in the past 2 weeks) may be left on another blockchain fork, even once they upgrade.
Current blockchain looks like this:
#5529599 0.0 IFC
#5529600 524,288.0 IFC
...
#5544990 524,288.0 IFC
But a client with the new version syncing from scratch (or a block below #5529600) will expect:
#5529599 0.0 IFC
#5529600 0.0 IFC
...
#5544990 0.0 IFC
This is where the consensus fails and peers start banning each other for misbehaving. It may require people who are fully synced to delete the blockchain and start again. In addition, since the fork point is in the past, any transactions that were sent after #5529599 will be invalidated.
Code should be something more like
//Force block reward to zero when right shift if undefined
if(halvings>=64 && nHeight >= 5616000) // hard fork point set to specific block in future
return nFees;
Bitcoin fixed the problem before it happened, so the change in consensus code will not cause a hard fork.
If there is a block with errors, please synchronize from the block before 5529599
The 1919 version of the bug fix has been successfully released
Source code
https://github.com/WilliamXuu/infinitecoin
Source code
https://github.com/WilliamXuu/infinitecoin
Uh oh. Making this code "effective immediately" will break consensus on existing clients, and will cause a hard fork. If peers disagree on rewards they will probably ban each other (as they should), which will split the network. The fork point really should have been set at a future block, so people had time to upgrade.
I understand why it's being done, but the point I am making is that the blockchain fork should have been activated at some future block number, to give people a chance to upgrade.
Because you've changed consensus code I think you may also have problems with people syncing, since the fork point will be set to the first 64 bit halving (block 5529600). People who have already synced past this point (which is anyone who has run the IFC client in the past 2 weeks) may be left on another blockchain fork, even once they upgrade.
Current blockchain looks like this:
#5529599 0.0 IFC
#5529600 524,288.0 IFC
...
#5544990 524,288.0 IFC
But a client with the new version syncing from scratch (or a block below #5529600) will expect:
#5529599 0.0 IFC
#5529600 0.0 IFC
...
#5544990 0.0 IFC
This is where the consensus fails and peers start banning each other for misbehaving. It may require people who are fully synced to delete the blockchain and start again. In addition, since the fork point is in the past, any transactions that were sent after #5529599 will be invalidated.
Code should be something more like
//Force block reward to zero when right shift if undefined
if(halvings>=64 && nHeight >= 5616000) // hard fork point set to specific block in future
return nFees;
Bitcoin fixed the problem before it happened, so the change in consensus code will not cause a hard fork.
The 1919 version of the bug fix has been successfully released
Source code
https://github.com/WilliamXuu/infinitecoin
Source code
https://github.com/WilliamXuu/infinitecoin
Uh oh. Making this code "effective immediately" will break consensus on existing clients, and will cause a hard fork. If peers disagree on rewards they will probably ban each other (as they should), which will split the network. The fork point really should have been set at a future block, so people had time to upgrade.
If your consensus is a fixed total of 90.6 billion IFC
Then you should upgrade the node 1919 version that fixes the vulnerability.
See Bitcoin on June 1, 2014 0.9.2 rc1 version
IFC fix vulnerability on line 873
https://github.com/WilliamXuu/infinitecoin/blob/master/src/main.cpp
Please check the bitcoin source code
https://github.com/bitcoin/bitcoin/releases?after=v0.9.2
IFC Infinite Currency 1919 version of the bug fix program has been successfully repaired, and has been successfully released!
source code
https://github.com/WilliamXuu/infinitecoin
Wallet Download
https://github.com/WilliamXuu/infinitecoin/releases
Author: William Xu (William Xu1)
Update the node version
7,000 gaps are estimated to take more than two days
source code
https://github.com/WilliamXuu/infinitecoin
Wallet Download
https://github.com/WilliamXuu/infinitecoin/releases
Author: William Xu (William Xu1)
Update the node version
7,000 gaps are estimated to take more than two days
The 1919 version of the bug fix has been successfully released
Source code
https://github.com/WilliamXuu/infinitecoin
Source code
https://github.com/WilliamXuu/infinitecoin
Uh oh. Making this code "effective immediately" will break consensus on existing clients, and will cause a hard fork. If peers disagree on rewards they will probably ban each other (as they should), which will split the network. The fork point really should have been set at a future block, so people had time to upgrade.
The 1919 version of the bug fix has been successfully released
Source code
https://github.com/WilliamXuu/infinitecoin
Wallet download
https://github.com/WilliamXuu/infinitecoin/releases
Author: WilliamXu (WilliamXu1)
Please update the node version
10,000 block gaps estimated to take more than 3 days
Source code
https://github.com/WilliamXuu/infinitecoin
Wallet download
https://github.com/WilliamXuu/infinitecoin/releases
Author: WilliamXu (WilliamXu1)
Please update the node version
10,000 block gaps estimated to take more than 3 days
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.
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.
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.
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.
If successful, ifc will make an important contribution to the recognition of the digital currency model on a global scale.
Jump to: