Skip to content

Releases: project-bitmark/bitmark

Bitmark Core v0.9.7.2

05 Jul 13:38
2c236eb
Compare
Choose a tag to compare

Bitmark Release v0.9.7.2

bitmark.conf file now accepts either 'miningalgo' or simply 'algo' to specifiy choice for mining.
Bump Network Protocol version to 70003 to facilitate distinction from pre-fork nodes.

8 Proof-of-Work Algorithms (8 mPoW)

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

Difficulty Adjustments: Dark Gravity Wave v3 (DGW v3)

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

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

Block Rewards vary according to Hash Rate

The block reward variation by Coin Emission Modulation algorithm (CEM v0.1), also known as Coin Emission Rate Reduction acts (modulates) on one-half of the block reward according to the ratio of currrent hashrate over peak hashrate.
50% of the block reward is reduced by the Emission Reduction Factor = ratio (current_hashrate / peak_hashrate), also known as the subsidy scaling factor (SSF),
where, for each of the 8 proof-of-work algorithms used in Bitmark mining:

  • peak hashrate (peak_hashrate) is highest hashrate in last year and
  • current hashrate (current_hashrate) is hash rate average of the last 90 blocks (1 day)

Note that if the current hashrate equals the peak hashrate, then then ERF factor is unity, and no reduction takes place; the full nominal reward for the epoch is given.

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 the Emission Reduction Factor (ERF). The numerator is the hashrate over the most recent 90 blocks, the current hashrate. This ERF is computed to determine the subsidy for that algo's next 90 blocks.

Program Binaries for these mainstream OS's:

*Windows ( 64 & 32 bit )
*MacOS Intel ( El Capitán and above )
*MacOS Apple M1. silicon

*Linux / Ubuntu ( 16.04 LTS "Xenial Xerus", 18.04 "Bionic Beaver")
Note: binaries versions for both libsodium 23 (latest) and libsodium 18 (default for Ubuntu 16.04)
64b = 64 bit; .s = stripped of debug symbols (to reduce memory footprint)

  • Raspbian v9 "Stretch"
  • RaspberryPi OS v10 "Buster"

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

Place the bootstrap.dat file in your home directory:

Windows: C:\Users\<user>\AppData\Roaming\Bitmark
Mac: /Users/<user>/Library/Application Support/Bitmark'
Linux: /home/<user>/.bitmark

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)


f34a41ffdde828a07f2f9e3d4e969d8c82cf0f7b10207fee5634c0a3576ab06b  Bitmark-cli.v0.9.7.2-Ubuntu16.04-Official.64b.s
640cf5d7caf4e7db7b81429099274086230b01dcfe1252f7c2218d78b2900ec5  Bitmarkd.v0.9.7.2-Ubuntu16.04-Official.64b.s
18eaec8f2d5b7ab0423c0410bec7f54a57b2babc85f8849a47f19c7aee82602c  Bitmark-cli.v0.9.7.2-Ubuntu_18.04-Official.64b.s
e36915c866cbb1b823fd37477c297cdffb68002cb368b47cdff3ff09dae43c79  Bitmarkd.v0.9.7.2-Ubuntu_18.04-Official.64b.s
6526d962a17ead0d1bfdfcb6f9969fa76193014dee872fde9c1f21b6f83b3119  bootstrap.dat
e49d5a3406e3f7c5b394de15e5cc0ba0367c36d432ba60a1cc6fc6489b8bb623  Bitmark-0.9.7.2-Win64-Official-setup.exe
253a5848a290ebfe4d832f585800500f21c1e1cb2662ed0ea6fc86304e63ab82  Bitmark-0.9.7.2-Win32-Official-setup.exe
72f61df8e3c33d893341d208c675c022026b10b500d10388cd8cba2abc25119f  Bitmark-Qt_0.9.7.2-MacOS-Official.intel.dmg
42d6f986e3a75788a66821634c932581fea28f4fb39dfcf14c57c5a9a29a32ff  Bitmark-Qt.9.7.4.Apple.M1.silicon.dmg
e6d2d26a6430b0c0ad7b8b66f3f1efe9c84278bca4acdd19d2bc043715edecc9  Bitmark-v0.9.7.2-Raspbian.v9-Stretch-Official.armhf.deb
51a4764b03eca450c947344e0969dc01014482df640fdeb29d6c006cb9522bb6  Bitmark.v0.9.7.2-RaspberryPi-OS.v10-Buster-Official.armhf.deb

Bitmark Core v0.9.7.1

24 Jun 18:40
Compare
Choose a tag to compare

Bitmark pre-release v0.9.7.1

Bump Network Protocol version to 70003. Facilitate distinction from pre-fork nodes.

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", 14.04 "Trusty Tahr")
*Windows ( 64 & 32 bit )
*MacOS ( El Capitán and above )

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)

21d0ae1a7c3ff87479a5dc30d0b3cc56cad9aae557d66753fece9b5f1f39290c  bitmark-cli-v0.9.7.1-Ubuntu16-RC1.64b.s
9385ab854264a5adaeca50dd8ee1c7aa5ba3c6bcef409e4c1a0559b27ef24689  bitmarkd-v0.9.7.1-Ubuntu16-RC1.64b.s
0c18518a641449cc54a9a806eb1db6f71dd4cc2e1c0f3886babd464fc5759918  bitmark_0.9.7rc1_armhf.deb

