Module lazy 

Lazy account parser – on-demand account deserialization.

The standard entrypoint parses every account upfront, burning CU even for accounts the instruction never touches. The lazy parser gives you instruction data and program ID immediately, then hands back an iterator that parses accounts one at a time ON DEMAND.

Hopper’s lazy path is distinct not because Pinocchio lacks lazy parsing, but because Hopper Native pre-scans the instruction tail, preserves canonical duplicate-account handling in raw_input, and then exposes a LazyContext that already knows instruction_data and program_id before the first account is materialized.

CU Savings

Programs that dispatch on instruction_data[0] and only need a subset of accounts save measurable CU. A vault program that routes 8 instruction variants through a single entrypoint might only parse 2-3 of 10 accounts for a given variant.

Usage

use hopper_native::lazy::LazyContext;
use hopper_native::hopper_lazy_entrypoint;

hopper_lazy_entrypoint!(process);

fn process(ctx: LazyContext) -> ProgramResult {
    let disc = ctx.instruction_data().first().copied().unwrap_or(0);
    match disc {
        0 => {
            let payer = ctx.next_account()?;
            let vault = ctx.next_account()?;
            // Remaining accounts are never parsed.
            do_deposit(payer, vault, &ctx.instruction_data()[1..])
        }
        _ => Err(ProgramError::InvalidInstructionData),
    }
}

Structs

LazyContext

Pre-parsed header from the BPF input buffer: instruction data + program ID, plus a cursor positioned at the first account.

Functions

lazy_deserialize^⚠

Deserialize a BPF input buffer into a LazyContext.