CrypDefi is now Fortkey. read the announcement

    Fortkey developer docs

    Welcome to the Fortkey documentation. Whether you are running an algorithmic desk, connecting a manual trading workflow, or evaluating our security architecture, you will find everything you need to build on Fortkey here.

    Fortkey is self-custody signing infrastructure for trading firms: keys are generated and used inside hardware-isolated enclaves in your perimeter, every transaction is decoded and policy-checked before a signature exists, and signing runs at trading speed close to your venues.

    Start here

    Getting started

    Authenticate a bot, send an unsigned payload, get a policy-checked signature back.

    Build with AI

    A copy-paste prompt for Cursor, Claude Code, and other agents.

    What is Fortkey?

    The platform concepts: wallets, admins, traders, policies, roles.

    Policy engine

    Field-level rules and rule logic, enforced before any signature exists.

    Security

    Enclaves, layered KMS encryption, attestation, and the key lifecycle.

    Explore by role

    Bot developers
    Admins and operations
    Security reviewers

    Key capabilities

    Enclave signing

    Private keys are generated, stored, and used only inside attested enclaves. No person or system outside the enclave ever sees a raw key.

    Policy enforcement

    Whitelists, blacklists, transaction types, byte-level smart contract validation, user and group scoping, IP restrictions, and bring-your-own-policy callbacks.

    Multi-region signing

    Latency-routed signing replicas near your venues, with policies applied globally in near real time.

    Two ways to trade

    Bots through the SDK or REST API; humans through FortkeyLink, which connects to standard browser extensions like a hardware wallet.

    Chain coverage

    Signing across 9 chain families including Canton. Documented policy rule interpretations for Aptos, EVM, Polkadot, Radix, Solana, Stellar, Sui, and XRPL, with new chains added on demand.

    Auditability

    Transaction logs that show exactly what was requested, what was parsed, what was signed, and why anything was blocked.

    Start building

    1. 01Try the sandboxSo you have an organization, a wallet, and a bot user to work with.
    2. 02AuthenticateLog a bot in with the challenge-response protocol. No static API keys.
    3. 03Sign your first transactionRust or TypeScript SDK, or plain REST.
    4. 04Add a policyAttach a whitelist or a smart contract rule, then verify with the simulator.

    Need help?

    Questions or a chain we should add? Talk to engineering.

    Coming soon

    Free-tier MCP-native signing for individual developers, quants, and AI agents is in the works.