-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
update signing info endpoint #1889
update signing info endpoint #1889
Conversation
…nstead of cosmosvaladdr for consistencyu reasons
13c7c8a
to
6782672
Compare
Thanks for the PR; see #1866 (comment). I'm still OK with merging this for now, but we should leave the issue open, and note that the REST endpoints may need to change in the future. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Codecov Report
@@ Coverage Diff @@
## develop #1889 +/- ##
========================================
Coverage 63.83% 63.83%
========================================
Files 118 118
Lines 7024 7024
========================================
Hits 4484 4484
Misses 2285 2285
Partials 255 255 |
Fixed merge conflict with develop. |
Thanks; merged. |
docs/
) - (/slashing/signing-info endpoint does not appear to exist in spec, or api docs)PENDING.md
that include links to the relevant issue or PR that most accurately describes the change.cmd/gaia
andexamples/
As discussed in #1866, REST endpoint
/slashing/signing-info/{ validator }
should takecosmosValPub
rather than existingcosmosVallAddr
in order to maintain consistency between REST and CLI interfaces.For Admin Use: