gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Docs cleanup (#16997)

Browse Source
This commit is contained in:
Justin Starry
2021-05-03 10:59:03 +08:00
committed by GitHub
parent 894bedcae7
commit 1fde69ef48
52 changed files with 19620 additions and 8606 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/cluster/bench-tps.md
View File

@@ -96,13 +96,13 @@ For example
- To enable `info` everywhere and `debug` only in the solana::banking_stage module:
```bash
export RUST_LOG=solana=info,solana::banking_stage=debug
export RUST_LOG=solana=info,solana::banking_stage=debug
```
- To enable BPF program logging:
```bash
export RUST_LOG=solana_bpf_loader=trace
export RUST_LOG=solana_bpf_loader=trace
```
Generally we are using `debug` for infrequent debug messages, `trace` for potentially frequent messages and `info` for performance-related logging.

20
docs/src/cluster/vote-signing.md
View File

@@ -24,19 +24,19 @@ The vote signing service consists of a JSON RPC server and a request processor.
1. Register a new validator node
- The request must contain validator's identity \(public key\)
- The request must be signed with the validator's private key
- The service drops the request if signature of the request cannot be verified
- The service creates a new voting asymmetric key for the validator, and returns the public key as a response
- If a validator tries to register again, the service returns the public key from the pre-existing keypair
- The request must contain validator's identity \(public key\)
- The request must be signed with the validator's private key
- The service drops the request if signature of the request cannot be verified
- The service creates a new voting asymmetric key for the validator, and returns the public key as a response
- If a validator tries to register again, the service returns the public key from the pre-existing keypair
2. Sign a vote
- The request must contain a voting transaction and all verification data
- The request must be signed with the validator's private key
- The service drops the request if signature of the request cannot be verified
- The service verifies the voting data
- The service returns a signature for the transaction
- The request must contain a voting transaction and all verification data
- The request must be signed with the validator's private key
- The service drops the request if signature of the request cannot be verified
- The service verifies the voting data
- The service returns a signature for the transaction
## Validator voting