cafa85bfbb
Indices for code and data shreds of the same slot overlap; and so they will have the same random number generator seed when shuffling cluster nodes for turbine broadcast. This results in the same propagation path for code and data shreds of the same index and effectively smaller sample size for re-transmitter nodes. For example a 32:32 batch (32 code + 32 data shreds), is retransmitted through _at most_ 32 unique nodes, whereas ideally we want ~64 unique re-transmitters. This commit adds shred-type to seed function so that code and data sherds of the same (slot, index) will (most likely) have different propagation paths. |
||
|---|---|---|
| .. | ||
| benches | ||
| bpf | ||
| cargo-build-bpf | ||
| cargo-test-bpf | ||
| docker-solana | ||
| gen-headers | ||
| macro | ||
| program | ||
| 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 Discord