Security

RugFreePump is a Solana-native token launch platform driven by an on-chain bonding-curve mechanism. The protocol is designed around a clear separation between on-chain execution and enforcement and the external systems that provide application, data, and infrastructure services. The most important security boundary is the RugFreePump on-chain program. Protocol rules, protocol state transitions, and protocol-controlled SOL and token movements are executed through the deployed on-chain program and Solana accounts rather than through the off-chain dApp. The platform also depends on separate security domains, including Solana, Pyth, Raydium, off-chain infrastructure, and user-controlled wallets. This page explains how these components interact, which controls are enforced on-chain, and which authorities and trust boundaries exist in the current deployment.

​

Core security architecture

​

On-chain protocol execution

The RugFreePump on-chain program is the primary protocol execution and enforcement layer. The deployed on-chain program is responsible for the core protocol lifecycle, including:

• Token mint creation
• Bonding-curve sale creation and state management
• Contribution accounting
• Bonding-curve purchase calculations
• Protocol fee application
• Purchase and contribution limits
• Sale expiration and finalization
• Eligible withdrawals
• Liquidity migration
• Purchased token allocation and claiming
• Recovery and cancellation operations
• Required authority and account validation
• Interactions with required external Solana programs

Protocol operations are accepted only when the accounts, authorities, state, inputs, and conditions satisfy the rules implemented by the deployed on-chain program. The resulting protocol state is recorded in Solana accounts.

​

On-chain asset control

Protocol-controlled SOL and token movements are executed through the RugFreePump on-chain program and Solana accounts. The off-chain RugFreePump infrastructure does not custody or directly control users’ SOL or tokens. The on-chain execution layer governs protocol-controlled asset operations including:

• SOL contributions to bonding-curve sales
• Token purchases
• Protocol fee transfers
• Eligible withdrawals
• Bonding-curve vault balances
• Liquidity migration
• Purchased token custody and claiming
• Related protocol-controlled SOL and token transfers

The off-chain infrastructure, including the dApp, APIs, databases, indexers, and metadata services, does not directly execute or control protocol-controlled asset movements. Off-chain application state therefore does not determine whether a protocol-controlled asset transfer is permitted. The deployed RugFreePump on-chain program and the Solana runtime enforce the applicable rules and authorization requirements during transaction execution.

​

On-chain security controls

RugFreePump uses account, state, authority, input, and lifecycle validation to constrain which protocol operations the deployed on-chain program will accept.

​

Account and authority validation

The on-chain program validates the accounts and authorities required for each protocol operation. Security-relevant controls include:

• PDA derivation
• Required account validation
• Authority validation
• Sale and account state validation
• Validation of accounts associated with the expected token and bonding-curve state
• Validation of required external on-chain program addresses

These checks prevent protocol instructions from simply operating against arbitrary accounts or unauthorized protocol state.

​

Sale lifecycle controls

The on-chain program enforces the state transitions associated with a bonding-curve sale. These controls include:

• Sale-state validation
• Purchase-condition validation
• Contribution limits
• Sale expiration checks
• Finalization conditions
• Migration eligibility checks
• Migration lock periods
• Migration-state protection
• Purchased token claim eligibility
• Token unlock schedule enforcement
• Prevention of claims exceeding the buyer’s recorded token allocation
• Recovery and cancellation state validation

The on-chain program therefore determines which lifecycle transition is valid for the current on-chain state.

​

Maintenance controls

RugFreePump includes an on-chain maintenance state that can restrict protocol operations when maintenance controls are enabled. The on-chain program checks the maintenance state as part of operations that are restricted during maintenance. The protocol also uses lifecycle conditions intended to prevent maintenance controls from being enabled while active bonding-curve sales are within their protected active lifecycle. These checks are enforced by the on-chain program rather than by the dApp.

​

Purchase protection

The bonding-curve purchase path includes controls intended to constrain accepted purchases. These include:

• Minimum purchase requirements
• Contribution limits
• Purchase slippage validation
• Bonding-curve state validation
• Required SOL/USD oracle validation

These conditions are evaluated during on-chain transaction execution.

​

Oracle security

The bonding-curve mechanism uses external SOL/USD price data because the curve is denominated and calculated using USD-equivalent values while buyers contribute SOL. The current implementation uses Pyth price data and validates the supplied price before accepting it for protocol execution. The purchase path currently requires:

• Full Pyth verification
• The expected SOL/USD price feed
• A positive price
• A price update no older than 30 seconds
• Oracle confidence within the configured 2% threshold

