RPC
Send JSON-RPC requests over HTTPS. Bitcoin endpoints do not support WebSocket. Archive data is available: every block since genesis, through getblock.
- HTTPS
-
https://rpc.graphops.xyz/v1/bitcoin/signet
Bitcoin Signet RPC
Call Bitcoin Core-compatible JSON-RPC methods on Bitcoin Signet through GraphOps RPC over HTTPS.
GraphOps services on Bitcoin Signet
One API key from your organization can include every service you use, and all of them draw from the organization's credit balance.
Bitcoin Signet network details
Use these identifiers to name Bitcoin Signet in requests, manifests and package configuration.
- RPC network
-
signet - CAIP-2 network ID
-
bip122:00000008819873e925422c1ff0f99f7c - Network type
- Testnet
- Block explorer
- mempool.space(opens in a new tab)
Make a first Bitcoin Signet request
This request reads Bitcoin Signet chain information with getblockchaininfo.
Create an API key that includes RPC in your organization and export it as GRAPHOPS_API_KEY.
The example sends it in the Authorization header.
RPC quickstart(opens in a new tab) Authentication(opens in a new tab)
Prerequisites
Set GRAPHOPS_API_KEY to your GraphOps API key.
Run the command in a terminal with curl installed.
CLI · curl
curl --fail-with-body --silent --show-error 'https://rpc.graphops.xyz/v1/bitcoin/signet' \
-H "Authorization: Bearer ${GRAPHOPS_API_KEY}" \
-H 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "getblockchaininfo",
"params": []
}'
export {};
const response = await fetch("https://rpc.graphops.xyz/v1/bitcoin/signet", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.GRAPHOPS_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
jsonrpc: "2.0",
id: 1,
method: "getblockchaininfo",
params: [],
}),
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
console.log(JSON.stringify(await response.json()));
import json
import os
import requests
response = requests.post(
"https://rpc.graphops.xyz/v1/bitcoin/signet",
headers={"Authorization": f"Bearer {os.environ['GRAPHOPS_API_KEY']}"},
json={
"jsonrpc": "2.0",
"id": 1,
"method": "getblockchaininfo",
"params": [],
},
timeout=30,
)
response.raise_for_status()
print(json.dumps(response.json()))
package main
import (
"bytes"
"fmt"
"io"
"log"
"net/http"
"os"
"time"
)
func main() {
body := bytes.NewBufferString(`{"jsonrpc":"2.0","id":1,"method":"getblockchaininfo","params":[]}`)
request, err := http.NewRequest(http.MethodPost, "https://rpc.graphops.xyz/v1/bitcoin/signet", body)
if err != nil {
log.Fatal(err)
}
for name, value := range map[string]string{
"Authorization": "Bearer " + os.Getenv("GRAPHOPS_API_KEY"),
"Content-Type": "application/json",
} {
request.Header.Set(name, value)
}
response, err := (&http.Client{Timeout: 30 * time.Second}).Do(request)
if err != nil {
log.Fatal(err)
}
defer response.Body.Close()
result, err := io.ReadAll(response.Body)
if err != nil {
log.Fatal(err)
}
if response.StatusCode != http.StatusOK {
log.Fatalf("HTTP %s: %s", response.Status, result)
}
fmt.Println(string(result))
}
use reqwest::header::{HeaderMap, HeaderName};
use serde_json::{json, Value};
use std::{env, error::Error, time::Duration};
#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
let mut headers = HeaderMap::new();
for (name, value) in vec![
("Authorization", format!("Bearer {}", env::var("GRAPHOPS_API_KEY")?)),
] {
headers.insert(name.parse::<HeaderName>()?, value.parse()?);
}
let response = reqwest::Client::new()
.post("https://rpc.graphops.xyz/v1/bitcoin/signet".to_string())
.headers(headers)
.timeout(Duration::from_secs(30))
.json(&json!({"jsonrpc":"2.0","id":1,"method":"getblockchaininfo","params":[]}))
.send()
.await?
.error_for_status()?;
let result: Value = response.json().await?;
println!("{result}");
Ok(())
}
Pricing
Usage on Bitcoin Signet draws credits at the same rates as on every other network. Your monthly plan sets the price per credit.
Bitcoin Signet questions
- How does GraphOps identify Bitcoin Signet?
- Bitcoin Signet is a testnet. Its CAIP-2 network ID is
bip122:00000008819873e925422c1ff0f99f7c, and RPC endpoints name itsignetin their path. - What is the GraphOps Bitcoin Signet RPC endpoint?
- Send HTTPS JSON-RPC requests to
https://rpc.graphops.xyz/v1/bitcoin/signet. Authenticate with an API key from your organization that includes RPC, in theAuthorizationheader or as a route token at the end of the path. - Does Bitcoin Signet RPC support WebSocket?
- No. Bitcoin Signet RPC accepts JSON-RPC over HTTPS only.
- Does GraphOps Bitcoin Signet RPC serve archive data?
- Yes. Bitcoin Signet RPC keeps every block since genesis, so
getblockreturns any block.
Related networks
- Mainnet
Bitcoin Mainnet
bip122:000000000019d6689c085ae165831e93- RPC · archive
- Mainnet · Chain ID 1
Ethereum Mainnet
eip155:1- RPC · archive, tracing
- Subgraphs · managed indexing
- Substreams
- Testnet · Chain ID 11155111
Ethereum Sepolia
eip155:11155111- RPC · archive
- Subgraphs · managed indexing
- Mainnet · Chain ID 100
Gnosis
eip155:100- RPC · archive
- Subgraphs · managed indexing
Start building on Bitcoin Signet.
Create an organization, choose your monthly credits, then create an API key that includes the services you need.