[MANDATORY UPGRADE] DigitalNote 5.0.2 Release & DigitalNote GUI 1.0.15c-beta ReleasedTo be sufficiently prepared for the scheduled network upgrade,
users should download and run the new daemon (v5.0.2) or GUI wallet (v1.0.15c-beta) BEFORE block 669,369. Please note that this is a refork due to this issues explained here:
https://bitcointalk.org/index.php?topic=4451957.msg40980746#msg40980746. A blockchain resync is not needed, necessarily, but if you experience problems you may choose to do so. Only this version will work after the fork of June 25th . If you download/sync with the blockchain using the old digitalnoted (v4.0.3) or old GUI (v1.0.14-beta) after the hard fork, you will be on the old chain. Consequently, if you make a transaction while you are in this state, then that transaction will be on the old chain (don't worry, you can get your XDN back on the new chain per guides below).
Exchanges and major pools have been notified and sent the releases last weekend and will begin updating as soon as possible at which point their wallets will be back online.Information:On block 669,369 (approximate date June 27, 2018), there will be a hard fork on the DigitalNote network. This is a re-scheduled and consensual network upgrade, so unlike the BCH/BTC split a new coin won't be created. Rather, there will be a split in the DigitalNote blockchain, where the consensus will start following the post-fork (or "new") chain, instead of the pre-fork (or "old") chain.
Release Notes:- Proof-of-work change to CryptoNightV1 (variant 1 also known as "monero7") to remain ASIC resistant
- Difficulty adjustment algorithm has been updated to Zawy's LWMA-2 to resist hash and timestamp attacks
- Seed nodes updated to be operational (no more unresponsive seeds from old dev)
- Block target reduced to 2 minutes
- Difficulty is hard-coded to “reset” back to GPU levels for blocks immediately following the fork so that the network continues to work as intended and does not stall
- GUI embedded pool miner now works
- Latest checkpoints and small Payment Gate bug fix
- Arch Linux compile fixes
Download Linkshttps://digitalnote.biz/GUI Wallet (v1.0.15c-beta):https://github.com/DigitalNoteXDN/digitalnotewallet/releasesCLI daemon and wallet (v5.0.2):https://github.com/DigitalNoteXDN/digitalnote/releasesHow to Upgrade:1) Download the new binaries from the official website or Github.
2) Extract the new binaries to a new directory of your liking. This is the easiest and recommended way (alternatively, however, you can overwrite the old binaries).
3) Opening the new client will automatically load your wallet although it is recommended to always have a backup copy located somewhere else.
4) A blockchain re-sync is not needed. If you start the v1.0.15b-beta of DigitalNote it will simply pick up where it left off.
Paper Wallet:You don't have to do anything. However, if you want to restore a wallet after the scheduled network upgrade, you need to use the new binaries.
Solo Mining:You need to update the command line wallet to solo mine. Make sure to download v5.0.1.
Pool mining:Pool operators running dvandal's cryptonote-nodejs-pool should be ready to modify "cnVariant" to “1” in their config.json file after the fork height. Pools running other software should be ready to update their algorithm to monero7/CryptoNightV7/CryptoNightV1 (they are all different ways of saying the same thing). Miners should switch their software over to the CryptoNightv7 algorithm after the fork.
We recommend XMR-Stak v2.43+ but you can use any CryptoNight Variant 1 compatible miner:
https://github.com/fireice-uk/xmr-stak/releasesIn your pool.txt config be sure to set “currency” to “cryptonight_v7” after the fork (instead of “cryptonight”).
Welcome home, GPU miners.Common issues:Below are Monero based guides for when they similarly hard forked earlier this year, so the wallet versions and block heights will be different, but the same process applies to DigitalNote:
I forgot to upgrade (from CLI or GUI v0.1.4.0 to CLI or GUI v0.2.0.x) before block 170000 and, as a result, accidentally synced to the wrong (alternative) chain:https://monero.stackexchange.com/questions/7989/i-forgot-to-upgrade-from-cli-or-gui-v0-11to-cli-or-gui-v0-12-and-as-a-result/I forgot to upgrade (from CLI or GUI v0.1.4.0 to CLI or GUI v0.2.0.x) before block 170000 and created / performed a transaction on the wrong (alternative) chainhttps://monero.stackexchange.com/questions/7993/i-forgot-to-upgrade-from-cli-or-gui-v0-11to-cli-or-gui-v0-12-and-created-pe/If you still require help, please post your issue in this thread and describe it in as much detail as possible. Also, feel free to post any other guides that could help people and we will add them to the list.
Contributors for this Release:-AuCRHI
-CocaCola
-Zawy
-Grunsen
-Rainman