These checks establish the conditions under which external price data can be accepted by the on-chain program. RugFreePump controls the validation rules applied to the supplied oracle data but does not control the underlying Pyth infrastructure. Pyth therefore remains an external security boundary.

​

Token supply security

RugFreePump establishes a defined token supply during token creation. The current implementation uses:

• Total supply: 1,000,000,000 tokens
• Decimals: 6
• Bonding-curve allocation: 800,000,000 tokens
• Liquidity allocation: 200,000,000 tokens

The initial supply is minted during token creation. After the initial supply is created, the mint authority is revoked. Once revoked, that authority cannot subsequently be used to create additional tokens. This establishes the protocol’s fixed-supply behavior for tokens created through the current token-creation flow.

​

Purchased token custody and claiming

Purchased tokens are not transferred directly to buyers during bonding-curve purchases. Instead, the RugFreePump on-chain program records each buyer’s cumulative purchased token allocation in the buyer’s on-chain accumulation account. The purchased tokens remain in protocol-controlled token custody throughout the bonding-curve sale and cannot be transferred to buyers before successful liquidity migration. After successful liquidity migration, buyers can claim their purchased tokens through the protocol’s claim_token instruction. The on-chain program enforces token claiming according to the sale’s selected token sale model:

• Token Unlocked (TU): The buyer’s full purchased token allocation becomes claimable immediately after successful liquidity migration.
• Token Locked (TL): Purchased tokens become claimable gradually according to the sale’s configured token unlock schedule.

The token sale model and applicable unlock configuration are recorded in the sale’s on-chain state. The claiming process is governed by on-chain account validation, the buyer’s recorded purchased token allocation, the sale’s migration state, and the applicable token unlock conditions. Off-chain infrastructure does not determine or override the amount of purchased tokens a buyer is permitted to claim.

​

Liquidity migration security

Liquidity migration represents a controlled transition from the RugFreePump bonding-curve environment to Raydium CPMM liquidity. The migration process is constrained by on-chain validation of the required sale state, timing, authorities, accounts, and external on-chain program.

​

Raydium CPMM program validation

The RugFreePump on-chain program validates the expected Raydium CPMM program before performing the external interaction. The migration therefore does not simply accept an arbitrary external on-chain program address supplied by an off-chain service. The interaction with Raydium occurs through an on-chain CPI. Raydium remains an external protocol and is outside RugFreePump’s direct control.

​

Migration state protection

The on-chain program tracks the migration state of a sale and validates whether migration is currently permitted. Migration lock and state checks prevent conflicting migration-related operations from being accepted for the same sale. This keeps the migration process within the state transitions defined by the RugFreePump on-chain program.

​

Protection against premature liquidity pool creation

RugFreePump’s token custody architecture is designed to prevent buyers from creating competing liquidity pools using purchased tokens before the protocol’s official liquidity migration. During the bonding-curve sale, purchased tokens are not transferred directly to buyers. Instead, the on-chain program records each buyer’s cumulative purchased token allocation while the corresponding tokens remain under protocol-controlled custody. Buyers cannot claim or transfer their purchased tokens before successful liquidity migration. This prevents purchased token allocations from being used to initialize external liquidity pools ahead of the protocol’s intended migration. Following successful migration, purchased tokens become claimable according to the sale’s selected Token Unlocked (TU) or Token Locked (TL) model. This protection prevents the risk of premature liquidity pool creation interfering with the protocol’s official Raydium CPMM migration.

​

Recovery path

RugFreePump includes a controlled recovery path for finalized sales when the normal liquidity-migration flow cannot safely complete. Recovery provides an alternative on-chain handling path for exceptional finalized-sale conditions rather than requiring the protocol to remain permanently dependent on an unsuccessful normal migration attempt. The recovery operation is restricted by the on-chain program’s administrative authority and applicable on-chain state and account checks. Recovery therefore acts as a protocol-level fallback mechanism for exceptional liquidity-migration conditions. It does not bypass the on-chain program. The recovery operation itself must satisfy the authorization and state-transition rules enforced by the deployed on-chain program.

​

Cancellation and contributor withdrawal

RugFreePump also provides a controlled cancellation path for finalized sales that cannot proceed through the normal liquidity-migration flow. Cancellation transitions the sale into the applicable cancellation state under the conditions enforced by the on-chain program. Once a finalized sale is placed into the cancellation state, contributors can use the protocol’s withdrawal mechanism according to the applicable withdrawal rules. This provides a defined on-chain exit path for contributor funds when a finalized sale cannot proceed through normal liquidity migration. The cancellation mechanism is therefore a protocol-level safety mechanism that prevents a finalized sale from being dependent exclusively on successful completion of the normal migration path. Cancellation and withdrawal remain governed by the deployed on-chain program, the sale’s recorded state, contributor accounting, and the available balance in the bonding-curve vault.

