Skip to content

Bitnet v0.0.4b
Compare
Choose a tag to compare
@masayoshikob masayoshikob released this 27 Aug 09:33
· 9 commits to main since this release
v0.0.4b
353239e

Security patch and improved user experience. All prior versions will be deprecated.

  • Updated GPU Miner binary for Microsoft Windows
  • Miner is now disabled by default, and needs to be enabled with flags
  • Ethash improvements and removal of ice age
  • Security patch to prevent consensus-level attacks
  • Updated scripts for all OSs
  • General bug fixes
  • Core parameters updates, with new bootnodes and built-in genesis
  • Minor updates to the JSConsole

⚠ All prior versions will be deprecated, and updating your node is mandatory. Else your node may fork from the network in the coming days.

Full Changelog: v0.0.3b...v0.0.4b

If you have any issues syncing with the network, please try the following steps:

  1. If you're executing the Bitnet binary directly and in a single step, try initializing the protocol genesis before starting the bitnet (or bitnet.exe on Windows) binary. You can do that by running the command below inside your Bitnet folder - it assumes you have downloaded the latest pre-build release:
./bitnet --datadir bitnet.db init .bitnet && ./bitnet --networkid 210 --config .config

or, if you're on Windows:

.\bitnet --datadir bitnet.db init .bitnet ; .\bitnet --networkid 210 --config .config
  1. Try deleting your existing database for a full resync with the network. You can use the command below to delete the bitnet.db folder:
rm -rf bitnet.db

or, if you're on Windows:

rmdir /s /q bitnet.db

If after following the steps above you still cannot sync your node, please ask for help in one of our community channels. Most of our developers are more active on Discord than in other social media platforms.

Assets 5