v0.54.0 #3567
steven-sheehy
started this conversation in
Releases
v0.54.0
#3567
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This release adds support for three new REST APIs and four HIPs.
HIP-21 describes the need for a free network info query to enable SDKs and other clients to be able to retrieve the current list of nodes. In v0.49.1, we added a new
NetworkService.getNodes()
gRPC API. In this release, we're adding an equivalent address book API to our REST API. In addition to the standardorder
andlimit
parameters, it supports afile.id
query parameter to filter by the two address books0.0.101
or0.0.102
and anode.id
query parameter to filter nodes and provide pagination.GET /api/v1/network/nodes
HIP-336 describes new Hedera APIs to approve and exercise allowances to a delegate account. An allowance grants a spender the right to transfer a predetermined amount of the payer's hbars or tokens to another account of the spender's choice. In v0.50.0 we added database support to store the new allowance transactions. In this release, two new REST APIs were created to expose the hbar and fungible token allowances. Full allowance support won't be available until a future release when consensus nodes enable it on mainnet.
GET /api/v1/accounts/{accountId}/allowances/crypto
GET /api/v1/accounts/{accountId}/allowances/tokens
Also on the REST API, we added support for HIP-329 CREATE2 addresses. Now any API that accepts a contract ID will also accept the 20-byte EVM address as a hex-encoded string. We improved the performance of the REST API by adding cache control headers to enable distributed caching via a CDN. The performance of the list transactions by type REST API saw a fix to improve its performance.
As part of HIP-260, contract precompile call data now populates new fields
amount
,gas
, andfunction_parameter
insideContractFunctionResult
within theTransactionRecord
. Mirror node now stores these fields and exposes them via its existing contract results REST APIs.There were a number of security improvements made to containerized mirror nodes. All Docker images now run as non-root regardless of running in Kubernetes or Docker Compose. The helm charts saw changes to conform to the Kubernetes restricted pod security standard. This ensures the mirror node runs with security best practices and reduces its overall attack surface. The Kubernetes Pod Security Standard replaces the deprecated PodSecurityPolicy and as such we've removed all configuration related to the latter.
Upgrading
This release has a long migration that is expected to take around 25 minutes to complete. As always, we recommend a red/black deployment to eliminate downtime during migrations. If you're using the
hedera-mirror-common
chart, please check the kube-prometheus-stack upgrade notes to ensure Prometheus Operator can update successfully.Enhancements
Bug Fixes
Dependency Upgrades
@hashgraph
/proto from 2.1.5 to 2.2.0 in /hedera-mirror-rest #3465@hashgraph
/proto from 2.1.5 to 2.2.0 in /hedera-mirror-rest/check-state-proof #3462Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.54.0.
Beta Was this translation helpful? Give feedback.
All reactions