Skip to content

Releases: nimiq/core-js

v1.6.2

14 Sep 01:02
v1.6.2
fb3238c
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.6.1...v1.6.2

v1.6.1

14 Mar 00:27
v1.6.1
b7fba25
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.6.0...v1.6.1

v1.6.0

05 Nov 00:35
v1.6.0
7035440
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.5.8...v1.6.0

v1.5.8

25 Oct 00:46
v1.5.8
ac75c46
Compare
Choose a tag to compare

What's Changed

  • Bump node-fetch from 2.6.0 to 2.6.1 by @dependabot in #571
  • Bump http-proxy from 1.18.0 to 1.18.1 by @dependabot in #570
  • Client: Correct number of confirmations reported when a tx gets confirmed by @sisou in #567
  • Bump codecov from 3.6.5 to 3.7.1 by @dependabot in #563
  • Bump elliptic from 6.5.2 to 6.5.3 by @dependabot in #564
  • Bump lodash from 4.17.15 to 4.17.19 by @dependabot in #562
  • Fix HTLC conversion to and from plain format by @sisou in #568
  • Fix type errors in types.d.ts definition file (and in code by extension) by @sisou in #569
  • Include BasicAccount and contracts into offline build by @sisou in #572
  • Specify result types of HTLC.proofToPlain() method by @sisou in #574
  • Support for Node 14, the new LTS release by @sisou in #573
  • Transaction proof should be described based on sender account type, not recipient by @mar-v-in in #575
  • Bump socket.io from 2.3.0 to 2.4.1 by @dependabot in #579
  • Bump ini from 1.3.5 to 1.3.8 by @dependabot in #580
  • Disable broken test and increase timeout of another by @jeffesquivels in #582
  • Remove seed4 from testnet config as it's decomissioned by @jeffesquivels in #581

Full Changelog: v1.5.7...v1.5.8

v1.5.4

27 Jan 21:14
v1.5.4
f7bab29
Compare
Choose a tag to compare

Changelog

  • Added support for SSL certificate hot reloading.
  • Fixed a bug that caused certain peer address queries to return incomplete results.
  • Fixed a mempool inconsistency issue (thanks @tomkha).
  • Fixed a Client issue related to pending transaction handling.
  • Fixed a number of minor JSON-RPC issues.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.

v1.5.0

16 Aug 10:54
v1.5.0
9a137f2
Compare
Choose a tag to compare

Changelog

  • Introduced pico consensus mode, an optimistic extension for nano mode, which dramatically reduces sync time.
  • Introduced high-level Client API to simplify use of the core-js library.
  • Added support for multiple reverse proxy addresses.
  • Improved robustness of WebRTC connection setup.
  • Improved signaling of services supported by a node.
  • Fixed a connection cleanup issue which caused high CPU load in browser clients.
  • Fixed a bug that caused pool clients to not accept all settings after initial connect.
  • Rotated the release package signing key.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.

v1.4.3

15 Feb 18:42
v1.4.3
1ea5cee
Compare
Choose a tag to compare

Changelog

  • Fixed a bug that caused the nano pool client to parse pool messages incorrectly.
  • Fixed ES6 module loading.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.

v1.4.2

12 Feb 16:15
v1.4.2
9fdf745
Compare
Choose a tag to compare

Changelog

  • Added mempool spam filters, learn more here.
  • Added support for ImageWallet key format.
  • Improved responsiveness of nano client during sync.
  • Fixed a bug that caused the nano miner to stop working under certain conditions.
  • Fixed a number of minor JSON-RPC issues.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.

v1.4.1

05 Dec 02:08
v1.4.1
8680aa6
Compare
Choose a tag to compare

Changelog

  • Added dedicated npm package for Nimiq browser applications.
  • Added user agent string to network handshake.
  • Improved mining performance for CPUs with AVX support.
  • Improved CPU architecture detection and native add-on selection.
  • Fixed an issue when sending transactions with nano clients via JSON-RPC.
  • Fixed display of certain balances in remote client.
  • Fixed a memory issue with long-running HTTP requests.
  • Reduced number of external library dependencies.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.

v1.4.0

13 Nov 18:03
v1.4.0
429d2f0
Compare
Choose a tag to compare

Changelog

  • Added CPU architecture detection for optimal mining performance (thanks @terorie).
  • Added a warning if the local system time is incorrect (thanks @Beeppool).
  • Added new JSON-RPC features:
    • Support for external miner implementations (getWork / getBlockTemplate).
    • Support for transaction flags in createRawTransaction (thanks @jgraef).
  • Fixed an issue with fragmented database files on Windows.
  • Fixed display of mempool contents in JSON-RPC client.
  • Improved miner performance when assembling blocks.

Instructions

  • Debian/Fedora users can update & upgrade.
  • Windows users need to uninstall and reinstall. This doesn't erase your account information but you can create a backup of %LocalAppData%\Nimiq to be sure.
  • Pool operators should make sure their users upgrade as well.