CNS-868: IPRPC part 1 - IPRPC data implementation #1207
Merged
Conversation
This file contains 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
Yaroms
reviewed
Feb 13, 2024
Yaroms
reviewed
Feb 13, 2024
Yaroms
reviewed
Feb 13, 2024
Yaroms
reviewed
Feb 13, 2024
Yaroms
reviewed
Feb 13, 2024
Yaroms
reviewed
Feb 15, 2024
Yaroms
reviewed
Feb 15, 2024
Yaroms
reviewed
Feb 26, 2024
Base automatically changed from
CNS-866-support-all-denoms-in-pool-methods
to
main
February 28, 2024 12:23
omerlavanet
previously approved these changes
Feb 28, 2024
…t/lava into CNS-868-iprpc-data-implementation
omerlavanet
approved these changes
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
IPRPC relies on two on-chain params: eligible IPRPC subscriptions and minimum IPRPC cost (in ulava).
There is a gov TX (a TX that can only be run using a proposal) to set them and a query to get them.