gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
f4f14c42bb40d19a986fe9b1b29915acfdd497aa
solana/docs/src/running-validator/validator-info.md
Dan Albert ffeac298a2 Move from gitbook to docusaurus, build docs in Travis CI (#10970) 
* fix: ignore unknown fields in more RPC responses

* Remove mdbook infrastructure

* Delete gitattributes and other theme related items

Move all docs to /docs folder to support Docusaurus

* all docs need to be moved to /docs

* can be changed in the future

Add Docusaurus infrastructure

* initialize docusaurus repo

Remove trailing whitespace, add support for eslint

Change Docusaurus configuration to support `src`

* No need to rename the folder! Change a setting and we're all good to
go.

* Fixing rebase items

* Remove unneccessary markdown file, fix type

* Some fonts are hard to read. Others, not so much. Rubik, you've been
sidelined. Roboto, into the limelight!

* As much as we all love tutorials, I think we all can navigate around a
markdown file. Say goodbye, `mdx.md`.

* Setup deployment infrastructure

* Move docs job from buildkite to travic

* Fix travis config

* Add vercel token to travis config

* Only deploy docs after merge

* Docker rust env

* Revert "Docker rust env"

This reverts commit f84bc208e807aab1c0d97c7588bbfada1fedfa7c.

* Build CLI usage from docker

* Pacify shellcheck

* Run job on PR and new commits for publication

* Update README

* Fix svg image building

* shellcheck

Co-authored-by: Michael Vines <mvines@gmail.com>
Co-authored-by: Ryan Shea <rmshea@users.noreply.github.com>
Co-authored-by: publish-docs.sh <maintainers@solana.com>
2020-07-11 05:11:07 +00:00

1.8 KiB
Raw Blame History

title
title
Publishing Validator Info

You can publish your validator information to the chain to be publicly visible to other users.

Run solana validator-info

Run the solana CLI to populate a validator info account:

solana validator-info publish --keypair ~/validator-keypair.json <VALIDATOR_INFO_ARGS> <VALIDATOR_NAME>

For details about optional fields for VALIDATOR_INFO_ARGS:

solana validator-info publish --help

Example Commands

Example publish command:

solana validator-info publish "Elvis Validator" -n elvis -w "https://elvis-validates.com"

Example query command:

solana validator-info get

which outputs

Validator info from 8WdJvDz6obhADdxpGCiJKZsDYwTLNEDFizayqziDc9ah
  Validator pubkey: 6dMH3u76qZ7XG4bVboVRnBHR2FfrxEqTTTyj4xmyDMWo
  Info: {"keybaseUsername":"elvis","name":"Elvis Validator","website":"https://elvis-validates.com"}

Keybase

Including a Keybase username allows client applications (like the Solana Network Explorer) to automatically pull in your validator public profile, including cryptographic proofs, brand identity, etc. To connect your validator pubkey with Keybase:

  1. Join https://keybase.io/ and complete the profile for your validator

  2. Add your validator identity pubkey to Keybase:

    • Create an empty file on your local computer called validator-<PUBKEY>

    • In Keybase, navigate to the Files section, and upload your pubkey file to

      a solana subdirectory in your public folder: /keybase/public/<KEYBASE_USERNAME>/solana

    • To check your pubkey, ensure you can successfully browse to

      https://keybase.pub/<KEYBASE_USERNAME>/solana/validator-<PUBKEY>

  3. Add or update your solana validator-info with your Keybase username. The

    CLI will verify the validator-<PUBKEY> file