2.4.0

Performance Improvements

• Use CW-N's new block endpoint for history fill operations (#162)

Bug Fixes

• Fix treatment of events associated to multiple transactions returned by the txs/txs endpoint (#177)

Codebase Improvements

• Update Haskell dependencies and GHC version (to 9.2.8) (#172, #174, #176)
• Nix build setup improvements (#170)
• Build with Nix and cache (to nixcache.chainweb.com) the project in GitHub actions (#165)
• README improvements (#168, #169, 178)
• Cabal build GitHub action fix (#166)
• Fix the hie.yaml for HLS (Haskell LSP) (#175, #179)

Nix Store Paths

x86_64-linux: /nix/store/d2qh91p0fv8bmcs1paajhr6vjh7bbqa1-chainweb-data-exe-chainweb-data-2.4.0
x86_64-darwin: /nix/store/a7035d7dddmvkjn7vrr6j0gdfbv19bih-chainweb-data-exe-chainweb-data-2.4.0
aarch64-darwin: /nix/store/frn36wncy4vkz3lnhdh9alpnmssr0scj-chainweb-data-exe-chainweb-data-2.4.0

New Contributors

• @DevopsGoth made their first contribution in #166
• @trendzetter made their first contribution in #168
• @edmundnoble made their first contribution in #162

Full Changelog: v2.3.0...v2.4.0

2.3.0

New Features

• Decouple chainweb-data from the P2P API of chainweb-node, using the service endpoint exclusively instead. The --p2p-{host,post} CLI arguments are no longer needed, but are still recognized for backwards compatibility (#160)
• Enable running the HTTP API without the ETL, allowing read-only operation (#149)
• Attach signer and signature information to TxDetail endpoints (/txs/{tx,txs}) (#152, #153, #155)
• Extend network metadata to allow ETL'ing from (fast-)development nodes (#158)
• Add --extra-migrations-folder CLI argument (#163)

Bug Fixes

• Fix fill and backfill issues caused by node's P2P API throttling, resulting in partial fills (#151)

Minor

• #156, #157, #159

Nix Store Path

/nix/store/ykjk6pvb59npj2i4nynfg3qm9qzkfwx7-chainweb-data-exe-chainweb-data-2.3.0/

New Contributors

• @mbwmbw1337 made their first contribution in #155

Full Changelog: v2.2.0...v2.3.0

2.2.0

Notes

• This release completes the transition from beam-automigrate to the new incremental migration scripts (See Issue #101). If you're upgrading from a version earlier than 2.1.X, you'll first have to run CW-D v2.1.1 to migrate your database to a state that's compatible with the new script based migrations.

• After this version, the transactionCount field of the /stats endpoint becomes an estimate rather than an exact count. This change allowed us to decouple the ETL process from the HTTP server and fixed a long-standing resource accumulation issue.

New Features

• Enable searching by pactid in the /txs/search endpoint (#143)
• Include continuation transaction rows in the /txs/search resullt if their original transaction satisfies the search criteria (#66)
• Extend the /txs/account endpoint response with cross-chain information in the case of cross-chain transfers (#137, #138)
• Add minheight, maxheight query parameters to all transaction search enpoints (/txs/{events,account,search}) (#135)

Performance Improvements

• Remove the mutable server state and decouple the ETL from the HTTP server (#148)

Codebase Improvements

• Add support for Nix flakes (#132, #133, #134, #136)
• Simplify the handling of the recentTxs (#140)
• Update maintainers list (#131)

Nix Store Path

/nix/store/n1jhsy0psl4ljf5pmwxsnxnzsgdxs5k3-chainweb-data-exe-chainweb-data-2.2.0

2.1.1

BREAKING CHANGE: Shortly after the 2.1.0 release, we've noticed an oversight in the new /txs/account endpoint and decided to correct it with a quick breaking change instead of unnecessarily complicating the API. The following fields of the new /txs/account endpoint has been renamed: chainid -> chain, name -> token See #126

Other Changes

• A new minheight parameter for /txs/accounts (#127)
• A docker.nix definition for building Ubuntu-based chainweb-data docker images using Nix (#84)

Nix Store Path

Linux: /nix/store/frb2w22yj5a7bqcrkv1djl3z9vwsjca6-chainweb-data-2.1.1

2.1.0

Notes

• This release drops the officiall support for Ubuntu 18.04 and adds support for Ubuntu 22.04 (see #100)
• This is the last version that uses beam-automigrate for managing the database schema, from this version on, we'll switch to managing the schema using incremental migration scripts (see #101, #102, #104). When future versions of chainweb-data need to migrate the database from a version earlier than 2.1.0, they will ask the user to first run 2.1.0 to prepare their database for incremental migrations.

New Features

• A new /txs/account endpoint for fetching the incoming and outgoing transfers of a Kadena or non-Kadena account. #76 (also #83, #96, #103, #110, #114, #117, #124, #125)
• All search endpoints (/txs/{account,events,search}) now support an optional (at the discretion of the HTTP gateway) "bounded execution" workflow (#109, also #118, #121)
• The event search endpoint /txs/event now accepts 2 new arguments to narrow down the search results (#74):
  • modulename: Narrows down the search to events whose modules names match this value exactly
  • minheight: The minimum block height of the search window
• A hidden new --serve-swagger-ui CLI argument that can be passed to chainweb-data to make it serve a Swagger UI for an auto-generated OpenAPI 3 spec for the chainweb-data HTTP API. The CLI argument is hidden because this spec is rudimentary and unofficial at the time of this release. Future releases will improve it.
• A new --ignore-schema-diff CLI argument to chainweb-data to make it ignore any unexpected database schema changes. This can be used by chainweb-data operators to make schema changes to their database and keep running chainweb-data, but such ad-hoc database schema changes are not officially supported since they can cause a wide variety of errors under unpredictable conditions.
• A new migrate command for the chainweb-data CLI that can be used to run the database migrations and exit.
• A new /txs/txs endpoint similar to /txs/tx, but it returns a list of TxDetail objects, which can contain more than one entry when a transaction is introduced multiple times into the blockchain on independent branches. #71 #72

Performance improvements

• Code search and event search query optimization (#67)
• Add requestkey indexes on events and transactions tables (#98)
• Refactor richlist generation (#89)
• Load-based throttling for search endpoints (#116)
• Optimize the recent transactions query at server start up (#119)
• Set random_page_cost to 0 for CW-D connections #122

Bug fixes

• Coin circulation calculation fix #97

Minor

• 9eddd3f
• 297e4f1
• #78
• #85
• #87
• #99
• #105
• #108
• #107 (obsoleted and reverted by #109)

Nix Store Path

Linux: /nix/store/6ycpir4fqa5sskq097friw35781xwwkw-chainweb-data-2.1.0

2.0.0

This is a major backwards-incompatible update. All chainweb-data users need to delete their DB and rebuild from scratch. Major changes include:

• DB fills in several hours instead of several days
• New command fill replaces the old backfill and gaps commands (which still exist but will be removed in a future release)
• The server command now has a -f option which will run fill once a day to fill any gaps in the block data
• New tables for events and transaction signers
• Standardized to storing base64url values with no padding (i.e. the '=' at the end)
• Fixed a bug where parent block hashes were stored instead of the block hash
• Much faster calculation of coins in circulation

1.2.0

Support split between node service and p2p APIs, other misc improvements.

1.1.0

Changed

The transactions table now stores the entire PayloadWithOutputs structure,
not just the smaller Payload.

1.0.0

Initial release.