-
Notifications
You must be signed in to change notification settings - Fork 636
Cosmos SDK: provide an API for accessing state
and store
#2610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
thank you, let us know if we can help |
+1 |
This was referenced Mar 22, 2024
@melekes any update on this guy? |
gentle ping, we cant move forward with comet integration in the sdk for the next release. If there is an expected timeline it would be good to know so we can share with ibc, cosmwasm, and other teams waiting on the release |
This was referenced Apr 3, 2024
This was
linked to
pull requests
Apr 4, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 16, 2024
…2709) This partly undoes the changes in #1605 by re-exporting the store/ package. Closes #2610 Paging @tac0turtle to check if this can help Cosmos SDK continue migration to Comet v1 --- #### PR checklist - [ ] ~~Tests written/updated~~ - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] ~~Updated relevant documentation (`docs/` or `spec/`) and code comments~~ - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec --------- Co-authored-by: Andy Nogueira <me@andynogueira.dev> Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com>
mergify bot
pushed a commit
that referenced
this issue
Apr 16, 2024
…2709) This partly undoes the changes in #1605 by re-exporting the store/ package. Closes #2610 Paging @tac0turtle to check if this can help Cosmos SDK continue migration to Comet v1 --- #### PR checklist - [ ] ~~Tests written/updated~~ - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] ~~Updated relevant documentation (`docs/` or `spec/`) and code comments~~ - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec --------- Co-authored-by: Andy Nogueira <me@andynogueira.dev> Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com> (cherry picked from commit 7d230d7)
4 tasks
melekes
pushed a commit
that referenced
this issue
Apr 16, 2024
…ackport #2709) (#2821) This partly undoes the changes in #1605 by re-exporting the store/ package. Closes #2610 Paging @tac0turtle to check if this can help Cosmos SDK continue migration to Comet v1 --- #### PR checklist - [ ] ~~Tests written/updated~~ - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] ~~Updated relevant documentation (`docs/` or `spec/`) and code comments~~ - [x] Title follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec <hr>This is an automatic backport of pull request #2709 done by [Mergify](https://mergify.com). Co-authored-by: Adi Seredinschi <adizere@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Summary
The latest version of Cosmos SDK imports
state
andstore
packages (which in v1 are internal, meaning can't be imported outside of CometBFT).Problem Definition
Previously, the way to test something on a testnet for a single validator was by modifying the
genesis.json
file and skipping blocksync as indicated in #1679. A new solution was developed because exportinggenesis.json
can take minutes and requires lots of RAM. Instead of modifying thegenesis.json
file, Cosmos SDK directly modifies the chain's state and updates the store: https://github.com/cosmos/cosmos-sdk/blob/main/server/start.go#L729. For that, it needs access tostate
andstore
packages, which are currently internal.Proposal
Either create a subset of API needed for ^ or completely reexport
state
andstore
packages.The text was updated successfully, but these errors were encountered: