Module 4 - Set Configuration
Example JSON for configuring RPC URL, rollups, and payers.
Update rome-sdk/example.config.json
to specify Solana RPC, Rollup IDs, and Solana Payer details.
{ "rpc_url": "https://node3.devnet-us-sol-api.devnet.romeprotocol.xyz", // Replace with your RPC path "commitment": "confirmed", "rollups": { "121212": "RPDwFyw4ekzzgyJfSrVmJgmfi51ovyqzLckYGchLpKX", // Rome Devnet Esquiline "121213": "RPDwFyw4ekzzgyJfSrVmJgmfi51ovyqzLckYGchLpKX" // Rome Devnet Subura }, "payers": [ { "payer_keypair": "/Users/username/.config/solana/id.json", // Replace with your Solana keypair path "number_holders": 64 } ]}
Solana RPC URL
Section titled “Solana RPC URL”The rpc_url points to Rome’s Devnet Solana node.
Rollup Chain IDs
Section titled “Rollup Chain IDs”The rollups field maps from Chain ID to Solana Program ID, which is the same for all rollups so just use the Solana Program ID used above.
Specify all Chain IDs you want to work with. Rome Devnet Esquiline (121212) and Rome Devnet Subura (121213) are included above.
Solana Keypair
Section titled “Solana Keypair”Make sure to specify a valid Solana payer keypair. Number of holders determines how many transactions can be run in parallel. Payers pay SOLs to execute Solana transactions.
If you don’t have a Solana keypair, generate it using solana-keygen new -o /Users/username/.config/solana/id.json
. Make sure to replace your username.
Fund your Solana keypair on Solana Devnet using solana airdrop 1 -ud
.