Skip to content

Bitmark Core v0.9.7.0
Compare
Choose a tag to compare
@dbkeys dbkeys released this 20 Jun 18:18
· 179 commits to master since this release
v0.9.7.0
cdb2410
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Bitmark release v0.9.7.0

June 6, 2018

8 Proof-of-Work Algorithms (8 mPoW)

{ SCrypt,   SHA256d,   Yescrypt,   Argon2d,   X17,   Lyra2REv2,   EquiHash,   CryptoNight }

Difficulty Adjustments: Dark Gravity Wave v3 (DGW v3)

Each algorithm is governed by custom DGWv3 to balance mining difficulty to network hashrate.

  • "Surge Supressor" triples difficulty if 9 in-a-row from the same algo
  • "Resurrector" slices difficulty by 1/3 if an algo has not contributed in 160 min.

Subsidy varies according to Hash Rate

Reward variation by Coin Emission Modulation algorithm (CEM v0.1)
Modulates up to half of the block reward according to the ratio of currrent hashrate to peak hashrate.
50% of the block reward is scaled by the ratio (current_hr/peak_hr), the subsidy scaling factor (SSF),
where:

  • peak hashrate (peak_hr) is highest hashrate in last year and
  • current hashrate (current_hr) is hash rate for algo over last 90 blocks

90 blocks is the approximate daily output of blocks per algorithm. So, every 90 blocks (once a day), CEM looks back 365 of these 90 block periods to determine the highest hashrate for the algo in the past year, to use as the denominator of subsidy scaling factor (SSF). The numerator is the hashrate over the most recent 90 blocks, the current hashrate. This SSF is computed to determine the subsidy for that algo's next 90 blocks.

Binaries:
*Ubuntu 16.04 LTS "Xenial Xerus"
*Windows 64 & 32 bit
*MacOS (Generic: El Capitan and higher & High Sierra specific)

Bitmark BlockChain: 'bootstrap.dat ' file up to block 453088

Place the bootstrap.dat file in your ~/.bitmark directory (Linux) or
C:\Users<user>\AppData\Roaming\Bitmark (Windows)

Bitmark will automatically validate and import the "bootstrap.dat" file when it's placed in the data directory.
or can explicity ask to load from it when the node is run:

bitmarkd -loadblock=~/.bitmark/bootstrap.dat

Note: once it has been used, 'bootstrap.dat' will automatically be re-named 'bootstrap.dat.old'

Sha256 CheckSums: (shasum -a 256)

427f0a1ef753a995338ebac7203a1be7bcc3081da1802fc22ec49b69e6424b5f  bitmarkd-v0.9.7.0-official
acf13775d6b0e2f568b70401134c0aa137b485de208462f8a1b712884fcebf70  bitmark-cli-v0.9.7.0-official

7c84da57d03c0b06df55c06bd5d0dc8c3a7a8893441b8cc5be72c321e6b4951e  bootstrap.dat

4bdb6cd4035ae3b8f9cadbd4d36bd98f8d690cc422e30ae86f66db32bb74350e  bitmark-0.9.7.1-RC1-win64-setup.exe
4e5abccbe39793d9187ac551b59acd5c1cda1ddefa7c39e7780b572ee3e8b95a  bitmark-0.9.7.1-RC1-win32-setup.exe

94359b96b2987a752f4e8a34e3bcb0f268b1c49085d8406e9b535bdd4c1790df  Bitmark-Qt-HighSierra_0.9.7.1-RC1.dmg

ebaf23b1e6e2f6437263015fb43cb6adb0056a0923d1bdf306ab897c7905c8d1  Bitmark-Qt_0.9.7.1-RC1.dmg
Assets 9
Loading