132 releases (83 stable)
|new 1.4.13||Nov 29, 2020|
|1.4.3||Oct 24, 2020|
|1.2.15||Jul 30, 2020|
|1.1.0||Mar 31, 2020|
|0.12.1||Mar 26, 2019|
#330 in Cryptocurrencies
486 downloads per month
$ curl https://sh.rustup.rs -sSf | sh $ source $HOME/.cargo/env $ rustup component add rustfmt
If your rustc version is lower than 1.39.0, please update it:
$ 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
$ git clone https://github.com/solana-labs/solana.git $ cd solana
$ cargo build
Run the test suite:
$ cargo test
Start your own testnet locally, instructions are in the online docs.
testnet- public stable testnet accessible via devnet.solana.com. Runs 24/7
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
The release process for this project is described here.
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!
All claims, content, designs, algorithms, estimates, roadmaps, specifications, and performance measurements described in this project are done with the author's best effort. It is up to the reader to check and validate their accuracy and truthfulness. Furthermore nothing in this project constitutes a solicitation for investment.