Deploying Solana Programs to Mainnet: Setup, Audit, Verification

In practice, we often encounter this situation: a team spends weeks developing, but when deploying to mainnet, they discover that rent-exemption wasn't accounted for or upgrade authority is tied to a single key. One client came with a ready program of 150 KB — at deployment, solana rent showed 1.2 SOL, but the wallet only had 0.5 SOL. We had to urgently buy more tokens and rewrite scripts. Solana is not EVM: each transaction and account requires planning. We perform turnkey deployment, from Anchor setup to final verification, and know all the pitfalls.

Instrumentation: Anchor Framework vs Native Rust

Anchor is the standard framework for Solana development. If you write in native Rust without Anchor, multiply development time by 3 and add manual instruction deserialization. Anchor handles most of the boilerplate and generates IDL (Interface Definition Language) — the analog of ABI for EVM.

# Build
anchor build

# Deploy to mainnet-beta
anchor deploy --provider.cluster mainnet-beta \
  --provider.wallet ~/.config/solana/deployer-keypair.json

Deployment Cost: Rent-Exemption

In Solana, storing data in an account costs SOL in the form of rent. To prevent the account from being deleted, you need to maintain a minimum balance (rent-exemption). The size of the program account is proportional to the bytecode size. It's important to plan: the deployment budget must include not only transaction fees (~0.00025 SOL) but also the rent-exemption for storing the program account itself.

# Estimate cost before deployment
solana rent <bytes>
# Example: program 200KB ≈ 1.4 SOL rent-exemption

Buffer Account and Two-Stage Deployment

Solana limits the size of a single transaction. Programs larger than a few kilobytes are deployed in several stages via a buffer account:

1. Create a buffer account.
2. Load bytecode in parts via solana program write-buffer.
3. Deploy the program atomically from the buffer.

Anchor does this automatically. For manual deployment via CLI:

solana program deploy \
  --program-id target/deploy/my_program-keypair.json \
  --buffer /path/to/buffer-keypair.json \
  target/deploy/my_program.so

Why Upgrade Authority Is the Biggest Risk?

By default, Anchor creates an upgradeable program with upgrade authority equal to the deployer keypair. This is fine for development but not for production. In production, we transfer authority to a multisig (Squads Protocol — the standard multisig on Solana). Any program update then requires M-of-N signatures. This is critical for mainnet — a single key as upgrade authority is a single point of failure. One of our clients lost $10k due to a leaked deployer keypair when an attacker updated the program to a malicious version. After that, we implemented multisig for all projects.

Immutable program — if the logic is final and no updates are planned. This is irreversible: after --final, the program cannot be updated or closed.

How We Find PDA Collisions?

Program Derived Addresses (PDA) are unique addresses derived from program ID and seeds. A collision occurs when two different data accounts generate the same PDA. We test for collisions using findProgramAddress in tests, and also use bump seeds (from 255 to 0) to eliminate conflicts. In one project, we discovered a collision in 3 of our seeds — this could have led to funds theft. A security audit firm (Neodyme) confirmed our finding.

Verification and IDL

After deployment, we upload the IDL on-chain — this allows other developers and tools (Explorer, Anchor clients) to automatically know the program interface.

anchor idl init --filepath target/idl/my_program.json <PROGRAM_ID> \
  --provider.cluster mainnet-beta

Source code verification is done via solana-verify (by OtterSec). It publishes proof that the on-chain bytecode corresponds to a specific Git commit.

Checklist Before Mainnet Deployment

• Full test coverage on localnet and devnet.
• Audit (OtterSec, Neodyme, Trail of Bits — specialize in Solana).
• Program derived addresses (PDA) checked for collisions.
• Integer overflow check (overflow-checks = true in Cargo.toml).
• Upgrade authority transferred to multisig.
• Sufficient SOL in deployer wallet including rent-exemption.
• Monitoring via Helius webhooks or Shyft for critical instructions.

What's Included in the Work

• Configuring Anchor for your project. Deploying the program to mainnet/devnet with buffer setup. Transferring upgrade authority to multisig or finalizing. Uploading IDL on-chain. Verifying code via solana-verify. Documentation of account structure and instructions. Support for 14 days after deployment.

We have performed deployment for 50+ projects and guarantee that your contract will work without surprises. Contact us to evaluate your project — our engineers with 5+ years of blockchain experience will respond within a day. Get a consultation for your project today.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.