RPC Archive Nodes

Access reliable, high-performance blockchain data with Sentio's integrated RPC Archive Nodes. Query complete historical blockchain data, monitor usage in real-time, and streamline your dApp development workflow—all within the Sentio platform.

Overview

Sentio RPC Archive Nodes provide direct access to full historical blockchain data across multiple networks. With transparent pay-per-request billing and comprehensive monitoring, you can optimize your blockchain interactions while maintaining complete visibility into costs and performance.

Supported Networks

Ethereum Mainnet
Movement Testnet & Mainnet
Aptos Testnet & Mainnet

Getting Started

Creating Your First RPC Node

Access RPC Nodes
Navigate to "RPC Nodes" in the left sidebar of the Sentio platform.
Create New Node
Click "+ Create RPC Node" in the top-right corner of the RPC Node List page.
Configure Network
In the "Create RPC Node" dialog:
- Select "Choose Network" dropdown
- Pick your target blockchain network (e.g., Ethereum Mainnet, Aptos Testnet)
Deploy Node
Click "Create Node" to provision your RPC Archive Node.

Your new node will appear in the RPC Node List once provisioned.

Managing Your RPC Nodes

Node Overview

The RPC Node List provides a comprehensive view of all your nodes with key information:

Column	Description
Network	Target blockchain network
Fork ID	Forked network identifier (if applicable) - see forks documentation
ID	Unique node identifier
Status	Current operational status
Last Called	Timestamp of most recent API call
Total Calls	Cumulative request count
Creator	Node creator
RPC URL	Endpoint preview

Node Configuration

Click any node to access its detailed configuration page, where you can:

Copy Full Endpoint URL: Your unique RPC endpoint for integration with Web3 applications, SDKs (Ethers.js, Aptos SDK), or direct API calls
Toggle Node Status: Enable or disable your RPC node as needed

Connecting over gRPC

Networks that expose a native gRPC API (currently Sui Mainnet and Sui Testnet) can also be reached over gRPC. When a network supports it, the node page shows a gRPC Endpoint and a grpcurl example next to the HTTP endpoint.

gRPC uses a different addressing scheme from JSON-RPC, because the URL path of a gRPC request is always the method name (for example /sui.rpc.v2.LedgerService/GetServiceInfo):

	JSON-RPC	gRPC
Endpoint	`https://sui.rpc.sentio.xyz/<your-node-id>`	`sui.rpc.sentio.xyz:443` (TLS)
Network	Selected by the subdomain	Selected by the subdomain, e.g. `sui` or `sui-testnet`
Node ID	Part of the URL path	Sent as the `x-endpoint-id` request metadata header

Do not append the node ID to the gRPC endpoint. A request such as sui.rpc.sentio.xyz/<your-node-id> fails with UNIMPLEMENTED; the node ID must be sent in the x-endpoint-id header instead.

Requests without the x-endpoint-id header are served as anonymous requests: they are not attributed to your node, so they do not show up in its usage, logs, or cost.

Server reflection is enabled, so grpcurl can discover services without local proto files:

# List the available services
grpcurl -H "x-endpoint-id: <your-node-id>" sui.rpc.sentio.xyz:443 list

# Call a method
grpcurl -H "x-endpoint-id: <your-node-id>" -d '{}' \
  sui.rpc.sentio.xyz:443 sui.rpc.v2.LedgerService/GetServiceInfo

In application code, attach the header to every call. For example, in Go:

conn, err := grpc.NewClient("sui.rpc.sentio.xyz:443",
	grpc.WithTransportCredentials(credentials.NewTLS(&tls.Config{})))
if err != nil {
	return err
}
ctx = metadata.AppendToOutgoingContext(ctx, "x-endpoint-id", "<your-node-id>")
info, err := rpcv2.NewLedgerServiceClient(conn).GetServiceInfo(ctx, &rpcv2.GetServiceInfoRequest{})

Streaming methods such as SubscriptionService/SubscribeCheckpoints are supported as well.

Common errors:

gRPC status	Meaning
`NOT_FOUND` (5) `rpc node <id> not found`	The node ID is wrong, or the node is disabled
`NOT_FOUND` (5) `no grpc endpoint configured for chain`	The network does not offer gRPC; use its JSON-RPC endpoint
`PERMISSION_DENIED` (7)	The network is not enabled for this node
`UNIMPLEMENTED` (12)	The request path is not a gRPC method, usually because the node ID was put in the URL

Monitoring & Analytics

Performance Dashboard

Each RPC node includes a comprehensive monitoring dashboard with real-time metrics and historical analysis.

Summary Metrics

Monitor your node's key performance indicators:

Total Requests: Request volume within selected timeframe
Error Rate: Failed request count and percentage
Success Rate: Percentage of successful requests
Total Cost: Accumulated costs in Sentio Units

Performance Analysis

Detailed performance breakdowns including:

Request Time Statistics: Average, median, minimum, and maximum total response times (including network latency)
Execution Time Statistics: Processing time metrics for server-side request handling

Time Series Analytics

Visualize usage patterns and performance trends over customizable time intervals:

1 minute, 5 minutes, 15 minutes
1 hour, 1 day intervals

Request Logs

Access detailed request records for debugging and analysis by clicking "View Request Logs".

Billing & Cost Management

Pricing Model

Pay-Per-Request: Only pay for actual API calls made
Transparent Costs: Real-time cost tracking in Sentio Units
No Setup Fees: Start using immediately with no upfront costs

Cost Monitoring

Track expenses through the Summary Metrics dashboard, with detailed breakdowns available for budget planning and optimization.

Next Steps

Ready to get started? Create your first RPC Archive Node and begin leveraging Sentio's robust blockchain infrastructure for your development needs. With full historical data access, transparent monitoring, and flexible billing, you have everything needed for professional blockchain development.

🖥️ RPC Nodes