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

Add validator RPC updates #278

Closed
wants to merge 3 commits into from
Closed

Conversation

bachase
Copy link
Contributor

@bachase bachase commented Oct 13, 2017

Adds documentation for upcoming validator_lists and validator_sites RPC calls. See XRPLF/rippled#2242. I think the RPC formats have settled, but will update this PR if anything changes.

Copy link
Collaborator

@mDuo13 mDuo13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a couple really small nitpicky comments, but largely, this looks great. Thanks so much for the work here!

When we have an official validator publisher live at its final URL, it would be great to replace the examples with versions using the production site, list, and quorum. Until then, it's fine as-is.

## validator_lists ##
[[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ValidatorLists.cpp "Source")

The `validator_lists` command returns human readable information about the current list of published and trusted validators used by the server. [New in: rippled 0.90.0]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[New in: rippled 0.90.0]

Please add an extra [] to the end there. (Markdown style / compatibility thing)

| `available` | Boolean | If `false`, the validator keys in `list` may no longer be supported by this publisher. |
| `expiration` | String | Either the human readable time when this published list will expire or the string `unknown` if the server has yet to load a list for this publisher. |
| `list` | Array | Array of published validator keys. |
| `pubkey_publisher` | String | Hex encoded public key of publisher. |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What type of key must publishers use? ECDSA? Are there other options?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It supports whatever the PublicKey class supports, which is currently secp25k1 or ed25519, but I think the external tooling for generating keys does ed25519 by default. What is the best designation for that?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just change the description to something like this:

Ed25519 or ECDSA public key of the list publisher, as hexadecimal.

## validator_sites ##
[[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/ValidatorSites.cpp "Source")

The `validator_sites` command returns status information of sites serving validator lists. [New in: rippled 0.90.0]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change [New in: rippled 0.90.0] to [New in: rippled 0.90.0][] for greater Markdown compatibility

@bachase
Copy link
Contributor Author

bachase commented Oct 17, 2017

I think we are close to having the official list ready, so I'll push the updates after that. Do you prefer I squash down to a single commit?

@mDuo13
Copy link
Collaborator

mDuo13 commented Oct 18, 2017

No need to squash commits

@mDuo13
Copy link
Collaborator

mDuo13 commented Dec 1, 2017

merged as df621af

@mDuo13 mDuo13 closed this Dec 1, 2017
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

Successfully merging this pull request may close these issues.

None yet

2 participants