Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/across-protocol/contracts/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers deploying Across Protocol contracts on both EVM chains (using Hardhat or Foundry) and Solana/SVM chains (using Anchor).

​
Prerequisites

Before deploying, ensure you have:
  • Node.js (minimum version 16.18.0, recommended 20.17)
  • Foundry - Installation guide
  • Anchor (for Solana) - Installation guide
  • Environment variables configured (RPC URLs, API keys, etc.)
If you encounter build issues, try downgrading to Node 20.17 using nvm use 20.17. For Anchor users, run avm use latest if you’ve never used Anchor before.

​
EVM Deployment

​
Environment Setup

Create environment variables for your deployment: 
export NODE_URL_1=https://mainnet.infura.com/v3/YOUR_KEY
export ETHERSCAN_API_KEY=YOUR_ETHERSCAN_KEY
export MNEMONIC="your twelve word mnemonic phrase here"
The contracts use named RPC endpoints based on chain ID. See foundry.toml for the complete list: 
[rpc_endpoints]
arbitrum = "${NODE_URL_42161}"
base = "${NODE_URL_8453}"
ethereum = "${NODE_URL_1}"
optimism = "${NODE_URL_10}"
polygon = "${NODE_URL_137}"
# ... see foundry.toml for full list
1

Build contracts

Compile all contracts before deployment:
forge build
2

Deploy HubPool

Deploy the HubPool contract on Ethereum mainnet:
forge script script/DeployHubPool.s.sol:DeployHubPool \
  --rpc-url ethereum \
  --broadcast \
  --verify \
  -vvvv
First test deployment without --broadcast to simulate in dry-run mode.
3

Deploy SpokePool

Deploy a SpokePool on your target chain (e.g., Arbitrum):
forge script script/DeployArbitrumSpokePool.s.sol:DeployArbitrumSpokePool \
  --rpc-url arbitrum \
  --broadcast \
  --verify \
  -vvvv
Available SpokePool deployment scripts:
  • DeployArbitrumSpokePool.s.sol
  • DeployOptimismSpokePool.s.sol
  • DeployPolygonSpokePool.s.sol
  • DeployZkSyncSpokePool.s.sol
  • DeployUniversalSpokePool.s.sol
  • And more in script/ directory
4

Extract deployed addresses

After deployment, extract addresses to the deployment registry:
yarn extract-addresses
This updates /broadcast/deployed-addresses.json with your new deployments.

​
ZKSync Deployment

ZKSync requires special configuration using the zksolc compiler:
1

Install foundry-zksync

Install the ZKSync fork of Foundry:See instructions here.
2

Set ZKSync profile

export FOUNDRY_PROFILE=zksync
3

Deploy contract

FOUNDRY_PROFILE=zksync forge script script/DeployZkSyncSpokePool.s.sol:DeployZkSyncSpokePool \
  --rpc-url zksync \
  --broadcast \
  --verify \
  -vvvv
Or use the yarn shortcut:
yarn forge-script-zksync script/DeployZkSyncSpokePool.s.sol:DeployZkSyncSpokePool \
  --rpc-url zksync \
  --broadcast \
  --verify \
  -vvvv

​
Hardhat Deployment (Legacy)

While Foundry is recommended, Hardhat is still supported: 
NODE_URL_1=https://mainnet.infura.com/xxx \
  yarn hardhat deploy --tags HubPool --network mainnet

​
Solana/SVM Deployment

Solana deployment uses Anchor and requires verified builds for production.

​
Initial Setup

1

Verify program IDs match keypairs

Before deploying for the first time, ensure all program IDs in lib.rs and Anchor.toml match the deployment keypairs:
anchor keys list
Update IDs in your code to match keypairs under target/deploy/ and commit changes.
2

Build verified binaries

Use verified docker builds for production:
unset IS_TEST  # Ensures production build
yarn build-svm-solana-verify  # Builds verified SVM binaries
yarn generate-svm-artifacts  # Builds IDLs
3

