# Blockops

- [Welcome to Blockops](https://docs.blockops.network/welcome.md): Core banking infrastructure for digital assets.
- [Quickstart: first wallet and transaction](https://docs.blockops.network/get-started/first-wallet-and-transaction.md): Create an MPC wallet in the sandbox, receive test funds, and send a governed withdrawal.
- [What is Blockops?](https://docs.blockops.network/overview/what-is-blockops.md): Core banking infrastructure for digital assets: what the platform is, how it secures keys, and why it is built the way it is.
- [Platform architecture](https://docs.blockops.network/overview/platform-architecture.md): How the wallet API, the MPC signing cluster and the chain operations layer fit together, and where authority lives in each.
- [Core concepts](https://docs.blockops.network/overview/core-concepts.md): The objects the platform works with (workspaces, wallets, assets, withdrawals, policies, approvals, API keys and webhooks) and how they relate.
- [Deployment models](https://docs.blockops.network/overview/deployment-models.md): Managed, hybrid and self-hosted deployments, and who holds the key shares in each.
- [How the platform is secured](https://docs.blockops.network/security/how-the-platform-is-secured.md): The trust boundaries of the wallet platform: what each one checks, and what a single failure can and cannot do.
- [Who holds the keys](https://docs.blockops.network/security/who-holds-the-keys.md): Where wallet key shares live under each deployment model, and what Blockops can and cannot do with them.
- [Threshold signing with citadel-core](https://docs.blockops.network/security/threshold-signing.md): How citadel-core generates keys as shares, signs with a threshold of nodes, protects the shares, and reshares them to a new set of nodes.
- [Access control](https://docs.blockops.network/security/access-control.md): Roles for people, scopes for API keys, and the approval controls that separate initiating a transaction from approving it.
- [Continuity and recovery](https://docs.blockops.network/security/continuity-and-recovery.md): What is backed up, how a failed signing node is restored without exposing key material, and how the platform behaves during partial failure.
- [Compliance & assurance](https://docs.blockops.network/security/compliance-and-assurance.md): The control framework behind the platform, what is mapped to which standard, and what is and is not certified.
- [MPC Wallet Infrastructure](https://docs.blockops.network/wallets/overview.md): Create wallets, receive and send funds, enforce policy and approvals, and receive signed events through an API built for server-to-server use and a console for the people who govern it.
- [Wallets & accounts](https://docs.blockops.network/wallets/wallets-and-accounts.md): Create an MPC wallet, attach assets to get deposit addresses, receive funds, and read balances.
- [Transactions & signing](https://docs.blockops.network/wallets/transactions-and-signing.md): Request a withdrawal, follow it from request through approval, signing, broadcast and confirmation, and sign digests directly.
- [Policies & approvals](https://docs.blockops.network/wallets/policies-and-approvals.md): Workspace controls on the movement of funds: approval requirements, dual control, whitelists, limits, and the kill switch.
- [Webhooks & events](https://docs.blockops.network/wallets/webhooks-and-events.md): Register HTTPS endpoints, verify signed deliveries, and the full catalogue of wallet, deposit, withdrawal and signing events.
- [Reporting & audit trail](https://docs.blockops.network/wallets/reporting-and-audit.md): Transaction history and export, balances and analytics, and the audit log of who did what in the workspace.
- [Supported networks & assets](https://docs.blockops.network/overview/supported-networks.md): The networks each Blockops product supports, and guides for connecting to them.
- [Automate deposits](https://docs.blockops.network/solutions/payments/automate-deposits.md): Give every customer a deposit address, detect incoming funds automatically, and reconcile them without polling.
- [Automate payments](https://docs.blockops.network/solutions/payments/automate-payments.md): Send payouts from a treasury wallet under policy, with a service key that can do nothing else.
- [Accept cryptocurrencies](https://docs.blockops.network/solutions/custody/accept-cryptocurrencies.md): Receive digital assets into an institution's treasury with addresses whose keys no single party holds.
- [Govern wallet access](https://docs.blockops.network/solutions/custody/govern-wallet-access.md): Decide who can see, configure and move funds, enforce it with roles, scoped keys and approval groups, and prove it from the audit log.
- [Embed user wallets](https://docs.blockops.network/solutions/custody/embed-user-wallets.md): Give each of your users a wallet inside your product, operated by your backend under your policies, with keys held as MPC shares.
- [Define treasury policies](https://docs.blockops.network/solutions/compliance/define-treasury-policies.md): Turn a written treasury policy into limits, destination rules and approval thresholds the platform enforces on every withdrawal.
- [Build programmable approval policies](https://docs.blockops.network/solutions/compliance/build-programmable-approval-policies.md): Design approval tiers with M-of-N groups, route held withdrawals to approvers, and integrate approvals with your own workflow tools.
- [Self-hosted signing](https://docs.blockops.network/self-hosted/overview.md): What you run when your institution operates its own citadel-core signing nodes, and what Blockops provides.
- [Install on Linux hosts (systemd)](https://docs.blockops.network/self-hosted/install-systemd.md): Deploy a production citadel-core cluster as hardened systemd services on three or more Linux hosts.
- [Install on Kubernetes](https://docs.blockops.network/self-hosted/install-kubernetes.md): Deploy citadel-core signing nodes as a StatefulSet with secrets, persistent storage, probes and network policy.
- [Install on AWS ECS Fargate](https://docs.blockops.network/self-hosted/install-ecs.md): Run citadel-core signing nodes as Fargate tasks with Secrets Manager, S3 and EFS.
- [Configuration reference](https://docs.blockops.network/self-hosted/configuration.md): Every citadel-core configuration key, environment override, command-line flag and CLI command.
- [Operate a cluster](https://docs.blockops.network/self-hosted/operate.md): Health, logs, backups, upgrades, adding nodes and recovering a lost node in a self-hosted citadel-core cluster.
- [Security checklist](https://docs.blockops.network/self-hosted/security-checklist.md): The controls a self-hosted citadel-core deployment must have in place before it holds production key shares.
- [Blockchain Infrastructure](https://docs.blockops.network/blockchain-infrastructure/overview.md): The infrastructure services under the wallet platform: RPC endpoints, node operations, monitoring, indexing and dedicated rollups.
- [Getting started with the Blockchain API](https://docs.blockops.network/get-started/overview.md): Create an account, get an API key, and make your first JSON-RPC request.
- [How to create an account](https://docs.blockops.network/get-started/create-your-account.md): Sign up with Google, GitHub or an email address.
- [Blockchain API](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/overview.md): JSON-RPC endpoints over HTTP and WebSocket for 28 networks, with per-project API keys.
- [Endpoints, keys & authentication](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/endpoints-and-authentication.md): Generate HTTP and WebSocket endpoints, authenticate with your API key, and rotate it.
- [Rate limits & error codes](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/rate-limits-and-errors.md): Requests-per-second limits for public and private endpoints, and the error codes the API returns.
- [Common RPC methods & examples](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/rpc-methods-and-examples.md): Common JSON-RPC methods, with cURL, wscat and @polkadot/api examples.
- [Ethereum](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/ethereum.md): Endpoints and example requests for Ethereum Mainnet and Sepolia.
- [Base](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/base.md): Endpoints and example requests for Base Mainnet and Base Sepolia.
- [Optimism](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/optimism.md): Endpoints and example requests for Optimism Mainnet and Optimism Sepolia.
- [Polkadot](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/polkadot.md): Public and private endpoints and example requests for Polkadot.
- [Kusama](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/kusama.md): Public and private endpoints and example requests for Kusama.
- [Westend](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/westend.md): Endpoints and example requests for the Westend test network.
- [Gargantua](https://docs.blockops.network/blockchain-infrastructure/blockchain-api/networks/gargantua.md): Endpoints and example requests for Gargantua, the Hyperbridge test network.
- [Mission Control](https://docs.blockops.network/blockchain-infrastructure/node-operations/overview.md): Deploy and manage blockchain nodes across cloud providers and your own servers.
- [Node Deployment](https://docs.blockops.network/blockchain-infrastructure/node-operations/deploy-a-node.md): Deploy a node with Mission Control on GCP, AWS, Cherry Servers or bare metal.
- [Private Servers Deployment](https://docs.blockops.network/blockchain-infrastructure/node-operations/deploy-to-your-own-servers.md): Connect a server you operate to Blockops over an SSH tunnel and deploy a node to it.
- [Telescope](https://docs.blockops.network/blockchain-infrastructure/monitoring-and-alerting.md): Metrics, logs, uptime checks and alerts for deployed nodes.
- [Pulsar](https://docs.blockops.network/blockchain-infrastructure/indexing.md): Managed SubQuery and The Graph indexers with GraphQL endpoints.
- [Rollup Deployment](https://docs.blockops.network/blockchain-infrastructure/rollups.md): Deploy a dedicated OP Stack rollup that settles to Ethereum.
- [Glossary](https://docs.blockops.network/overview/glossary.md): Terms used across the Blockops documentation.
- [Frequently asked questions](https://docs.blockops.network/resources/faq.md): Answers to common questions about Blockops, the Blockchain API, Mission Control and Telescope.
- [Blog](https://docs.blockops.network/resources/blog.md): Product updates and partnership announcements from the Blockops blog.
- [Support](https://docs.blockops.network/get-started/support.md): How to reach Blockops support and the community.
- [Wallet API](https://docs.blockops.network/api-reference/introduction.md): Base URL, authentication and conventions for the Blockops Wallet API.
- [List supported networks](https://docs.blockops.network/api-reference/catalog/list-supported-networks.md): Returns the network catalog.
- [Get supported network detail](https://docs.blockops.network/api-reference/catalog/get-supported-network-detail.md): Returns one network catalog entry.
- [List supported assets](https://docs.blockops.network/api-reference/catalog/list-supported-assets.md): Asset IDs are catalog UUIDs. They are not token contract addresses.
- [List wallets for a workspace](https://docs.blockops.network/api-reference/wallets/list-wallets-for-a-workspace.md)
- [Create an MPC wallet](https://docs.blockops.network/api-reference/wallets/create-an-mpc-wallet.md): Starts asynchronous wallet creation. In dry-run mode this only persists operation state and validates the key-generation request. In keygen mode it publishes an key-generation request and the operation is later completed by the keygen result consumer. Stale keygen requests can be failed by operator-…
- [Get wallet detail](https://docs.blockops.network/api-reference/wallets/get-wallet-detail.md): Returns wallet detail.
- [Get wallet detail through SDK web3 alias](https://docs.blockops.network/api-reference/wallets/get-wallet-detail-through-sdk-web3-alias.md): Compatibility alias for wallet-detail calls.
- [Get wallet creation status](https://docs.blockops.network/api-reference/wallets/get-wallet-creation-status.md)
- [Attach an asset and derive a deposit address](https://docs.blockops.network/api-reference/wallets/attach-an-asset-and-derive-a-deposit-address.md): Attaches a catalog asset to an MPC wallet. The service derives the address from stored wallet public-key metadata, the configured chain code, and a server-selected derivation path. Client-provided derivation paths are not accepted.
- [List wallet assets](https://docs.blockops.network/api-reference/wallets/list-wallet-assets.md): Lists assets attached to a wallet.
- [Get a wallet deposit address](https://docs.blockops.network/api-reference/wallets/get-a-wallet-deposit-address.md)
- [Get a wallet address by address type](https://docs.blockops.network/api-reference/wallets/get-a-wallet-address-by-address-type.md): Compatibility alias for address-by-type callers; returns the same deposit-address state.
- [Get SDK transaction status](https://docs.blockops.network/api-reference/transactions/get-sdk-transaction-status.md): Compatibility alias for transaction status calls; backed by the withdrawal record.
- [List transaction activity for a workspace](https://docs.blockops.network/api-reference/transactions/list-transaction-activity-for-a-workspace.md): Returns withdrawal activity and deposit activity from the transaction ledger.
- [Export transaction activity for a workspace](https://docs.blockops.network/api-reference/transactions/export-transaction-activity-for-a-workspace.md): CSV export of the same withdrawal and deposit activity returned by the workspace transaction list.
- [Get transaction detail for a workspace](https://docs.blockops.network/api-reference/transactions/get-transaction-detail-for-a-workspace.md): Resolves transaction detail by transaction id, row id, or transaction hash across withdrawals and persisted deposits.
- [List transaction activity for a wallet](https://docs.blockops.network/api-reference/transactions/list-transaction-activity-for-a-wallet.md): Returns withdrawal activity and deposit activity from the transaction ledger.
- [Create a constrained generic signing request](https://docs.blockops.network/api-reference/signing/create-a-constrained-generic-signing-request.md): SDK-compatible raw signing boundary for prebuilt 32-byte digests. The route is and signing is explicitly enabled. It persists an operation_type=generic signing request. It does not construct transactions or bypass future policy/session governance. Workspaces with active approval policies must use /a…
- [Create a constrained generic signing request](https://docs.blockops.network/api-reference/signing/create-a-constrained-generic-signing-request-1.md): Compatibility alias for SDK requestSign calls. Semantics match /api/v1/web3/transaction/{wallet_id}/signRaw and it is deprecated for policy-governed tenants in favor of /api/v1/web3/transaction/{wallet_id}/signTyped.
- [Create a typed signing request](https://docs.blockops.network/api-reference/signing/create-a-typed-signing-request.md): Policy-evaluable signing route for enterprise tenants. The request must include recipient, amount, asset, and chain semantics in addition to the signing digest. Matching approval policies create a pending approval request instead of publishing immediately.
- [Get generic signing status](https://docs.blockops.network/api-reference/signing/get-generic-signing-status.md): Reads only generic signing requests for the wallet-bound caller.
- [Get wallet balance for one asset](https://docs.blockops.network/api-reference/balances/get-wallet-balance-for-one-asset.md)
- [Get wallet balance overview](https://docs.blockops.network/api-reference/balances/get-wallet-balance-overview.md)
- [Request a withdrawal](https://docs.blockops.network/api-reference/withdrawals/request-a-withdrawal.md): Provider automation path for withdrawals. With signing disabled this creates an idempotent dry-run operation. With signing enabled it plans a native EVM transaction from trusted wallet metadata and persists a signing request. Signing, signing result persistence, EVM broadcast, and receipt reconcilia…
- [Get withdrawal detail](https://docs.blockops.network/api-reference/withdrawals/get-withdrawal-detail.md)
- [List withdrawals for a workspace](https://docs.blockops.network/api-reference/withdrawals/list-withdrawals-for-a-workspace.md)
- [Count withdrawals for a workspace](https://docs.blockops.network/api-reference/withdrawals/count-withdrawals-for-a-workspace.md)
- [List withdrawals for a wallet](https://docs.blockops.network/api-reference/withdrawals/list-withdrawals-for-a-wallet.md)
- [Count withdrawals for a wallet](https://docs.blockops.network/api-reference/withdrawals/count-withdrawals-for-a-wallet.md)
- [Get webhook verification public key](https://docs.blockops.network/api-reference/webhooks/get-webhook-verification-public-key.md): Returns the base64-encoded Ed25519 public key used by integrators to verify signed Blockops webhook payloads.
- [List workspace webhooks](https://docs.blockops.network/api-reference/webhooks/list-workspace-webhooks.md)
- [Create a workspace webhook](https://docs.blockops.network/api-reference/webhooks/create-a-workspace-webhook.md)
- [Update a workspace webhook](https://docs.blockops.network/api-reference/webhooks/update-a-workspace-webhook.md)
- [Delete a workspace webhook](https://docs.blockops.network/api-reference/webhooks/delete-a-workspace-webhook.md)
- [List webhook delivery logs](https://docs.blockops.network/api-reference/webhooks/list-webhook-delivery-logs.md)
- [Requeue a webhook delivery](https://docs.blockops.network/api-reference/webhooks/requeue-a-webhook-delivery.md)
- [Get webhook delivery stats](https://docs.blockops.network/api-reference/webhooks/get-webhook-delivery-stats.md)
- [List workspace API keys](https://docs.blockops.network/api-reference/api-keys/list-workspace-api-keys.md): Admin-only route. Returns scoped DB-backed API keys for a workspace without exposing their signing secrets.
- [Create a workspace API key](https://docs.blockops.network/api-reference/api-keys/create-a-workspace-api-key.md): Admin-only route. Creates a DB-backed scoped API key. The `api_secret` is returned only in this create response.
- [Revoke a workspace API key](https://docs.blockops.network/api-reference/api-keys/revoke-a-workspace-api-key.md): Admin-only route. Revokes a DB-backed scoped API key.
- [List workspace audit events](https://docs.blockops.network/api-reference/audit/list-workspace-audit-events.md): Admin-only read surface for audit events. This route reads durable audit event state; producers for sensitive actions are added as each governance and custody mutation is audited.

## OpenAPI Specs

- [openapi](/api-reference/openapi.yaml)