Skip to main content

Blockops

Blockops provides core banking infrastructure for digital assets: an MPC wallet platform built for financial institutions, and the blockchain infrastructure it runs on: RPC endpoints, managed nodes, indexing, monitoring and dedicated rollups.
Follow Getting started: create an account, create a project, and make your first request. Each product then has its own guide.
Email hello@blockops.network, use the support icon at the bottom right of the dashboard, or ask the community on Discord. See Support.

Accounts and access

With Google, GitHub, or an email address. Email sign-up asks for a business name, your name, an email address and a password, and requires email verification. See Create your account.
Rotate it. Open the project in the dashboard and use Rotate Key; the old key stops working immediately. See Endpoints, keys & authentication.

Blockchain API

The full list is on Supported networks & assets, with a connection guide for each network that has one.
With your project’s API key, either in the authorization: APIKEY <key> header or as the ?api_key=<key> query string. Both HTTP and WebSocket endpoints accept either form.
Public endpoints allow 50 requests per second and are intended for testing only. Private endpoints, which use your API key, allow 1000 requests per second. If you need more, contact support. See Rate limits & error codes.
The API returns standard HTTP status codes: 401 for a missing or invalid key, 404 for an unknown route, 429 when you exceed the request limit, and 500 for a server-side error. Network-specific errors come back in the JSON-RPC response body. See Rate limits & error codes.

Mission Control

The Blockops service for deploying and managing blockchain nodes. Nodes can run on Google Cloud, AWS, Cherry Servers, bare metal, or a private server you connect over an SSH tunnel. See Node operations.
One. You can start with a single node and add more later.
Yes. Bare-metal servers are reached over SSH; servers without inbound access are connected through an outbound SSH tunnel. See Deploy to your own servers.

Telescope

Metrics, logs, uptime and alerts for deployed nodes, through a Node Health Dashboard for individual nodes and a Network Dashboard for a network. Metrics are collected by push, where Blockops exposes an endpoint for you, or by pull from a datasource you provide. See Monitoring & alerting.
Alerts are created on a dashboard (metrics or logs) or on an uptime monitor and are delivered to the contact points you configure.
Yes. Each node you deploy can be added to Telescope, and the Network Dashboard covers a network as a whole.

Pulsar and Rollups

A managed indexing service. You deploy SubQuery or The Graph indexers and query them through a GraphQL endpoint, without running the indexer infrastructure yourself. See Indexing.
A dedicated OP Stack Layer 2 chain that settles to Ethereum. Testnet rollups deploy to Ethereum Sepolia and are self-serve; mainnet rollups settle to Ethereum Mainnet and are set up with the Blockops team. See Rollups.
Still have a question? Email hello@blockops.network.