DOCSEARCHbyAlgolia
Submit Docs

Fireblocks API Reference

website·Indexed 40 days ago

https://developers.fireblocks.com

API documentation for the Fireblocks platform, featuring endpoints for managing API keys, audit logs, blockchain and asset registration, and specialized beta features including Compliance Orchestrator, Canton calls, and Blockchain Link.

Tokens
299.2K
Snippets
1.3K
Records
2.2K
Agent score
67%

What's inside Fireblocks

  1. Overview of the Fireblocks Network

    The Fireblocks Network is a peer-to-peer, institutional liquidity and transfer network consisting of over 1,500 liquidity providers, lending desks, and trading counterparties. It allows members to discover, connect, and settle transactions with other network members securely using specialized features exclusive to Network membership.

  2. Overview of Fireblocks x402 Protocol Implementation

    Fireblocks implements the open x402 protocol (specification available at x402.org), which defines the 402 handshake, the PaymentRequired body, and the roles of client, resource server, and facilitator. The Fireblocks facilitator follows x402 v2. While the protocol remains standard for interoperability with other x402 services, Fireblocks adds a settlement and custody layer where payments settle through a Fireblocks vault, ensuring raw private keys never leave Fireblocks and spending is governed by Fireblocks Policy rules.

  3. Overview of ERC721F and ERC1155F Collections API

    The Collections API is a convenience wrapper around the Tokenization API specifically for ERC721F (non-fungible) and ERC1155F (semi-fungible) tokens. It abstracts the complexity of deploying and linking NFT contracts, allowing developers to deploy, mint, burn, and manage tokens and their associated metadata within the Fireblocks ecosystem. These reference implementations are designed for compliance and scalable token management.

  5. Overview of Fireblocks Self-Custody Infrastructure features

    Fireblocks provides self-custody technology to secure digital assets using several core mechanisms:

    • MPC (Multi-Party Computation) technology: Eliminates single points of compromise by creating and encrypting private key shares in isolated environments across multiple parties. Signing occurs via rounds of computation without the shares ever meeting in one environment.
    • API Co-Signer: Allows for the automation of transaction approval and signing while maintaining custody.
    • Secure Hardware Enclaves: Protects private keys from unauthorized users or malicious software by storing them in secure hardware environments.
    • Key Backups: Provides users with backup copies of signing keys to ensure full control over funds.

  7. Overview of Fireblocks Wallet-as-a-Service (WaaS)

    Fireblocks Wallet-as-a-Service (WaaS) is an API-based solution that provides secure MPC (Multi-Party Computation) wallets. It allows developers to create, manage, and secure wallets for a large number of users without implementing the underlying security infrastructure. The service provides APIs capable of generating ECDSA and EdDSA signatures to sign transactions.

  8. Overview of Fireblocks Treasury Management capabilities

    Fireblocks Treasury Management provides a suite of tools to secure, govern, and operationalize fund operations for Web3 entities. Key capabilities include:

    • Asset Protection: Secure storage for tokens and NFTs, and protected access to fiat accounts and exchanges via multi-layer security.
    • Governance & Automation: Implementation of transaction authorization policy rules to define roles, approval levels, and automated workflows based on business requirements.
    • Treasury Visibility: Centralized viewing of assets across hot and cold wallets, including tracking and reporting of internal fund movements.
    • Asset Utility: Integration with DeFi, Staking, and Tokenized Funds, supported by a Gas Station for automated gas management during asset transfers.
    • Secure Transfers: Use of the Fireblocks Network for secure channel transactions with address resolution to prevent man-in-the-middle attacks and human error.
    • Trading Operations: Automation of rebalancing and transfers between exchange accounts to minimize counterparty risk.

  9. Overview of Fireblocks Off Exchange

    Fireblocks Off Exchange is a digital asset management infrastructure designed for trading desks, hedge funds, brokerages, custodians, and banks. It enables end users to utilize exchange services while maintaining complete control over their own assets, thereby mitigating the risks associated with centralized exchange malfunctions. Key benefits include end-user asset control, trustable exchange relationships, management of supported assets, and the ability to control rate limits and response codes to optimize platform load.

  10. Overview of Fireblocks Wallet-as-a-Service (WaaS)

    Fireblocks Wallet-as-a-Service (WaaS) provides a plug-and-play self-custody solution for applications to allow users to own, store, buy, sell, and trade digital assets. It utilizes secure MPC (Multi-Party Computation) wallets to scale user deposits while maintaining security and compliance. Key capabilities include native support for over 150 blockchains, raw signing for unsupported chains, and a Policy Engine to protect against internal collusion, human error, and external attacks.

  11. Overview of the Fireblocks Plugin-based Callback Handler

    The Fireblocks Plugin-based Callback Handler is a boilerplate application that simplifies the installation and setup process for users who need to handle Fireblocks callbacks. It allows developers to implement custom functionalities through plugins, removing the need to build a full server application from scratch. The boilerplate is available on GitHub.
    # Access the boilerplate on GitHub
https://github.com/fireblocks/plugin-based-callback-handler

  12. Overview of Dynamic Embedded Wallets

    Dynamic (a Fireblocks company) provides non-custodial embedded wallets using Threshold Signature Schemes (TSS-MPC). These wallets allow users to hold assets and interact with DeFi protocols within an application without requiring browser extensions or seed phrases. The architecture uses a 2-of-2 TSS-MPC system where one key share remains on the user's device and the other in a Trusted Execution Environment (TEE), ensuring the full private key is never constructed in a single location.