v0.145.1 #12645
steven-sheehy
started this conversation in
Releases
v0.145.1
#12645
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-1261 Simple Fees saw a new REST API added to support estimating network fees. The new
POST/api/v1/network/feesREST API takes as input a serialized Transaction protobuf object in the request body with eitherapplication/protobuforapplication/x-protobufContent-Typeheader and produces a break down of estimated network fees. Not that this API is currently not implemented and just returns dummy data so it should not be used in production. Interested parties can use it to start integrating early so that they're ready for when we integrate the upstream fee estimation library in a future release.The
/api/v1/network/supplyREST API has now been converted to Java. The JavaScript implementation will continue to be the default for a few releases as we work to stabilize and optimize the new implementation. Similarly, the/api/v1/network/feesendpoint was converted to Java and enabled by default in prior releases and is now considered stable. As such, this release removes the legacy JavaScript implementation of the network fees.As forecasted in the blog for HIP-1217, the modularized
/api/v1/contracts/callis now rolled out to all environments. The workaround for allowing calls to long-zero EVM address for accounts that have an ECDSA alias has been disabled in all environments as well. In this release, we make it the default behavior to reject long-zero EVM addresses for accounts with an alias and soon we will be removing the option entirely. Note that the option to reject accounts without sufficient payer balance was not enabled on 12/1 as per the blog. Based upon customer feedback, we will not enable this feature globally and instead enhanced the logic to only conditionally validate payer balance iffromis populated and eithergasPriceorvalueare populated. This behavior is more aligned with how other EVM chains validate payer balances. Finally, we've begun the process of deleting the legacy monolithic code base with it targeted for complete removal by the next release.HIP-1056 Block Streams saw the remaining block stream protobuf changes from consensus node v0.69 addressed. Additionally, the block root hash calculation was updated to use the latest algorithm ensuring support for newer block nodes.
Breaking Changes
As noted above, the
/api/v1/network/feesJavaScript implementation is now removed in favor of the newer Java-based implementation. Operators should ensure their routing logic is updated so that requests to/api/v1/network/feesare directed to the rest-java process instead of the rest process. If operators use our docker compose or Helm chart this routing change is handled automatically.We now set the
hiero.mirror.web3.evm.allowLongZeroAddressesproperty tofalseby default as described in the overview. In a future release, the undocumented property will be removed entirely.The alpha
getFeeEstimategRPC API was removed in favor of the equivalentPOST/api/v1/network/feesREST API. This gRPC API only returned stub data and would not have been used by any one in production.Enhancements
Bug Fixes
Documentation
Dependency Upgrades
@hashgraph/proto from 2.24.0 to 2.25.0 in /rest #12467Deployments
Contributors
Thank you to all the contributors who worked on this release:
@bilyana-gospodinova
@IvanKavaldzhiev
@jnels124
@martingeorgiev1
@sdimitrov9
@steven-sheehy
@xin-hedera
This discussion was created from the release v0.145.1.
Beta Was this translation helpful? Give feedback.
All reactions