Skip to main content
RugFreePump exposes its protocol through a native Solana program and its public Anchor interface. Developers can integrate directly with the on-chain program using standard Solana tooling. The RugFreePump web application and backend infrastructure are entirely decoupled from the core protocol and are not required for direct on-chain integration.

​
Development Environments

RugFreePump provides separate Solana clusters for development and production. Use the program ID that matches your target Solana cluster.
  • Devnet: For development, integration testing, transaction construction validation, and isolated program interaction.
  • Mainnet: For production integrations and live user transactions.

​
Public Integration Surface

The complete deployed program interface remains available through the Anchor IDL. Currently, the Developer Guide provides an exhaustive integration reference for the following primary entry point: The buy instruction can be invoked directly by off-chain Solana clients (e.g., TypeScript SDKs) or by external on-chain Solana programs through Cross-Program Invocation (CPI), subject to the account, signer, authority, and state constraints enforced by the runtime.

​
Protocol Accounting Units

RugFreePump enforces deterministic integer-scaled values for all on-chain accounting to prevent floating-point precision loss.

​
On-Chain State & Integration Artifacts

The RugFreePump program state and its associated Solana accounts serve as the sole authoritative source of truth. Off-chain applications may provide indexing, caching, or data aggregation, but these layers are entirely optional. To implement a direct integration, your client or program will consume the following primary artifacts:
  • RugFreePump Program ID
  • Anchor IDL & generated TypeScript types
  • Instruction account layouts & argument definitions
  • Program Derived Address (PDA) seeds and external account dependencies
  • Program-emitted Events
See the Anchor IDL & Types reference for complete artifact downloads, and for granular transaction construction data, see the Buy documentation.

​
CPI Compatibility

Public entry points may be invoked through Cross-Program Invocation (CPI), subject to the account, signer, authority, state, and Solana runtime requirements applicable to each instruction. On-chain callers must satisfy the same structural validation, signer, authority, and state requirements enforced against standard client transactions. Note: RugFreePump does not currently distribute a standalone CPI wrapper or Rust integration crate. A dedicated CPI utility crate is planned for a future developer tooling release. In the interim, programs should generate CPI helpers directly via the Anchor IDL.