20a7cdd43d
* Restrict access to Bank's HardForks Callers could previously obtain a a lock to read/write HardForks from any Bank. This would allow any caller to modify, and creates the opportunity for inconsistent handling of what is considered a valid hard fork (ie too old). This PR adds a function to Bank so consistent sanity checks can be applied; the caller will already have a Bank as that is where they would have obtained the HardForks from in the first place. Additionally, change the getter to return a copy of HardForks (simple Vec). * Allow hard fork at bank slot if bank is not yet frozen |
||
|---|---|---|
| .. | ||
| benches | ||
| bpf | ||
| cargo-build-bpf | ||
| cargo-build-sbf | ||
| cargo-test-bpf | ||
| cargo-test-sbf | ||
| docker-solana | ||
| gen-headers | ||
| macro | ||
| program | ||
| sbf | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.toml | ||
| README.md | ||
| build.rs | ||
| package.json | ||
README.md
Solana SDK
Use the Solana SDK Crate to write client side applications in Rust. If writing on-chain programs, use the Solana Program Crate instead.
More information about Solana is available in the Solana documentation.
The Solana Program Library provides examples of how to use this crate.
Still have questions? Ask us on Stack Exchange