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.

Sign up for GitHub

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

Jump to bottom

Allow users to specify ProofSpecs for non-SDK chains #67

Closed
5 tasks
hu55a1n1 opened this issue Nov 10, 2021 · 0 comments · Fixed by informalsystems/hermes#1574
Closed
5 tasks

Allow users to specify ProofSpecs for non-SDK chains #67

hu55a1n1 opened this issue Nov 10, 2021 · 0 comments · Fixed by informalsystems/hermes#1574
Assignees
@hu55a1n1

Comments

@hu55a1n1
Copy link
Contributor

Crate

ibc

Summary

Currently, we use the Cosmos SDK ProofSpecs definition for all Tendermint chains. We should allow users to specify the ProofSpecs for non-SDK chains.

Proposal

We maybe add a config option [[chains]].proof_spec that takes a file/text with a serialized (JSON?) ProofSpec definition.

Acceptance Criteria

Users are able to specify a custom ProofSpecs for non-SDK chains

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hu55a1n1 hu55a1n1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Custom proof specs in config informalsystems/hermes
1 participant
@hu55a1n1