Wallet lib v7.15.0-dev.4

chore: bump version to 7.15.0-dev.4 (#182)

Wallet lib v7.15.0-dev.3

chore(release): bump version to 7.15.0-dev.3

Wallet lib v7.15.0-dev.2

chore: bump version to 7.15.0-dev.2 (#176)

Wallet lib v7.15.0-dev.1

chore: bump version to 7.15.0-dev.1 (#173)

Wallet lib v7.14.0

Bug Fixes

• merge conflict artefact issue (#170)
• outdated network option values (#167)

Features

• run tests against mn-bootstrap instead of devnet (#168)
• update to DAPI Client 0.14 and refactor transport layer (#163)

Documentation

• readme standard updates (#165)
• update documentation and definitions files (#154)

BREAKING CHANGES

• transporter option is replaced with transport that accepts DAPI Client options or a Transport instance.

Wallet lib v7.14.0-dev.2

chore: bump version to 7.14.0-dev.2 (#169)

Wallet lib v7.14.0-dev.1

feat!: update to DAPI Client 0.14 and refactor transport layer (#163)

BREAKING CHANGE: `transporter` option is replaced with `transport` that accepts DAPI Client options or a Transport instance.

Wallet lib v7.13.4

Bug Fixes

• simple transaction do not have any 4 inputs limitation (#158)
• account: forward all storage events (#159)

Features

• update dashcore-lib and DAPI Client (#161)

Wallet lib v7.13.3

7.13.3 (2020-06-16)

Notable Changes:

• Fixes:

  • fix!: createTransaction should be checking for 'recipient' instead of 'address' in 'txOpts.recipients' (#152)
  • fix: transaction hash not present on address (#151)

• Breaking changes:

  • Previously, the documentation stated a usage on createTransaction() with multiples recipients as such: recipients:[{recipient,satoshis}].
    However, the code where still referring and expecting recipients recipients:[{address,satoshis}].
    This version fixes that inconsistency.

Wallet lib v7.13.2

7.13.2 (2020-06-15)

Notable Changes:

• Features:

  • feature: Worker will now have ability to return a value on onStart and onExecute (#149)

• Fixes:

  • fix: comportement on new address with existing transaction in store (#147)
  • fix: SyncUp plugin not awaiting long enough (#149)