v0.66.0 #4634
steven-sheehy
started this conversation in
Releases
v0.66.0
#4634
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Continuing our goal of having up to date balances everywhere, this release now shows the current hbar balance on the balances REST API. If you provide a
timestamp
parameter, it will fallback to the previous behavior and use the 15 minute balance file. This allows us to continue to provide a historical view of your balance over time, while also showing the latest balance if no specific time range is requested. Live fungible token balance is actively being worked on for an upcoming release.Another big feature this release is support for cloud storage failover. The importer can now be configured with multiple S3 download sources and will iterate over each until one is successful. This makes the mirror node more decentralized and provides more resiliency in the face of cloud failure. The existing
hedera.mirror.importer.downloader
properties used to configure thecloudProvider
,accessKey
,secretKey
, etc. will continue to be supported and inserted as the first entry in the sources list, but it's recommended to migrate your configuration to the newer format. Also in the downloader, we increased the downloader batch size to 100 to improve historical synchronization speed. Ahedera.mirror.importer.downloader.sources.connectionTimeout
property was added to avoid occasional connection errors.HIP-573 gives token creators the option to exempt all of their token’s fee collectors from a custom fee. This mirror node release adds support to persist this new
all_collectors_are_exempt
HAPI field and expose it via the/api/v1/tokens/{id}
REST API.An important characteristic of a mirror node is that anyone can run one and store only the data they care about. The mirror node has supported such capability for a few years now but the configuration syntax was a bit tricky to get correct. To address this shortcoming, we add some examples to the configuration documentation to clarify things. This entity filtering was historically limited to just create, update and delete operations on entities. We've now expanded this filtering to include payer account IDs and accounts or tokens involved in transfers.
Breaking Changes
As part of the S3 failover work, we made a number of changes to existing properties to streamline things and only support one property for all stream types. The
hedera.mirror.importer.downloader.(balance|event|record).batchSize
properties were removed in favor of a single, generichedera.mirror.importer.downloader.batchSize
. Likewise, thehedera.mirror.importer.downloader.(balance|event|record).threads
properties were removed in favor ofhedera.mirror.importer.downloader.threads
. Thehedera.mirror.importer.downloader.(balance|event|record).prefix
properties were removed in favor of hardcoded configuration since there's never been a need to adjust these. If you're using any of these properties, please adjust your config accordingly.If you're writing stream files to disk after downloading by enabling the
writeFiles
orwriteSignatures
properties, there is one other breaking change to be aware of. As part of our migration away from node account IDs, we changed the paths on disk to use the node ID as well. If you'd like to avoid having two directories for the same node please rename your local directories manually. For example, change${dataDir}/recordstreams/record0.0.3
to${dataDir}/recordstreams/record0
.Enhancements
Bug Fixes
Documentation
Dependency Upgrades
@hashgraph
/proto from 2.9.0 to 2.10.0 in /hedera-mirror-rest/check-state-proof #4543@hashgraph
/proto from 2.9.0 to 2.10.0 in /hedera-mirror-rest #4539Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.66.0.
Beta Was this translation helpful? Give feedback.
All reactions