v0.57.0 #3841
steven-sheehy
started this conversation in
Releases
v0.57.0
#3841
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 release is focused on adding the necessary data and APIs needed for the JSON-RPC Relay defined in HIP-482. The JSON-RPC Relay implements the Ethereum JSON-RPC standard and relays HIP-410 Ethereum transactions to consensus nodes. Since the concept of a block is crucial for JSON-RPC APIs, this release also contains the implementation of HIP-415 Introduction of Blocks.
The mirror node now exposes the concept of blocks as introduced in HIP-415. We now calculate and store the cumulative gas used and the contract log bloom filter for the block as a whole. This HIP defines three new REST APIs and this release includes all three: a list blocks REST API, a get blocks REST API, and a list contract results REST API. The new
/api/v1/blocksAPI supports the usuallimitandorderquery parameters along withtimestampandblock.numberto support equality and range operators for consensus timestamps and block numbers, respectively. The/api/v1/blocks/{hashOrNumber}is identical to the list blocks but only returns a single block by either its block hash or its block number. Finally, a/api/v1/contracts/resultsREST API was added that is identical to the existing/api/v1/contracts/{id}/resultsbut able to search across contracts.GET /api/v1/blocks{ "blocks": [{ "count": 4, "gas_limit": 150000000, "gas_used": 50000000, "hapi_version": "0.24.0", "hash": "0xa4ef824cd63a325586bfe1a66396424cd33499f895db2ce2292996e2fc5667a69d83a48f3883f2acab0edfb6bfeb23c4", "logs_bloom": "0x549358c4c2e573e02410ef7b5a5ffa5f36dd7398", "name": "2022-04-07T16_59_23.159846673Z.rcd", "number": 19533336, "previous_hash": "0x4fbcefec4d07c60364ac42286d5dd989bc09c57acc7370b46fa8860de4b8721e63a5ed46addf1564e4f8cd7b956a5afa", "size": 8489, "timestamp": { "from": "1649350763.159846673", "to": "1649350763.382130000" } }], "links": { "next": null } }GET /api/v1/blocks/{hashOrNumber}{ "count": 4, "gas_limit": 150000000, "gas_used": 50000000, "hapi_version": "0.24.0", "hash": "0xa4ef824cd63a325586bfe1a66396424cd33499f895db2ce2292996e2fc5667a69d83a48f3883f2acab0edfb6bfeb23c4", "logs_bloom": "0x549358c4c2e573e02410ef7b5a5ffa5f36dd7398", "name": "2022-04-07T16_59_23.159846673Z.rcd", "number": 19533336, "previous_hash": "0x4fbcefec4d07c60364ac42286d5dd989bc09c57acc7370b46fa8860de4b8721e63a5ed46addf1564e4f8cd7b956a5afa", "size": 8489, "timestamp": { "from": "1649350763.159846673" "to": "1649350763.382130000" } }A number of changes were made in support of HIP-410 Ethereum Transactions. The
/api/v1/accounts/{idOrAlias}REST API was updated to accept an EVM address as a path parameter in lieu of an ID or alias. Anethereum_nonceandevm_addresswas added to the response of/api/v1/accounts/{idOrAliasOrAddress}and/api/v1/accounts. The existing/api/v1/contracts/results/{transactionId}was updated to accept the 32 byte Ethereum transaction hash as a path parameter in addition to the transaction ID that it supports now. Its response, as well as the similar/api/v1/contracts/{idOrAddress}/results/{timestamp}, was updated to add the following new Ethereum transaction fields:{ "access_list": "0xabcd...", "block_gas_used": 564684, "chain_id": "0x0127", "gas_price": "0xabcd...", "max_fee_per_gas": "0xabcd...", "max_priority_fee_per_gas": "0xabcd...", "nonce": 1, "r": "0x84f0...", "s": "0x5e03...", "transaction_index": 1, "type": 2, "v": 0 }Note: Existing fields omitted for brevity.
A new exchange rate REST API
/api/v1/network/exchangeratewas added that returns the exchange rate network file stored in0.0.112. It supports atimestampparameter to retrieve the exchange rate at a certain time in the past.{ "current_rate": { "cent_equivalent": 596987 "expiration_time": 1649689200 "hbar_equivalent": 30000 }, "next_rate": { "cent_equivalent": 594920 "expiration_time": 1649692800 "hbar_equivalent": 30000 }, "timestamp": "1649689200.123456789" }A new
/api/v1/contracts/results/logsAPI was added with the same query parameters and response as/api/v1/contracts/{address}/results/logsbut with the ability to search across contracts. It does not support address as a query parameter as it’s expected users use the existing API if they need logs for a specific address. The same rules around not exceedingmaxTimestampRangestill applies and allows it to stay performant. Pagination is possible using a combination of the timestamp and index query parameters.Finally, this releases completes our implementation of HIP-423 Long Term Scheduled Transactions. Two new fields
wait_for_expiryandexpiration_timewere added to/api/v1/schedulesand/api/v1/schedules/{id}.Enhancements
Bug Fixes
Dependency Upgrades
@hashgraph/proto from 2.4.0 to 2.4.2 in /hedera-mirror-rest #3714Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.57.0.
Beta Was this translation helpful? Give feedback.
All reactions