We are very pleased to announce that the Intense Coin network has been updated on schedule, and the version 4 hard fork was successful! The network is in full operation, and has been on block version 4 since block 166,134. At the time of this post, about 1,000 blocks have been mined on the new fork. The latest network upgrade requires version 2.0 (“Belaya”) or later of the Intense software (CLI download).
The Intense Coin network is now more ASIC resistant after adopting cryptonight variant 1 (also known as Monero version 7) proof-of-work, more responsive to hash attacks after implementing an improved difficulty algorithm from zawy, and anonymity and privacy have been bolstered significantly after enacting Ring Confidential Transactions (RingCT). Overall, the Intense network is harder, faster, better and stronger!
The remainder of this post will detail all information relevant to the hard fork: how to update, what it is, and how you’re affected. The bulk of the following information is courtesy of Venthos (ITNSpool.net Admin).
What You Need to Do
Download the latest software
- Upgrade your daemon and/or wallet software as soon as possible. Unless your daemon and/or wallet are version 2.0 or later of the software, they will not correctly sync with the network. At this time, new command line (CLI) binaries are available for Windows, Linux and Mac. GUI binaries will be updated in the coming days, but motivated users could connect the 1.45 or 1.5 GUI wallet to a 2.0 daemon without issue.
What is the process to upgrade?
Download the software as described above. If you haven’t already updated your wallet for use in 1.45 or later (‘XMR Rebase’), see instructions below on upgrading your wallet. If you already upgraded your wallet for use in 1.45+, you can continue to use the same wallet file in 2.0 or later of the software.
- After you open the version 2.0 daemon, check the current blockchain height by entering
print_heightin the daemon. It should match the height displayed on the Intense Blockchain explorer. If your displayed height is markedly higher than the explorer, your database is synced to the v3 fork. To resolve, close the daemon, run
intense-blockchain-import --pop-blocks 7500, and re-open the daemon to sync to the proper chain. The
intense-blockchain-importtool is in the same directory as the
What if I see messages about synchronization and my node being out of sync by several days? It says the top block is 172000+?
Those messages are coming from people that have not updated their software and are still running the v3 fork. You can safely ignore them. The messages will disappear over time as everyone runs version 2.0 or later of the software.
Determine if any of your prior transactions were affected
Any transactions contained in blocks after 166133 on version 3 of the network will “poof” from your wallet since the hard fork has occurred. This only applies if your transaction did not take place on the NEW chain. You can verify this by checking for the transaction ID in the block explorer!
- Open your wallet as usual
- Run show_transfers
The first column contains the block height of that transaction. If any transaction has a block height higher than 166133, it will disappear after the hard fork and no longer exist on the blockchain.
1.4.1/1.4.2 GUI Wallet
- Open your wallet as usual
- Click to the “Transactions” tab
- Click on the “Hash” for your most recent transaction
If the “Block Height” for that transaction is higher than 166133, it will disappear after the hard fork and no longer exist on the blockchain. You could then continue clicking on each transaction’s hash in your list until you get to a transaction that is at or below height 166133. At that point, you will know which of your transactions will remain.
1.45+ GUI Wallet
- Open your wallet as usual
- Click to the “History” tab
If the “Block Height” for any transaction in your history is higher than 166133, it will disappear after the hard fork and no longer exist on the blockchain.
If you have affected transactions, plan accordingly.
If they were incoming transactions (received coins), you will need to reach out to whoever sent you those coins once the hard fork occurs and ask them to resend those coins to you. Note that if it is a pool payout, the coins may be from the block reward that the pool will no longer have received (since any block rewards after 166133 would be lost and gone missing from the pool’s wallet, too)
If they were outgoing transactions (sent coins), you will need to resend the coins yourself once the hard fork occurs.
If you have checked to verify for missing transactions and your wallet was synced to the v3 chain after the 166133 fork, you will need to open your wallet in `intense-wallet-cli` and enter the command `rescan_spent` to remove references to old v3 blocks.
If you are still using 1.4.2 or earlier, upgrade your wallet
If you have not gotten around to converting your wallet to the newer 1.44+ XMR Rebase wallet, you are now required to migrate it. Unless you migrate your wallet, you will be unable to use your wallet after the hard fork occurs.
Note that for the reasons above, it is no longer an option to create a new wallet and send coins from your old version wallet to the new wallet. You must do a conversion of the wallet now if you hadn’t already done so prior to block 166133.
Please follow this guide if you need to migrate your wallet: GUIDE: Converting your 1.4.1/1.4.2 Wallet to the 1.45+ XMR Rebase Wallet
Please Note: You will need to operate a run command to properly open your wallet in the rebase. To do this, go to the folder with the new 2.0 CLI. Copy its directory as text. You can do this by right clicking the folder at the top of the screen. Once you have the directory, press the Windows key and the “R” key together. This will open a run command. Place an open quote in the run command, then past the folder directory. After the folder directory, you will need to type *without quotes* “\intense-wallet-cli.exe”. You will then need to close your quotation marks. After that, please paste “–generate-from-keys newrebase.wallet” without quotes.
It should look like the following:
Note that this conversion can be done at anytime (prior to or after the fork). It does not require the ability to “use” the blockchain to perform the conversion.
Continue to watch official communication channels for updates.
What is a hard fork?
A hard fork is when significant changes are made to the blockchain tools that make previous versions of the tools incompatible with it. The new tool’s rules for what are valid blocks are different than older tool’s rules, and thus a software update is required.
Has Intense Coin hard forked before?
Yes. Twice, actually. The original chain (v1) was first generated on 2017-08-15. ITNS forked to v2 on 2017-10-27, and later forked to v3 on 2017-12-04. Since then, we’ve all been using the “3rd generation” of the intense coin blockchain. Anyone using older v1 or v2 tools will have not been able to interact with our current chain since 2017-12-04. For reference, Monero has hard forked 6 times (they are v7 of their chain).
What does this mean for May 14th’s Hard fork?
May’s hard fork is being pushed up to be included in this emergency April 21st hard fork. The May hard fork will no longer happen. This diagram shows what is happening now vs. what was planned.
What is a rollback?
A rollback is when the developers/community decide that irreparable damage has been done to the blockchain by a malicious actor, and that the only fair thing to do is to revert the blockchain to a state prior to the attack. Since the blockchain is unable to be changed or modified, the only way to do this is to release a new set of tools that have logic coded into it to consider a specific block to be invalid. This causes the tools to ignore the existing mined blocks after that height and start mining new ones instead.
Has Intense Coin rolled back before?
No. This is not a usual or planned process. However, without rolling back the chain in this way, the attacker would have 8 million+ ITNS in their pockets from the exploits. The inconvenience of the rollback is deemed less impactful than such a large volume of ill gotten coins flooding the market.
What is this I keep hearing about Block 166133?
The attack first occurred with Block 166134, meaning that this block and anything mined after it make up what is considered to be a “tainted” portion of the blockchain. Intense Team developers have therefore decided to “fork” the blockchain at block 166133, abandoning the tainted portion of the chain that contains the hacked coins.
Why can’t you just remove the hacked coins?
Intense Coin, like other Cryptonote based coins, is anonymous. It is not possible for anyone (even the developers) to determine where the hacked coins were mined to. This means it is not possible to hard-code the blockchain tools to remove those coins from the hacker’s wallet. The only feasible option is a “scorched earth” situation via hard forking and rolling back the chain to a block prior to the exploit.
Exchange User Questions
Are my coins on stocks.exchange or tradeogre.com affected?
No. Your coins with an exchange are not actually stored on the blockchain. The exchange simply has their own database that says they owe you a certain amount of certain types of coins. However, if you deposited or withdrawn coins from an exchange and your personal wallet shows that deposit/withdrawal as being on a block after 166133, that withdrawal/deposit will be lost in the hard fork rollback. Intense Team acted quickly to ask these exchanges to halt withdrawal/deposits to minimize the chances of this happening. Use the “What You Need to Do” section earlier in this guide to identify if your transactions are affected. If they are, you will need to reach out to the exchange so that they can adjust your account with them to reflect any transactions that will be abandoned by the hard fork’s rollback.
Can I still trade ITNS safely?
Yes. Exchange trading is entirely an “off chain” process that does not involve or require the blockchain. You can trade in or out of ITNS without fear of having those trades rolled back by the hard fork. Exchanges will be notified shortly that they need to upgrade to the latest versions of the software to resume on-chain trading.
Can I keep mining to my old wallet address before I upgrade the wallet and/or software?
Yes. Your wallet address and coins are not going anywhere.
How do I know if the pool I’m mining is updated for the v4 hardfork?
Compare the top block shown at the pool with that of the Intense Coin block explorer. The numbers should match or be very close. If they do not match, the pool has not updated and needs attention, and is not worth your mining power.
What do I need to do to make sure I can mine after the hard fork?
As part of this hard fork, Intense Coin is adopting Monero’s proof of work change. This algorithm is called “CryptoNight v1”, or Cryptonight Variant 1. You will often see this incorrectly referenced as CryptoNight v7 by folks unfamiliar with the proof of work change. The “v7” comes from the Monero version that adopted it (Monero v7), but the actual algorithm is “CryptoNight v1”. So where Monero v7 adopted CryptoNight v1, Intense Coin v4 is adopting CryptoNight v1.
This means that your mining program must support this new CryptoNight v1 algorithm.
Some mining programs allow you to manually specify the algorithm instead of specifying the coin. For those programs, simply specify “CryptoNight v1” and you will be able to resume mining without issue after the hard fork. The mining programs will likely be patched in the coming days to support mining “Intense Coin v4” out of the box.
This is, of course, assuming that the pool you are mining with has made the necessary changes on their end to support the hard fork. Please reach out to the pool admin(s) for the pool you are mining with to confirm whether they have made the necessary changes to make their pool compliant with the hard fork as well as CryptoNight v1.
Pool Admin Questions
How do I upgrade my pool to be compliant with the hard fork?
You will need to perform several steps.
- If your pool was still operating on the 1.4.2 or earlier daemon/wallet, then you will need to go up to the “What You Need to Do” section and follow the wallet upgrade steps to upgrade your pool’s wallet to the new XMR Rebase.
- If your pool was still operating on the 1.4.2 or earlier daemon/wallet, then you will need to upgrade your pool software to be compliant with the new XMR Rebase.
- Regardless of daemon/wallet version, you will need to modify your pool configuration to use a minimum of “4” MixIn for its transactions (otherwise payouts will fail and be rejected).
- Regardless of daemon/wallet version, you will need to upgrade your pool software to be able to handle the new CryptoNight v1 algorithm.
Possible upgrade paths:
- If you are using nodejs-pool, you can upgrade to the fork Venthos maintains and be completely compliant with the new hard fork.
- If you are using intense-pool (the official pool repo software), it has not been updated and is unlikely to be updated. We ask pool admins to switch to Venthos’ fork or another PPLNS-compliant pool software, which reduces the allure of NiceHash and other cloud mining services to temporarily drive up blockchain difficulty.
- If you are using some other pool software, your mileage may vary on what changes you need to make depending on if it supported the XMR rebase already or not. But you are almost guaranteed to need to make changes to accommodate CryptoNight V1 for Intense Coin at Block Version 4 within the pool software.
Will my miners be affected?
If your pool mined any blocks past height 166133 on the v3 fork, then those block rewards will be reverted from the pool wallet after the hard fork. You will no longer have those funds to payout to your miners. This means you will likely have “credited” miners with balances that your pool is unable to pay.
Similarly, if you have performed any payouts where their transaction was contained in a block past 166133, those payouts will revert and go missing from your miner’s wallets after the hard fork. However, your pool software will continue to show that you “paid them” this amount. Since it is possible that a payout transaction in a block after 166133 contained balances due to a miner for blocks mined before 166133, you may technically still owe them some or all of that payout.
Realistically, your options are to:
- Rollback your own pool software and its database to a date prior to mining any blocks past 166133 so that balances are accurate and reflect legitimate blocks.
- Eat the loss out of your own pocket and fund the pool wallet with additional ITNS to cover the bogus balances your miners will have. Additionally, attempt to determine what payouts, if any, are legitimately owed to miners for blocks mined prior to 166133 that were paid out in a transaction after block 166133 and manually pay those out to those miners.
If you did not mine blocks past 166133 or did not send any payouts that have transactions in a block past 166133, then you should not have any inaccurate balances or reverted payouts as long as you keep the pool off.
How can I get my pool updated?
You will likely do the following:
- Download the new blockchain tools released by Intense Team (`git pull` the latest repo)
- Compile them
- Move away/delete the old blockchain (NOT your wallets!)
- Re-sync the blockchain up to 166133+
- Restart your pool
- Enjoy mining on ITNS v4
Note: This assumes you have updated your pool software as advised earlier in this post.
Let’s get back to business!
Now that the V4 hard fork is complete, let’s get back to what matters most: creating and providing decentralized, blockchain provided VPN! Fortunately, our VPN developers were able to continue work on the VPN side of things while the blockchain developers sorted through the hard fork. Stay tuned for more updates!
If you’re curious, our software release codename Belaya may just be an indicator of something to come in the future… 😉