Connect via RPC and Send Transactions

Connect through RPC

The Public RPC URL on the detail page is the entry point for this TestNet. Use it as the RPC endpoint in a wallet, script, or tool such as Foundry. Calls and transactions sent there run only on this TestNet.

For example, this Foundry command reads the current block number:

cast block-number -r <YOUR_RPC_URL>

Replace <YOUR_RPC_URL> with the URL copied from the detail page. Continue to follow normal key-management practices: a TestNet does not spend real funds, but production keys should never be written into scripts or logs.

Set a balance (Cheat Method)

Cheat Method

Call hardhat_setBalance to set any address's native-token balance out of thin air. The first argument is the target address, and the second is the balance in hexadecimal Wei.

cast rpc hardhat_setBalance \
  0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 \
  "0x1000000000000000000000" \
  -r <YOUR_RPC_URL>

This changes state only inside the current Virtual TestNet. It does not fund the address on the source chain.

Send a transaction

Send a transaction just as you would on a real EVM network. The example below uses Foundry cast to call deposit() on the Ethereum WETH contract with 1 ETH. The example private key should be used only on an isolated test network and involves no real funds.

cast send 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 "deposit()" \
  --value 1ether \
  --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 \
  -r <YOUR_RPC_URL>

Use hardhat_setBalance first to give the test account enough balance. Never use a production private key in a Virtual TestNet, script, or log.

Deploy and verify contracts

You can also send other transactions from a wallet, call contracts from a script, deploy a contract, or replay test steps. Sent requests appear in Operations on the detail page.

To verify a deployed contract, copy the Verify Contract URL from the detail page and use it as the custom verifier URL in your verification tool. Once verified, keep using the TestNet RPC to query or call the contract.

Inspect results

Operations records balance changes, time changes, and RPC requests. Records with a transaction hash can open directly in Skylens. The page carries the current TestNet parameter, so it shows execution against the fork rather than the matching mainnet transaction.

The statistics summary shows total requests, successes, failures, and success rate. When a request fails, find it in Operations first, then open its transaction to inspect the error, balance changes, and call trace.