Bitmark Core v0.9.7.0

20 Jun 18:18
cdb2410
Compare
Choose a tag to compare

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



Bitmark Core v0.9.5.1

10 Dec 20:03
70e8c41
Compare
Choose a tag to compare
Bitmark Core v0.9.5.1 Pre-release
Pre-release

Bitmark Core v0.9.5

(Note: versions prior to Bitmark v0.9.7.0 are incompatible ! Retained for historical purposes. )

###MacOS, Raspbian & Windows ( 32bit & 64 bit)

Updating

  • Download
  • Backup your wallet (File > Backup Wallet)
  • Close Bitmark
  • Run the installer / update:
    + MacOS: Double Click on .dmg file, drag Bitmark-Qt into Applications folder;
    + Raspberry Pi / Raspbian: dkpg -i bitmark_0.9.5-rc1-master_armhf.deb
    Binaries are placed in /usr/bin
  • Open Bitmark

Changes

  • Updated DNS Seeders
  • Abbreviations for RPC Client / Server commands
  • Tracks and Displays Total Bitmarks Emitted (Money Supply)

Sha256Sums

3f50ef94dbedea29a1be4fc0bbc13cdaf91b1b0a7ba9852310041112e2a82c6c  bitmark-v0.9.5-rc1-qt.dmg
671198e9d419d5863c8ef28eb6685fe754e9706ee347b8385af63e15d1ca2227  bitmark_0.9.5.1.master_armhf.deb
49a10a1240f2953a5519c83f944a0169a07986314e97e2e4e151ff607ae19ea3 bitmark-0.9.5-win32-rc1.setup.exe
76c0abb680ab867d6253c284cfcb0618d9c4e1e0039dd70da859d51006f137c7 bitmark-0.9.5-win64-rc1.setup.exe

Bitmark Core v0.9.4

18 Feb 14:38
Compare
Choose a tag to compare

This version of Bitmark Core aligns with Bitcoin 0.9.4, including post release updates.

This version of the 0.9.x series core has seeding from DNS. Previous versions of Bitmark Core will also automatically use seeds from DNS.

Updating

  • Download
  • Backup your wallet (File > Backup Wallet)
  • Close Bitmark
  • Run the installer / update
  • Open Bitmark

Changes

  • Limit the number of new addresses to accumulate
  • Disable SSLv3 (in favor of TLS) for the RPC client and server.
  • Guard against openssl's new strict DER checks
  • Fail immediately on an empty signature
  • Upgrade to openssl-1.0.1k.tar.gz
  • Improve robustness of DER recoding code

Sha256Sums

ca728ee818949029f54556a6b8955d3328b7dbf7dbd561ffef774d2ba7250d43  bitmark-0.9.4-linux.tar.gz
380edafb1677ea81dc33eac16819f347ba3cace9101f3fb00c12ae1b4238bc4b  bitmark-0.9.4-win32-setup.exe
bbd6f14146fb15aaef9ad616f36a0ca62cdac6268a84b9ef3976dc6581ec40f0  bitmark-0.9.4-win64-setup.exe
2b4b3d619d5ee54739df3926d69dc2c2e180852fa281d5c352549e60ffef1ea5  bitmark-0.9.4-win.zip
767acd0d1fd646a5fab6f69eb9b7ea54be043e002d10b8ab8e81cc96cca85fbb  bitmark-0.9.4-qt.dmg

Bitmark Core v0.9.3

04 Dec 01:20
Compare
Choose a tag to compare

This version of Bitmark Core aligns with Bitcoin 0.9.3, including post release updates.

It also includes Bitmark specific changes most notably the private key format has changed, a converter can be found at http://bitmark.co/brain to swap between old and new keys.

Existing wallets, and backups will continue to work as expected, only exported keys / cold storage keys need to be converted before import.

Updating

  • Download
  • Backup your wallet (File > Backup Wallet)
  • Close Bitmark
  • Run the installer / update
  • Open Bitmark

Major Changes

  • Private key version change to 213 to align with common third party tools.

Post Release Updates:

  • Make -proxy set all network types, avoiding a connect leak.
  • Refactor Alert to use static methods.

RPC:

  • Avoid a segfault on getblock if it can’t read a block from disk
  • Add paranoid return value checks in base58

Protocol and network code:

  • Don’t poll showmyip.com, it doesn’t exist anymore
  • Add a way to limit deserialized string lengths and use it
  • Increase IsStandard() scriptSig length
  • Avoid querying DNS seeds, if we have open connections
  • Remove a useless millisleep in socket handler
  • Stricter memory limits on CNode
  • Better orphan transaction handling
  • Add -maxorphantx= and -maxorphanblocks= options for control over the maximum orphan transactions and blocks

Wallet:

  • Check redeemScript size does not exceed 520 byte limit
  • Ignore (and warn about) too-long redeemScripts while loading wallet

