Quote from: vvrroooomm on November 16, 2018, 05:34:41 AM

Quote from: slb on September 13, 2017, 11:04:00 AM

Hi guys,
We added replay attack protection option in Forknote. Now you can use it to safely send transactions to both chains if you have old wallet, without worrying someone will replay it on the concurrent blockchain.

Usage:

1. Download Forknote - https://github.com/forknote/forknote/releases/tag/2.1.2
2. Use the following config for the Quazarcoin Forknote blockchain - https://github.com/forknote/configs/blob/master/quazarcoin.replay_attack_protection.conf
3. Use the following config for the Quazarcoin Minergate blockchain - https://github.com/forknote/configs/blob/master/quazarcoin.minergate.replay_attack_protection.conf

Forknote will force you to mix your coins with outputs after the the fork height, making the transaction invalid on the other chain.

I have not done any of this, what is the state of my few coins? Can someone explain what happens when you use the Forknote instructions above. Does it somehow change the coins to another coin, or just an alternative blockchain? Was this done to mitigate the Minergate running a messed up or double spendable chain? This is hard to understand what to do.

Note the blockchain that we are using is already updated and clean of any bug

feel free to join us on

pools: https://communitypool.org

Discord: https://discord.gg/88sZqyd