* add functionality to read proof from accounts instead of instruction data * update add tests * clippy * clarify instruction data discriminator * avoid cloning entire proof data * Update programs/zk-token-proof/src/lib.rs Co-authored-by: Jon C <me@jonc.dev> * update `PROOF_OFFSET_LENGTH` to `INSTRUCTION_DATA_LENGTH_WITH_PROOF_ACCOUNT` * update instruction docs * add feature gate * Update sdk/src/feature_set.rs Co-authored-by: Jon C <me@jonc.dev> * update feature name `enable_zk_from_account` to `enable_zk_proof_from_account` * Apply suggestions from code review Co-authored-by: Jon C <me@jonc.dev> * clarify the instruction data length more precisely --------- Co-authored-by: Jon C <me@jonc.dev> |
||
---|---|---|
.. | ||
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