Skip to content
Pre-alphaDirect is under active development.
directrpc

Direct RPC · For providers

Your infrastructure.
New revenue.

Earn from the blockchain infrastructure you already operate. Install Direct, connect your node and set your prices in minutes. Peer-to-peer connections work through NAT and firewalls without exposing your node or configuring port forwarding.

01 Your offering

You run the infrastructure.
You set the price.

Your node, its configuration and its operation stay with you. The Direct gateway connects that infrastructure to consumers without requiring a separate integration with each application.

Specify the network and set your price per request. Direct automatically detects what your node can serve and makes those capabilities available to consumers.

Talk to us about providing RPC

Your existing nodeKeep running your infrastructure
Direct gatewayCapabilities detected automatically

02 What you can offer

Different nodes.
Different kinds of work.

Direct automatically detects your node’s capabilities and announces them to consumers, so applications can discover the services your infrastructure supports.

Current activity

Blockchain data.

Serve balances, blocks, transactions and other RPC queries for the network your node follows.

Historical access

History and archive state.

Offer older chain data and state where your node retains it. Full chain history and archive state are assessed separately.

Execution details

Tracing.

Make supported debug and tracing capabilities available for applications that need to inspect execution.

Live updates

Subscriptions.

Provide access to supported blockchain events through a WebSocket connection to your node.

Capabilities depend on the network and node configuration. Direct checks what your node supports before making it available to serve those requests.

03 Serving a request

Your infrastructure
does the work.

The gateway connects your offering to the market. Requests reach the node you operate, and served usage is recorded as work is completed.

  1. 01

    An offering is selected.

    The consumer’s gateway finds a provider that matches the request and its purchasing preferences.

  2. 02

    Your gateway receives it.

    The request arrives over the peer-to-peer connection and is forwarded to your node.

  3. 03

    Your node responds.

    Your infrastructure performs the work. The response travels back through the gateways to the application.

  4. 04

    Usage is recorded.

    The provider gateway records served usage for settlement.

04 Joining the market

Ready to offer
your capacity?

Run the Direct gateway as close to your node as possible. The same machine is ideal; otherwise, prefer the same data center to keep latency low. Faster responses help your offering attract more traffic.

Offerings must meet the service’s requirements before consumers can select them. Direct continues checking health, integrity and performance while providers serve requests.

Talk to us about providing RPC