feat(api): expose minimumValidityBlocks in /chainstate#5465
Merged
Conversation
martinconic
requested review from
acud,
akrem-chabchoub,
gacevicljubisa,
janos and
sbackend123
and removed request for
akrem-chabchoub
akrem-chabchoub
approved these changes
May 19, 2026
gacevicljubisa
approved these changes
May 25, 2026
sbackend123
approved these changes
May 25, 2026
janos
approved these changes
May 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
Description
Closes #4922.
Extends
GET /chainstatewith aminimumValidityBlocksfield — thepostage stamp contract constant that defines the minimum number of
blocks a newly purchased batch must remain valid. With this, clients
have every input needed for stamp duration / cost calculations in a
single endpoint, without having to hit the Gnosis RPC and decode the
contract themselves.
Open API Spec Version Changes (if applicable)
Motivation and Context (Optional)
Related Issue (Optional)
Screenshots (if appropriate):
AI Disclosure