​

LP token handling

During successful liquidity migration, the LP tokens generated by the migration are automatically burned by the protocol flow. The associated LP token account is then closed as part of the migration process. This means the resulting LP position is not retained as an ongoing LP-token balance under the normal RugFreePump migration flow.

​

Administrative authority and upgrade security

RugFreePump currently operates under a single-authority administrative and upgrade model for the relevant on-chain program controls. The current deployment includes:

• A single on-chain program upgrade authority
• A single authorized authority controlling the relevant administrative and configuration authorities
• Administrative controls governed by that authority
• No multisig requirement for critical administrative operations
• No independent multisig governance layer currently deployed

This single-authority model is a fundamental security assumption of the current deployment.

​

On-chain program upgradeability

The RugFreePump on-chain program is upgradeable. The current on-chain program upgrade authority is controlled by the authorized authority described above. An authorized on-chain program upgrade can therefore change the code governing protocol execution. On-chain program upgrade authority is consequently part of the protocol’s security boundary and must be protected accordingly.

​

Administrative controls

The authorized administrative authority controls the protocol-level administrative functions implemented by the deployed on-chain program. These can include maintenance, configuration, recovery, cancellation, and other restricted protocol operations where applicable. Administrative authority does not come from the off-chain backend or database. It is enforced through the authorities and account checks implemented by the on-chain program. Future security improvements may introduce additional authorization layers, including multisig control. Such mechanisms are not considered active protections until they are actually deployed and used by the protocol.

​

External security boundaries

RugFreePump depends on external systems that are outside its direct control.

​

Solana

Solana provides the blockchain execution environment and account model in which the RugFreePump on-chain program operates. RugFreePump does not control:

• Solana validators
• Transaction ordering
• The Solana runtime
• Network-level execution
• The broader Solana network

The RugFreePump on-chain program executes according to the Solana transaction, account, and on-chain program execution model.

​

Pyth

Pyth provides the external SOL/USD price data required by the bonding-curve mechanism. RugFreePump validates the supplied price according to its on-chain program rules but does not control the underlying oracle infrastructure.

​

Raydium

Raydium provides external liquidity infrastructure used during migration. RugFreePump validates the expected Raydium CPMM program before interacting with it, but Raydium remains an independent external protocol.

​

Off-chain security boundary

The RugFreePump dApp and supporting off-chain infrastructure provide application and information services. These systems include:

• Website and dApp infrastructure
• APIs and application services
• Blockchain indexing
• Databases
• Real-time infrastructure
• Metadata infrastructure
• RPC providers
• Other supporting platform services

These systems can present information, retrieve indexed blockchain data, prepare supported transactions, provide metadata, and deliver real-time updates. They do not replace the RugFreePump on-chain program as the authority for protocol state transitions or protocol-controlled asset movements. The off-chain database is therefore not the authoritative ledger for protocol-controlled SOL, tokens, or on-chain protocol state. The resulting Solana account state and transaction execution remain authoritative for on-chain protocol operations.

​

User wallet security boundary

User wallets are separate from the RugFreePump protocol. RugFreePump does not control:

• User private keys
• Seed phrases
• Wallet signing authority
• User wallet balances

Transactions requiring user authorization must be approved by the user’s wallet. Users therefore retain control over the signing authority associated with their wallets. The wallet boundary is separate from the administrative authority of the RugFreePump protocol.

​

Independent on-chain verification

RugFreePump protocol execution can be independently inspected through Solana-compatible explorers and tools. Publicly verifiable information includes:

• RugFreePump on-chain program addresses
• Token mint addresses
• Solana account state
• Transaction signatures
• On-chain program instructions
• Sale state
• Protocol-controlled account activity
• Liquidity migration transactions
• Purchased token claim transactions
• Resulting blockchain state

The blockchain provides the authoritative record of executed protocol transactions and resulting on-chain state. The dApp therefore does not need to be treated as the sole source of truth for protocol execution. For the currently documented deployment and execution records, see the Proof of Execution page.

​

Current audit status

RugFreePump has not completed a formal third-party security audit at this time. A professional security audit is planned for a future stage of the project. The availability of the on-chain program or its published source code does not constitute an independent security audit.

​

Future security improvements

RugFreePump intends to strengthen the security architecture over time. Planned improvements include:

• Multisig authorization for critical operations
• Additional separation of administrative responsibilities
• Third-party security review
• Formal security audit
• Additional operational security controls

These are future improvements and are not represented as active protections in the current deployment.