Docs Build
Move a Solana app
Move a Solana program and its client to Acrux. Check what it calls, deploy the same binary at the same address, point the client at Acrux's RPC, and create its accounts on the new chain.
A Solana app moves to Acrux without a rewrite: the program is the same SBF binary, the client the same code, and only the RPC URL changes. What does not move by itself is the chain's state, so the app's accounts are created again on Acrux by its own instructions.
Check what the program calls
Every program your program invokes, and every program your client builds instructions for, has to be on Acrux. Solana's token and memo programs are there at their mainnet addresses: Programs on Acrux. A program of your own that it calls moves with it, in the next step.
Deploy the same binary at the same address
Build the program as you do for Solana and deploy it with the stock CLI pointed at Acrux, with
--use-rpc(Deploy a program). Deploy with the program keypair you deploy with on Solana,target/deploy/<program>-keypair.jsonby default, and it lands at the same program ID, so every address your client derives from it stays the same:Terminalsolana config set --url https://rpc.acrux.computer solana program deploy --use-rpc target/deploy/<program>.so --program-id target/deploy/<program>-keypair.jsonWith Anchor,
anchor deploy --provider.cluster https://rpc.acrux.computer -- --use-rpcdoes the same from the workspace (Anchor). The deployer pays in ACRUX: fund it from the faucet.Point the client at Acrux
Change the RPC URL and nothing else. web3.js derives the WebSocket for its confirmations from it.
Client Where the URL goes @solana/web3.jsnew Connection('https://rpc.acrux.computer', 'confirmed')Anchor the provider's cluster, --provider.cluster https://rpc.acrux.computer, orANCHOR_PROVIDER_URLsolanaCLIsolana config set --url https://rpc.acrux.computerA user's wallet its custom RPC (Add Acrux network) Create the app's accounts
Acrux is its own chain, so the accounts your app holds on Solana (its config and state accounts, its mints, its users' token accounts) are not on it. Run your program's own setup instructions against Acrux, as you would on a fresh cluster: its PDAs derive to the same addresses from the same program ID and seeds. Users fund their keys from the faucet and pay fees in ACRUX.
What a client sees on Acrux
The calls are Solana's; a few of their answers follow from 50 ms slots and three proposers a slot:
| On Acrux | |
|---|---|
| Blockhash lifetime | 1,200 slots, one minute (getLatestBlockhash) |
| Confirmation | confirmed and finalized arrive together, once the transaction's cblock is final (web3.js) |
| Priority fee | none is needed to land; a slot's merge orders by priority fee per compute unit, and getRecentPrioritizationFees answers 0 |
| Fees | the base fee, the priority fee, and an inclusion fee for each proposer that carries the transaction (Fees and the reserve rule) |
| Sending | sendTransaction sends to the next slot's three proposers; the CLI needs --use-rpc, since Acrux has no TPU port |
| Sealed sends | the same signed transaction, split t-of-n with @acrux/sdk, so no proposer reads it alone |