GUI:

  • fix ‘opens in testnet mode when presented with a BIP-72 link with no fallback’
  • AvailableCoins: acquire cs_main mutex
  • Fix unicode character display on MacOSX

Miscellaneous:

  • key.cpp: fail with a friendlier message on missing ssl EC support
  • Remove bignum dependency for scripts
  • Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitmark Core)
  • Upgrade miniupnpc to 1.9.20140701
  • Fix boost detection in build system on some platforms

Sha256Sums

42e717880f0a533aafadea8df08258f9052f4c28812c04f2e98d7efb2d9ad45a  bitmark-0.9.3-linux.tar.gz
9fd4a45b98fd657b218b9e413c7a05ca5ef246db2e90299361dec2ef3ae81c93  bitmark-0.9.3-qt.dmg
ff790b5c624996a656ec1111532f69976873f3fe7388b69c5a685f2e96aa7ddd  bitmark-0.9.3-win32-setup.exe
3e5da03bc46355ddf7bc1e791a220730da823fb506616c887b4f3fafde51d81c  bitmark-0.9.3-win64-setup.exe
4cc7f8575bb95551c040dc6bd3e91ad9debafb0b6d4ea68d9bab3795d6591507  bitmark-0.9.3-win.zip

Bitmark v0.9.2.2 - Rebranding and Security Revision

21 Aug 07:18
Compare
Choose a tag to compare

Overview, Discussion, Info, Logos, Source, Project, Twitter

Features

  • Alerting
  • Rebranded Client
  • Updated Seed Nodes and Checkpoints

A Minor Revision but to be considered a mandatory update

Updating

  • Download
  • Backup your wallet (File > Backup Wallet)
  • Close Bitmark
  • Run the installer / update
  • Open Bitmark

Sha256 Sums

fc58418c9898a61d83e527aeec8181f149ab17c08e645f93e4ff5e0f0ac51f99  bitmark-0.9.2.2-linux.tar.gz
d556cfa298adab753eb529087672dbd26d2587bae8889c9805862d3b5ce1d802  bitmark-0.9.2.2-win.zip
786a89fbd1754c4cb6eee22a5ee82129181b936bf0cec29629401394731b9208  bitmark-0.9.2-win32-setup.exe
27790a6c71fd11846c60ac42c13f596347f3492d4fd0b269741ae59860b48760  bitmark-0.9.2-win64-setup.exe
4e428fcf346339830446c44c4f32a49d8d1d22ceac0e37eefeb1b76a87d3808b  Bitmark-Qt.dmg

Building from source

Instructions for building can be found in the /doc/ section. If you are compiling for linux please be aware that the compilation process is different to most alternative currencies.

If building yourself please consider cloning the master branch of the repository so that you have the latest checkpoints.

Update Often - Miners/Pools/Exchanges
Checkpoints are updated every week before each Tuesday. If you self build please pull from the master branched once every week or two and rebuild to keep our network safe. Thank you.

bitmark text

Bitmark Release

13 Jul 10:48
Compare
Choose a tag to compare

Bitmark Details

Release Details

  • Based on Bitcoin 0.9.2.1 with unconditional support for all upgrades and BIPs which have been implemented.
  • Modified to use the Scrypt Proof of Work
  • Fully tested on all release platforms, and cross compiled using gitian.
  • Modified to use the latest QT 4.8 on linux in order to allow bitmark-qt support on CentOS and Fedora.
  • The genesis block is timestamped to 2014-07-13 18:00:41 UTC. This time was selected by polling the Bitmark community.

Downloads

Pre-compiled 32 and 64bit versions of bitmark-qt, bitmarkd, and bitmark-cli for all major operating systems are attached to this release. SHA256 sums for each download can be found below.

SHA256 Sums

d314892396818ffe049b18ebee3345abe5204a6f6af42fbfecb3a8a7036d03cc  bitmark-0.9.2.1-linux.tar.gz
90d7c4e0946c059f2c1b15a67c2ec86ed40c498a0d91baa95b2d6b097ccfae57  bitmark-0.9.2.1-win.zip
391b9b1d27e27e30fd510fc3ba9ec9b8861f9a8292d60286df3764c1ba37fadb  bitmark-0.9.2-win32-setup.exe
c7fdbb9a5b6561bfa24da49e5fc8de492df462d764aca0cb1affd98afc5ad47d  bitmark-0.9.2-win64-setup.exe
dc6222d67170d60109baf224868fa355401c4ecda6b6ee0d72aed703b04ca1d3  Bitmark-Qt.dmg

Building from source

Instructions for building can be found in the /doc/ section. If you are compiling for linux please be aware that the compilation process is different to most alternative currencies.

If building yourself please consider cloning the master branch of the repository so that you have the latest checkpoints.

Testing

Bitmark passes all of the Bitcoin QA tests, with the exception of the following:

  • miner tests currently fails as we do not have correct test data for a chain of blocks yet, this will be corrected once we have a chain.
  • checkpoint sanity checks also fail, as we have no checkpoints.

Pre-release versions of both of these tests were run before release to ensure the code base passed 100%.

bitmark logo