v0.56.0 #3727
steven-sheehy
started this conversation in
Releases
v0.56.0
#3727
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.
-
This is a big release with support for six different Hedera Improvement Proposals. Most of these changes are on the ingest side of things and future releases will work on adding them to our APIs.
HIP-16 will enable contract expiry and brings a new auto renew account field that contains the account responsible for any renewal fees associated with the contract. The contract REST APIs now show this
auto_renew_account
field along with a newpermanent_removal
flag that is set to true when the system expires a contract.We missed a requirement in our implementation of HIP-329 CREATE2 opcode to allow a HAPI client to do a native transfer of assets to a contract known only by its CREATE2 address. We fixed this logic gap and now support EVM addresses in a
CryptoTransferTransaction
.HIP-336 saw further polish to our allowance support. Support for an optional spender ID parameter on our
/api/v1/accounts/{id}/nfts?spender.id={id}
REST API is now included.HIP-410 brings with it the ability to wrap an Ethereum native transaction and submit it to Hedera. The mirror node can now parse this new
EthereumTransaction
along with the results from its execution. Any contracts created or results and logs generated by its execution will automatically show up on the relevant contract REST APIs. Support for specifying the contract initcode directly on a contract create was also added. To support Externally Owned Accounts (EOA) being able to submit Ethereum transactions, we now calculate and store the EVM address of the account's ECDSA secp256k1 alias. Finally, we added support for repeated topics in contract logs REST API to bring it more inline with theeth_getLogs
JSON-RPC method. If you supply multiple different topic parameters (e.g.topic0
andtopic1
) it is considered anAND
operation as before, but if pass repeated parameters liketopic0=0x01&topic0=0x02&topic1=0x03
it means “(topic 0 is 0x01 or 0x02) and (topic 1 is 0x03)”.HIP-415 is defining a block as the number of records files since stream start (AKA genesis). Since only mirror nodes have a full history, they will be used to provide consensus nodes the current block number to update their state. Since partial mirror nodes with an effective start date after stream start won't have all record files, they may contain an inconsistent value for their block number in contrast to other mirror nodes with all data. This release attempts to correct that with a migration to bring them inline with full mirror nodes so everyone has a consistent block number value.
HIP-423 Long term scheduled transactions enhances the existing scheduled transactions to allow time-based scheduling of transactions. This release adds ingest support for the new schedule-related fields. Next release will expose these fields via our existing schedule REST APIs.
Upgrading
As part of this release, we have finished upgrading our PostgreSQL databases to version 14 and have updated all tests to use that version as well. We recommend mirror node operators plan their migration to PostgreSQL 14 at their earliest convenience. More details on the upgrade process can be found in our database guide.
The migrations in this release are estimated to take up to 2 hours against a mainnet database. However, the migration that takes up the bulk of this time will only run if it needs to correct block numbers. This is only necessary if your mirror node is a partial mirror node and has an effective start date that occurs after the stream start.
Enhancements
Bug Fixes
Documentation
Dependency Upgrades
@hashgraph
/proto from 2.4.0 to 2.4.2 in /hedera-mirror-rest/check-state-proof #3698@hashgraph
/proto from 2.3.0 to 2.4.0 in /hedera-mirror-rest/check-state-proof #3641@hashgraph
/proto from 2.3.0 to 2.4.0 in /hedera-mirror-rest #3638Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.56.0.
Beta Was this translation helpful? Give feedback.
All reactions