Skip to content
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

Backport flag adjustments to mainnet genesis versions #520

Open
troykessler opened this issue Mar 20, 2025 · 2 comments
Open

Backport flag adjustments to mainnet genesis versions #520

troykessler opened this issue Mar 20, 2025 · 2 comments
Assignees

Comments

@troykessler
Copy link

Description and context

KYVE is a decentralized protocol which validates and archives blockchain histories and makes them permanently available for users. In order for the Story cosmos chain to be archived by KYVE some adjustments to the flags had to be made to be compatible with the other cosmos chains which was already implemented in #482 and #518. But since these changes where implemented after Story's mainnet has already been launched KYVE is not able to archive the chain from genesis.

Suggested solution

The solution is to backport these changes to the older versions so KYVE can use them to validate and archive Story's chain history. These changes need to be backported to the Homer upgrade (v1.0.0) and the Virgil upgrade (v1.1.0). This can be done by releasing new patch versions where it is optional to upgrade (v1.0.1 & v1.1.1).

Definition of done

This issue is done once the changes from #482 and #518 have been backported and released to all prior mainnet versions.

@0xHansLee
Copy link
Contributor

I wonder the backported version of Story (v1.0.1) is for a single entity (e.g. KYVE team) or validators providing Story's chain history?

@troykessler
Copy link
Author

I wonder the backported version of Story (v1.0.1) is for a single entity (e.g. KYVE team) or validators providing Story's chain history?

The backported version will be used by every KYVE protocol validator who is validating the Story chain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants