Skip to main content
The programs use an explicit binary interface. There is no Anchor IDL in this repository. The references below define instruction bytes, account order and PDA seeds.

Connect your project

Install @solana/kit. These examples use devnet and a Kit signer supplied by your connected wallet. Your wallet must support signing version-0 transactions.
Use your provider’s RPC and WebSocket URLs in a production integration. Keep the signer and cluster fixed throughout the operation. See deployed programs for availability and Kit wallet signers for connecting your wallet. Rawchunks does not provide a separate Solana client package.

Send an instruction

Each program reference gives the instruction’s data and ordered accounts. Assemble them as { programAddress, accounts, data }, then use this sequence. instruction is the object built on the Factory page, or another documented program instruction.
Show the simulated operation to the user before requesting their signature. After confirmation, read the resulting song or license account. If confirmation is uncertain, look up the saved signature before rebuilding or sending again. A seed conflict requires fresh counter reads; an expired blockhash requires a fresh transaction.

Build and test locally

Clone the blockchain repository. Install Rust and the Solana CLI toolchain. Run from programs/: The locked host-test dependencies require Rust 1.97.1 or newer. The SBF build uses the Solana toolchain’s compiler.
Build all three programs first. Tests load rawchunks_factory.so, rawchunks_royalties.so and rawchunks_remix.so from target/deploy/. LiteSVM runs transaction flows, including license purchases, variation minting, token balances and account validation. Mollusk runs individual instruction benchmarks. To run just those benchmarks:
Tests run locally without an RPC connection or network transaction. Pinocchio · LiteSVM · Mollusk