Releases: eosrio/hyperion-history-api
Releases · eosrio/hyperion-history-api
v3.3.10-1
What's Changed
- queues will now use CQv2 on RabbitMQ to improve performance, minimum version is RabbitMQ 3.10
- We highly recommend: RabbitMQ 3.13 with Erlang 26
- https://www.rabbitmq.com/blog/2024/01/11/3.13-release
- Minimum Node.js version is set to v20
- node-abieos set to version v3.3.0
- latest updates merged from AntelopeIO upstream
- added the
v2/get_filters
endpoint to display information about the active filters (whitelists/blacklists) - security patches
Full Changelog: v3.3.9-8...v3.3.10-1
v3.3.9-8
Hotfix to prevent large signature counts from overflowing the messaging buffers
v3.3.9-8 should be able to index transactions like: https://wax.bloks.io/transaction/2538659c5e289d9c2be91c46547f175f738c820569621901e08c55b06b7a5bf7
which are not possible to be indexed with previous releases
v3.3.9-7
Full Changelog: v3.3.9-4...v3.3.9-7
v3.3.9-4
- Removed deprecated index mapping, fixes slow startup on large chains
- Fixed v1/history/get_actions output that wasn't including notified actions
- Security patches
Full Changelog: v3.3.9...v3.3.9-4
v3.3.9
What's Changed
- Fixed infinite ETA on monitoring
- Fixed readers stopping before having finished (on v3.3.8-beta only)
- Removed redundant notifications array, since
receipts.receiver
was already indexed - Updated get_action output to include all fields
- Removed unused fields to save raw data storage, for example: if the inline_count = 0 the field will not be present, this applies to other cases like eosio::onblock, where signatures = [] and net_usage_words = 0
- Added
block_id
as a searchable field to get_actions - Added parser module 3.2 as default for the latest Antelope versions, removed deprecated v1.7 parser
- Fastify security updates
- Operational and stability fixes
- get_actions/get_deltas
before
andafter
now support block_num input as well as timestamps
Full Changelog: v3.3.7...v3.3.9
v3.3.8-beta
What's Changed
- Removed redundant notifications array, since
receipts.receiver
was already indexed - Updated get_action output to include all fields
- Removed unused fields to save raw data storage, for example: if the inline_count = 0 the field will not be present, this applies to other cases like eosio::onblock, where signatures = [] and net_usage_words = 0
- Added
block_id
as a searchable field to get_actions - Added parser module 3.2 as default for the latest Antelope versions, removed deprecated v1.7 parser
- Fastify security updates
- Operational and stability fixes
- get_actions/get_deltas
before
andafter
now support block_num input as well as timestamps
Full Changelog: v3.3.7...v3.3.8
v3.3.7-2
What's Changed
- Added api.stream_port param to specify the streaming client dedicated port (defaults to 1234 if empty)
- The new streaming client path is /stream instead of /socket.io, it can be updated on the new client for cross-compatibility https://github.com/eosrio/hyperion-stream-client
- Performance fix on abieos
- Using rewrite:true with an undefined starting block start_on:0 will not trigger reindexing from genesis
- Fixed regression on get_actions affecting some actions that caused the whole call to fail
- Upgraded some deprecated fastify plugins. The full upgrade will be included on the upcoming v3.4 release
Full Changelog: v3.3.6...v3.3.7
v3.3.6-2
What's Changed
- Update fix-missing-blocks.py by @ankh2054 in #126
- fix nested act data on failed node-abieos deserialization
- patch API queries for nested indexed data
- use uWebsockets as socket.io engine to improve throughput and memory usage
Full Changelog: v3.3.6...v3.3.6-2
v3.3.6
Tagged release based on the v3.3.5 branch that is now merged into main/master
- Included new data on v2/health endpoint to support validation of partial history providers
- head_offset calulates the difference between the head_block from Leap/NodeosRPC and the last block on ES
- first_indexed_block cache is removed at the indexer startup and re-cached on the first api call, no need to check on every call since the value should not change
- missing_blocks is calculated only for the intended range and not the full chain
- Add errors to each token on v2/state/get_tokens if their balance failed to be retrieved