v0.48.0 #3142
steven-sheehy
started this conversation in
Releases
v0.48.0
#3142
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
HIP-206 adds a parent consensus timestamp to the transaction record for internal transactions that occur like HTS precompiles invoked from a smart contract. To round out the
nonce
support in the last release we addedparent_consensus_timestamp
to/api/v1/accounts/{id}
and/api/v1/transactions
. This field helps define the parent/child relationships between transactions.HIP-226 describes the recently added contract results REST API. Each release we've been iterating and adding more functionality to the API until it matches the description in the HIP. This release adds the list of logs generated by a smart contract execution. Here's a sample of the new JSON response:
In the last release we added a new Web3 JSON-RPC API. With this release we've added a
hedera-mirror-web3
Helm chart that can be used to deploy it on Kubernetes. Additional metrics were added to the Java module and a new Grafana dashboard was created to visualize them. The Web3 API was also added to the docker-compose file.Upgrading
If you're upgrading an existing deployment of our Helm chart, there are a few breaking changes to keep in mind. First, we deploy the new Web3 API chart by default and it requires a
mirror_web3
database user exist with read permission. Please create the new database user before upgrading or you can disable thehedera-mirror-web3
sub-chart.We've upgraded the
PodDisruptionBudget
resources frompolicy/v1beta1
topolicy/v1
and as a result now require Kubernetes 1.21 or greater. For thehedera-mirror
chart, if you're using the optionalpostgresql
sub-chart you must scale the PostgreSQL replicas down to one before initiating an upgrade in order to upgrade repmgr.If you're using the
hedera-mirror-common
chart, there are a number of breaking changes in the community sub-charts it uses. Before upgrading, you will need to delete theprometheus-adapter
andkube-state-metrics
deployments. You'll also need to reinstall a few custom resource definitions. Run the below commands to do so:Enhancements
Bug Fixes
/tokens/:id/nfts/:serialNumber/transactions
is slow #2792Dependency Upgrades
Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.48.0.
Beta Was this translation helpful? Give feedback.
All reactions