Skip to content

Releases: ltonetwork/indexer

v1.4.3 - DID resolution

22 Jul 06:01
e20bf89
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.4.2...v1.4.3

v1.4.2

24 May 15:17
ed9f954
Compare
Choose a tag to compare
v1.4.2 Pre-release
Pre-release

What's Changed

  • Specify sender when verifying anchors by @jasny in #192

Full Changelog: v1.4.1...v1.4.2

v1.4.1

15 May 20:53
f001abd
Compare
Choose a tag to compare
v1.4.1 Pre-release
Pre-release

Full Changelog: v1.4.0...v1.4.1

v1.4.0 - Titanium

07 Nov 11:22
67e54e3
Compare
Choose a tag to compare
v1.4.0 - Titanium Pre-release
Pre-release

What's Changed

Full Changelog: v1.3.3...v1.4.0

v1.3.3

07 Oct 00:50
795bf20
Compare
Choose a tag to compare

What's Changed

Updated libraries

Full Changelog: v1.3.2...v1.3.3

v1.3.2

27 Sep 14:36
0e47c53
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.1...v1.3.2

v1.3.1

20 Sep 18:19
28dedce
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.0...v1.3.1

v1.3.0

22 Jul 11:55
1cc5c61
Compare
Choose a tag to compare

What's Changed

  • [#116] Adding support for cross chain DIDs by @brunodb3 in #150
  • Ability to batch hash requests into a single anchor tx by @jasny in #160

Full Changelog: v1.2.1...v1.3.0

v1.2.1

18 Jan 22:38
eb71efd
Compare
Choose a tag to compare

This release fixes some performance issues by optimizing the /wallet/addresses call to the public node. See related PR.


  • Optimizes the getNodeWallet() call to reduce the amount of times this call is made
    • On AWS at least, this call is made a lot of times, and it often results in a ECONNRESET error. With this optimization, at least that call is reduced, freeing up some resources instead of blocking the application. The ECONNRESET error might still happen, but at least it won't happen as often and clog up resources.

v1.2.0

06 Dec 12:23
d48bd1c
Compare
Choose a tag to compare

This release fixes the bug found on #139 (PR #140)


  • Fixes the issue with /transactions/addresses endpoint
    • The indexing was not behaving properly due to an error implementing AwaitLock
    • AwaitLock was getting stuck when multiple listeners were activated, so the data was never saved to the database
  • Fixes/moves leveldb connection handling of errors on .get method
    • Instead of throwing an error when value is not found, returns an empty list. This was done on the leveldb.service previously, but a better place is on the leveldb.connection, as it covers more use-cases
  • Some identation and linting fixes