Integration with Solana Runtime

Nyvo-generated programs follow Solana’s program model: they consist of accounts (storage) and instruction handlers (functions). Internally, Nyvo may use the Anchor framework to define the on-chain schema and instructions, or a similar schema, which enforces security checks and typical patterns.

All state is stored in Solana accounts, which Nyvo’s backend will create at deployment or on first use. For example, a governance module might have a PDA (Program Derived Address) for the governance treasury or config, derived deterministically from a seed like the organization name and the program ID. Nyvo leverages PDAs to create deterministic addresses for important accounts so that their addresses can be derived by any client without being explicitly stored.

This also enables the on-chain program to sign on those accounts when needed (since PDAs have no private key, the program can act as their signer). Overall, Nyvo’s architecture aligns with Solana’s philosophy of client-heavy design: complex logic runs in the on-chain program and the client (front-end) orchestrates calls to those programs via wallet-signed transactions.