Skip to main content

​
RPC addon

List of available networks and their aliases is available on the reference page. SQD Cloud provides a built-in RPC service. The service is available as an addon to all squids deployed to the Cloud, although playground squids only have access to a limited number of calls. Professional organizations do not have that limitation and can access their RPC endpoints from outside of the Cloud. Enable the RPC add-on in the manifest like this: 
deploy:
  addons:
    rpc:
      - eth-goerli.http

​
Processor configuration

With the add-on successfully enabled, your squid will get a unique proxied endpoint to the requested network. SQD Cloud will make its URL available to the deployed squid at the RPC_$\{Upper(network)\}_$\{Upper(protocol)\} environment variable. Assert it to avoid compilation errors. We also recommend rate limiting RPC addon requests on the processor side to the same rate as was used in the manifest: 
import \{assertNotNull\} from '@subsquid/util-internal'

processor.setRpcEndpoint({
  // dash in "eth-goerli" becomes an underscore
  url: assertNotNull(process.env.RPC_ETH_GOERLI_HTTP),
  rateLimit: 10
})

​
External access

Professional organizations can access their RPC proxies from outside of the SQD Cloud. Among other things, this enables a development process that uses the service for both local and Cloud runs transparently. Here an example configuration for Ethereum Mainnet:

​
Pricing

RPC addon requests are priced at a flat rate, with substantial packages included for free for all organization types. Pricing does not depend on the call method.