This is a quick release after 2.1.0 for fixing an oversight in the new /txs/accounts
endpoint.
- Rename
chainid
->chain
,name
->token
fields of/txs/accounts
for consistency (#126) - A new
minheight
parameter for/txs/accounts
(#127) - A
docker.nix
definition for building Ubuntu-basedchainweb-data
docker images using Nix (#84)
IMPORTANT NOTICE: Please skip this chainweb-data release and go straight to 2.1.1. Shortly after the 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. See PR #126.
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.
- 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) - 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 exactlyminheight
: The minimum block height of the search window
- A hidden new
--serve-swagger-ui
CLI argument that can be passed tochainweb-data
to make it serve a Swagger UI for an auto-generated OpenAPI 3 spec for thechainweb-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 tochainweb-data
to make it ignore any unexpected database schema changes. This can be used bychainweb-data
operators to make schema changes to their database and keep runningchainweb-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 thechainweb-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 ofTxDetail
objects, which can contain more than one entry when a transaction is introduced multiple times into the blockchain on independent branches. #71 #72 - Code search and event search query optimization (#67)
- Add requestkey indexes on
events
andtransactions
tables (#98) - Refactor richlist generation (#89)
- Load-based throttling for search endpoints (#116)
- Optimize the recent transactions query at server start up (#119)
- Coin circulation calculation fix #97
- Set random_page_cost to 0 for CW-D connections #122
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 oldbackfill
andgaps
commands - The
server
command now has a-f
option which will runfill
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
Adds events
table and provides the following new queries/endpoints:
tx
which is a "tx detail" search by request key returning a single result, with full eventsevents
which is an event search supporting the following params (along with limit and offset):param
for param text wildcard searchrequestkey
for exact request key searchname
for event name wildcard search (e.g. "TRANSFER")idx
for exact event idx search (meaningless withoutrequestKey
but oh well)
- Added support for chainweb-node's new separated P2P and Service APIs being served on separate ports.
- Added ability to rate limit the
gaps
andbackfill
commands with a--delay
commandline option.
- The
transactions
table now stores the entirePayloadWithOutputs
structure, not just the smallerPayload
.
Initial release.