Goldsky makes it easy to index smart contracts with a powerful no-code subgraph configuration system. Using the interactive CLI wizard, you can deploy a fully working subgraph in minutes.
Prerequisite Make sure you’re authenticated via:
goldsky login
Start the Goldsky wizard:
goldsky subgraph initYou’ll be prompted to enter a name and version:
Subgraph name: my-xrplevm-subgraph
Subgraph version: 1.0.0Set the target path where all configuration files will be saved:
Subgraph path: ~/my-subgraphs/my-xrplevm-subgraph/1.0.0You may skip this step to allow Goldsky to fetch ABI files automatically:
Contract ABI source: (leave blank)Provide the smart contract address:
Contract address: <your-contract-address>Select the network: choose XRPL EVM (Mainnet) or XRPL EVM Testnet from the list the wizard shows.
Set the start block (autodetected or manually entered). Use the block in which your contract was deployed, which you can find on the XRPL EVM Explorer:
Start block: <deployment-block>For XRPL EVM Goldsky supports subgraphs on XRPL EVM Mainnet and Testnet. See Goldsky's XRPL EVM Sidechain page.
Provide a human-readable name:
Contract name: MyContractTo also index function calls:
Enable subgraph call handlers? YesReview your setup:
Proceed with subgraph initialization? Yes
Proceed with subgraph build? YesDeploy to Goldsky’s indexing service:
Proceed with subgraph deploy? YesYou’ll receive links like:
Dashboard:
https://app.goldsky.com/.../dashboard/subgraphs/my-xrplevm-subgraph/1.0.0GraphiQL API:
https://api.goldsky.com/api/public/.../subgraphs/my-xrplevm-subgraph/1.0.0/gn
After deployment, test your subgraph using GraphiQL:
Entity names follow your contract's events. For example, if your contract emits an ERC-20 Transfer event:
query LatestTransfers($count: Int = 5) {
transfers(first: $count, orderBy: block_number, orderDirection: desc) {
id
block_number
transactionHash_
timestamp_
from
to
value
}
}To automate deployment (e.g., for CI pipelines):
goldsky subgraph init my-xrplevm-subgraph/1.0.0 \
--contract <your-contract-address> \
--network <xrpl-evm-network> \
--start-block <deployment-block> \
--contract-name MyContract \
--call-handlers \
--deployReplace <xrpl-evm-network> with the XRPL EVM network name exactly as the interactive wizard lists it.
| Flag | Description |
|---|---|
--target-path | Set a custom path for the subgraph config |
--force | Overwrite existing files |
--from-config | Use existing config as a template |
--abi | Provide local ABI source |
--contract | Contract address(es) to index |
--network | Network(s) to index |
--start-block | Block number to start indexing from |
--contract-name | Set custom contract name |
--description | Set subgraph description |
--call-handlers | Enable indexing of function calls |
--build | Trigger build step automatically |
--deploy | Trigger deployment after build |