Profiling

Hopper keeps profiling tied to concrete artifacts. Use the CLI to inspect the same SBF binary you deploy, then keep benchmark claims tied to exact commits, lockfiles, and toolchain versions.

Static SBF profile

cargo build-sbf --manifest-path examples/hopper-vault/Cargo.toml
hopper profile elf target/deploy/hopper_vault.so
hopper profile elf target/deploy/hopper_vault.so --json > target/hopper-vault-profile.json

hopper profile elf reports section sizes, symbols, CU-ish static estimates, and flamegraph export data. Treat it as a repeatable binary inspection tool, not as a substitute for live compute-unit measurements.

Tiny profile and size budget

Use #[program(profile = "tiny")] on programs whose public contract includes a small binary budget. The macro emits HOPPER_PROGRAM_PROFILE and enforces the first size-shape rules at compile time:

• instruction discriminators must be one byte so dispatch stays in the dense match data[0] form;
• handler-level modifier instrumentation is rejected, including #[pipeline], #[receipt], #[invariant], and #[access_control].

Use profile = "strict" or profile = "audit" when a program needs those instrumented paths. Tiny programs still use typed contexts and Hopper account validation; the profile only keeps extra audit scaffolding out of the binary.

The repository enforces a 16 KiB SBF budget for ../examples/hopper-counter in the Solana SBF workflow. Keep that budget tied to the built .so size, not a source estimate:

cargo build-sbf -- -p hopper-counter
program=$(find target -type f -name hopper_counter.so -print -quit)
stat -c%s "${program}"

Same-provenance benchmark flow

git rev-parse HEAD
cargo tree -p hopper-lang --locked > target/hopper-tree.txt
cargo build-sbf --manifest-path examples/hopper-parity-vault/Cargo.toml
hopper profile elf target/deploy/hopper_parity_vault.so --json > target/hopper-parity-vault-profile.json

Record the following next to any public benchmark claim:

• Hopper commit and Cargo.lock hash.
• Solana CLI and cargo-build-sbf versions.
• Exact manifest path and output .so path.
• hopper profile elf JSON.
• Live CU logs when the claim depends on runtime execution.

The current same-provenance vault benchmark snapshot remains in ../BENCHMARKS.md. Regenerate it before changing launch or benchmark claims.

Release checks

cargo fmt -- --check
cargo check -q -p hopper-cli --locked
cargo run -q -p hopper-cli -- solana-check --all
hopper publish-check --package hopper-parity-vault --full

Use solana-check before build-sbf in CI so crate-shape regressions fail with plain text diagnostics instead of late SBF errors.