Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.

Release 66

Compare
Choose a tag to compare
@oliverw oliverw released this 03 Jan 13:47
· 345 commits to master since this release
f5a7f1a

Breaking Changes

  • You must update your config.json and change the value of the manager property inside the banning element. Old: "manager": "integrated", new "manager": "Integrated" (the old value was lower-case, the new value is capitalized)

Changes

  • Completely removed the built-in 0.1% Dev-Donation
  • Improved Ethereum Sync status reporting
  • Implement Ethereum Stratum Protocol v1 (both Ethereum Stratum Protocol Versions are supported on the same port simultaneously)
  • Support for Raptoreum (RTM)
  • Added support for TLS auto detection. In effect it is now possible to support both SSL (TLS) and non-SSL connection on the same port and the pool will auto-detect incoming SSL connections. (Stratum Port Config Option: tlsAuto: true)
  • Added JSON Schema for config.json and load-time-validation for improved error reporting. To enable editor support add the following after the first "{" in your config.json: "$schema": "https://raw.githubusercontent.com/oliverw/miningcore/master/src/Miningcore/config.schema.json", as shown here.
  • Added build-scripts for Linux and Windows
  • Implemented new hash algorithms:
    • Ghostrider
    • Heavyhash
    • HMQ17
    • Sha256Csm
    • X16R V2
  • Implemented Cryptonight hash algorithms and their respective sub-variants:
    • Argon
    • Cryptonight Heavy
    • Cryptonight Lite
    • Cryptonight Pico
  • Upgraded librandomx to v1.1.10
  • Extended Coin metadata support which is also exposed by the API
    • Website
    • Twitter
    • Discord
    • Telegram
  • Consolidate timestamp column types to timestamptz in database schema to be compatible with npgsql 6.0 and higher
  • Update for npgsql 6.0 legacy timestamps (without time zone) with automatic runtime detection

Recommended but not required Database Migrations

These migrations are only meant for existing pools. You don't have to apply them when setting up a new pool as those changes are already applied to the initial database schema.

ALTER TABLE shares ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE blocks ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE balances ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE balances ALTER COLUMN updated TYPE TIMESTAMPTZ;
ALTER TABLE balance_changes ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE miner_settings ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE miner_settings ALTER COLUMN updated TYPE TIMESTAMPTZ;
ALTER TABLE payments ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE poolstats ALTER COLUMN lastnetworkblocktime TYPE TIMESTAMPTZ;
ALTER TABLE poolstats ALTER COLUMN created TYPE TIMESTAMPTZ;
ALTER TABLE minerstats ALTER COLUMN created TYPE TIMESTAMPTZ;

DROP INDEX IDX_POOLSTATS_POOL_CREATED_HOUR;
DROP INDEX IDX_MINERSTATS_POOL_MINER_CREATED_HOUR;
DROP INDEX IDX_MINERSTATS_POOL_MINER_CREATED_DAY;