Set environment variables

Export required variables:
export RPC_URL=https://api.devnet.solana.com
export KEYPAIR=~/.config/solana/dev-wallet.json
export PROGRAM=svm_spoke  # Also repeat for multicall_handler
export PROGRAM_ID=$(cat target/idl/$PROGRAM.json | jq -r ".address")
export MULTISIG=<YOUR_SQUADS_VAULT_ADDRESS>
export SOLANA_VERSION=$(grep -A 2 'name = "solana-program"' Cargo.lock | grep 'version' | head -n 1 | cut -d'"' -f2)
For initial deployment, also set:
export SVM_CHAIN_ID=$(cast to-dec $(cast shr $(cast shl $(cast keccak solana-devnet) 208) 208))
export HUB_POOL=0x14224e63716afAcE30C9a417E0542281869f7d9e  # Sepolia
export DEPOSIT_QUOTE_TIME_BUFFER=3600
export FILL_DEADLINE_BUFFER=21600
export MAX_LEN=$(( 2 * $(stat -c %s target/deploy/$PROGRAM.so) ))

​
Deploy Program

1

Deploy the program

solana program deploy \
  --url $RPC_URL \
  --keypair $KEYPAIR \
  --program-id target/deploy/$PROGRAM-keypair.json \
  --max-len $MAX_LEN \
  --with-compute-unit-price 100000 \
  --max-sign-attempts 100 \
  --use-rpc \
  target/deploy/$PROGRAM.so
2

Transfer upgrade authority to multisig

solana program set-upgrade-authority \
  --url $RPC_URL \
  --keypair $KEYPAIR \
  --skip-new-upgrade-authority-signer-check \
  $PROGRAM_ID \
  --new-upgrade-authority $MULTISIG
3

Upload IDL

anchor idl init \
  --provider.cluster $RPC_URL \
  --provider.wallet $KEYPAIR \
  --filepath target/idl/$PROGRAM.json \
  $PROGRAM_ID
4

Set IDL authority to multisig

anchor idl set-authority \
  --provider.cluster $RPC_URL \
  --provider.wallet $KEYPAIR \
  --program-id $PROGRAM_ID \
  --new-authority $MULTISIG

​
Initialize SVM Spoke

For svm_spoke, initialize the program state: 
anchor run initialize \
  --provider.cluster $RPC_URL \
  --provider.wallet $KEYPAIR -- \
  --chainId $SVM_CHAIN_ID \
  --remoteDomain 0 \
  --crossDomainAdmin $HUB_POOL \
  --svmAdmin $MULTISIG \
  --depositQuoteTimeBuffer $DEPOSIT_QUOTE_TIME_BUFFER \
  --fillDeadlineBuffer $FILL_DEADLINE_BUFFER

​
Create Token Vault

Create a vault for accepting deposits: 
export MINT=4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU  # USDC on devnet
anchor run createVault \
  --provider.cluster $RPC_URL \
  --provider.wallet $KEYPAIR -- \
  --originToken $MINT
Update the deployment info in deployments/legacy-addresses.json with the deployed program ID and deployment slot after deployment.

​
Deployment Best Practices

  • Always test in simulation mode first - Run deployment scripts without --broadcast to verify parameters
  • Verify contract addresses - Double-check all referenced addresses (HubPool, WETH, bridges, etc.)
  • Use verified builds for production - Especially for Solana, always use verified docker builds
  • Document deployments - Update deployment registries immediately after deployment
  • Set appropriate buffer values - QUOTE_TIME_BUFFER and FILL_DEADLINE_BUFFER affect user experience
  • Test upgrade authority - Verify multisig control before announcing deployments

​
Next Steps

After deployment:
  1. Verify your contracts on block explorers
  2. Learn about upgrading contracts using the UUPS pattern
  3. Review contract architecture to understand the system

Build docs developers (and LLMs) love

Get started for freeTalk to us