What is Blockops?

​

What is Blockops?

Blockops is core banking infrastructure for digital assets. It gives financial institutions a single control plane for their digital asset operations: MPC-secured wallet infrastructure, governance policies and controls over every transaction, and a complete audit trail, delivered through one API and one console with institutional-grade security. At the core is threshold cryptography. A private key is never generated, stored or reconstructed as a whole. It exists only as shares held by independent signing nodes, and every signature requires a threshold of them to cooperate. That removes the single point of failure of a conventional private key, and it lets you decide where the shares live: with Blockops, in your own infrastructure, or split so that nothing moves without you.

​

Your core banking layer

A bank’s core holds the accounts, settles every movement of money, enforces mandates on each transaction and keeps the books. Products are built on top of it. Blockops is that layer for digital assets. Your product, customers, pricing and business logic stay with you. Blockops carries the infrastructure and the cryptography, so you add onchain money movement, tokenization and yield without building any of it.

• Keys are never a single point of failure. Each key is generated as shares and used without ever being assembled.
• Every transaction passes governance before it is signed. Limits, whitelists, approvals and the freeze are enforced by the platform, not the caller.
• You control where custody sits. The API, policies and audit trail are the same in every model.
• The infrastructure underneath is Blockops’ too. Signing, policy, orchestration, events and the node and RPC layer run as one platform.

​

Why choose Blockops?

• Custody on your terms. Choose who runs the signing nodes and holds the key shares, and change it later without moving funds:
  • Managed: Blockops operates every node and holds the shares. You integrate and govern.
  • Hybrid: you run one or more nodes in your own infrastructure. Nothing can be signed without your share.
  • Self-hosted: you run every node and hold every share. Blockops runs the control plane and never touches key material.
  See Deployment models.
• Governance that cannot be bypassed. Limits, whitelists and approvals are evaluated before any signature exists, and only a person in the console can approve. See Policies & approvals.
• Evidence for your reviewers. Every action is recorded with actor and time, every state change arrives as a signed event, and controls are mapped against CCSS, SOC 2 and ISO 27001. See Compliance & assurance.
• One platform down to the chain. RPC access across 28 networks, node operations, monitoring and indexing, operated by Blockops. See Blockchain Infrastructure.

​

Core concepts

​

MPC-secured wallets

A wallet is a key generated as shares across the signing cluster, never as a whole. Attaching an asset binds the wallet to a network and token and yields a server-derived deposit address; on EVM networks one address serves the native asset and its tokens. Wallets, assets, deposits and withdrawals are the objects everything else refers to. See Wallets & accounts.

​

Governance policies and controls

Every withdrawal passes through the workspace’s governance before it reaches the signing cluster: spend limits per transaction and per day, destination whitelists with a hold on new addresses, approval groups with M-of-N thresholds, dual control on configuration changes, and an emergency freeze that fails every withdrawal closed. See Policies & approvals.

​

Users and permissions

People hold workspace roles (owner, admin, member, viewer) and can be restricted to specific wallets. Systems hold scoped API keys, bound to wallets and IP ranges, with expiry and immediate revocation. Approval is a human action in the console; scopes are enforced on every request before policy runs. See Access control.

​

Audit logs

Sign-ins, policy and group changes, key and webhook management, approvals, rejections and freezes are recorded with actor and time, available in the console and through the API. Transaction history and CSV export cover every deposit and withdrawal, and Ed25519-signed webhooks deliver each state change to your systems. See Reporting & audit.

​

Get started