598093b5db
When starting a validator, the node initially joins gossip with shred_verison = 0, until it adopts the entrypoint's shred-version: https://github.com/solana-labs/solana/blob/9b182f408/validator/src/main.rs#L417 Depending on the load on the entrypoint, this adopting entrypoint shred-version through gossip sometimes becomes very slow, and causes several problems in gossip because we have to partially support shred_version == 0 which is a source of leaking crds values from one cluster to another. e.g. see https://github.com/solana-labs/solana/pull/17899 and the other linked issues there. In order to remove shred_version == 0 from gossip, this commit adds shred-version to ip-echo-server response. Once the entrypoints are updated, on validator start-up, if --expected_shred_version is not specified we will obtain shred-version from the entrypoint using ip-echo-server. |
||
|---|---|---|
| .buildkite | ||
| .github | ||
| .travis | ||
| account-decoder | ||
| accounts-bench | ||
| accounts-cluster-bench | ||
| banking-bench | ||
| banks-client | ||
| banks-interface | ||
| banks-server | ||
| bench-exchange | ||
| bench-streamer | ||
| bench-tps | ||
| ci | ||
| clap-utils | ||
| cli | ||
| cli-config | ||
| cli-output | ||
| client | ||
| core | ||
| crate-features | ||
| docs | ||
| dos | ||
| download-utils | ||
| explorer | ||
| faucet | ||
| frozen-abi | ||
| genesis | ||
| genesis-utils | ||
| gossip | ||
| install | ||
| keygen | ||
| ledger | ||
| ledger-tool | ||
| local-cluster | ||
| log-analyzer | ||
| logger | ||
| measure | ||
| merkle-root-bench | ||
| merkle-tree | ||
| metrics | ||
| multinode-demo | ||
| net | ||
| net-shaper | ||
| net-utils | ||
| notifier | ||
| perf | ||
| poh | ||
| poh-bench | ||
| program-test | ||
| programs | ||
| rayon-threadlimit | ||
| rbpf-cli | ||
| remote-wallet | ||
| rpc | ||
| runtime | ||
| scripts | ||
| sdk | ||
| stake-accounts | ||
| storage-bigtable | ||
| storage-proto | ||
| streamer | ||
| sys-tuner | ||
| system-test | ||
| tokens | ||
| transaction-status | ||
| upload-perf | ||
| validator | ||
| version | ||
| watchtower | ||
| web3.js | ||
| .clippy.toml | ||
| .codecov.yml | ||
| .gitignore | ||
| .mergify.yml | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| RELEASE.md | ||
| SECURITY.md | ||
| cargo | ||
| cargo-build-bpf | ||
| cargo-test-bpf | ||
| fetch-perf-libs.sh | ||
| fetch-spl.sh | ||
| run.sh | ||
| test-abi.sh | ||
README.md
Building
1. Install rustc, cargo and rustfmt.
$ curl https://sh.rustup.rs -sSf | sh
$ source $HOME/.cargo/env
$ rustup component add rustfmt
Please sure you are always using the latest stable rust version by running:
$ rustup update
On Linux systems you may need to install libssl-dev, pkg-config, zlib1g-dev, etc. On Ubuntu:
$ sudo apt-get update
$ sudo apt-get install libssl-dev libudev-dev pkg-config zlib1g-dev llvm clang make
On Mac M1s, make sure you set up your terminal & homebrew to use Rosetta. You can install it with:
$ softwareupdate --install-rosetta
2. Download the source code.
$ git clone https://github.com/solana-labs/solana.git
$ cd solana
3. Build.
$ cargo build
4. Run a minimal local cluster.
$ ./run.sh
Testing
Run the test suite:
$ cargo test
Starting a local testnet
Start your own testnet locally, instructions are in the online docs.
Accessing the remote development cluster
devnet- stable public cluster for development accessible via devnet.solana.com. Runs 24/7. Learn more about the public clusters
Benchmarking
First install the nightly build of rustc. cargo bench requires use of the
unstable features only available in the nightly build.
$ rustup install nightly
Run the benchmarks:
$ cargo +nightly bench
Release Process
The release process for this project is described here.
Code coverage
To generate code coverage statistics:
$ scripts/coverage.sh
$ open target/cov/lcov-local/index.html
Why coverage? While most see coverage as a code quality metric, we see it primarily as a developer productivity metric. When a developer makes a change to the codebase, presumably it's a solution to some problem. Our unit-test suite is how we encode the set of problems the codebase solves. Running the test suite should indicate that your change didn't infringe on anyone else's solutions. Adding a test protects your solution from future changes. Say you don't understand why a line of code exists, try deleting it and running the unit-tests. The nearest test failure should tell you what problem was solved by that code. If no test fails, go ahead and submit a Pull Request that asks, "what problem is solved by this code?" On the other hand, if a test does fail and you can think of a better way to solve the same problem, a Pull Request with your solution would most certainly be welcome! Likewise, if rewriting a test can better communicate what code it's protecting, please send us that patch!
Disclaimer
All claims, content, designs, algorithms, estimates, roadmaps, specifications, and performance measurements described in this project are done with the Solana Foundation's ("SF") best efforts. It is up to the reader to check and validate their accuracy and truthfulness. Furthermore nothing in this project constitutes a solicitation for investment.
Any content produced by SF or developer resources that SF provides, are for educational and inspiration purposes only. SF does not encourage, induce or sanction the deployment, integration or use of any such applications (including the code comprising the Solana blockchain protocol) in violation of applicable laws or regulations and hereby prohibits any such deployment, integration or use. This includes use of any such applications by the reader (a) in violation of export control or sanctions laws of the United States or any other applicable jurisdiction, (b) if the reader is located in or ordinarily resident in a country or territory subject to comprehensive sanctions administered by the U.S. Office of Foreign Assets Control (OFAC), or (c) if the reader is or is working on behalf of a Specially Designated National (SDN) or a person subject to similar blocking or denied party prohibitions.
The reader should be aware that U.S. export control and sanctions laws prohibit U.S. persons (and other persons that are subject to such laws) from transacting with persons in certain countries and territories or that are on the SDN list. As a project based primarily on open-source software, it is possible that such sanctioned persons may nevertheless bypass prohibitions, obtain the code comprising the Solana blockchain protocol (or other project code or applications) and deploy, integrate, or otherwise use it. Accordingly, there is a risk to individuals that other persons using the Solana blockchain protocol may be sanctioned persons and that transactions with such persons would be a violation of U.S. export controls and sanctions law. This risk applies to individuals, organizations, and other ecosystem participants that deploy, integrate, or use the Solana blockchain protocol code directly (e.g., as a node operator), and individuals that transact on the Solana blockchain through light clients, third party interfaces, and/or wallet software.