{"id":"hot-protocol","title":"HOT Protocol","content":"**HOT Protocol** is a decentralized infrastructure layer designed to facilitate chain abstraction by enabling smart contracts to securely own and manage private keys. Developed by HOT Labs, the protocol utilizes a combination of Multi-Party Computation (MPC), Trusted Execution Environments (TEEs), and the [NEAR Protocol](https://iq.wiki/wiki/near-protocol) as a state and coordination layer. Its primary function is to allow users and smart contracts to interact with numerous [blockchains](https://iq.wiki/wiki/blockchain) through a single account, abstracting away the complexities of cross-chain operations and asset management. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[2\\]](#cite-id-ajK8PsUg2NAuxQGs)​\n\n## Overview\n\nThe HOT Protocol was created to address a fundamental limitation in [blockchain](https://iq.wiki/wiki/blockchain) technology: [smart contracts,](https://iq.wiki/wiki/smart-contract) by design, cannot securely store private key information on-chain due to the public and transparent nature of blockchain state. This prevents them from directly controlling assets or performing actions on external cryptographic networks. HOT Protocol provides a solution by creating an off-chain MPC network that acts as a decentralized signer, executing actions on behalf of a smart contract only after receiving explicit, on-chain authorization. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)​\n\nThe protocol's core mission is to create a more unified and seamless [Web3](https://iq.wiki/wiki/web3) experience. It is built on several key technological pillars, including HOT Chain Signature, an MPC-based signing mechanism; Omni Tokens, a standard for multi-chain assets; and a native [utility token](https://iq.wiki/wiki/utility-token), HOT. The ecosystem includes a suite of products ranging from wallets and exchanges to developer Software Development Kits (SDKs), aiming to simplify interactions for both end-users and developers. The core logic of the protocol's on-chain components is deployed on the [NEAR](https://iq.wiki/wiki/near-protocol) [blockchain](https://iq.wiki/wiki/blockchain), which was chosen for its infrastructure advantages. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[4\\]](#cite-id-a8m5CkLrmsSwbme6)​\n\nThe system is designed to be chain-agnostic, supporting interactions with both [EVM](https://iq.wiki/wiki/ethereum-virtual-machine-evm)-compatible networks and non-EVM chains such as [Solana](https://iq.wiki/wiki/solana), [TON](https://iq.wiki/wiki/the-open-network-toncoin), and [Stellar](https://iq.wiki/wiki/stellar). By securely delegating signing capabilities to smart contracts, the protocol enables the development of advanced applications like passkey-based [Bitcoin](https://iq.wiki/wiki/bitcoin) wallets, complex account recovery mechanisms, and [dApps](https://iq.wiki/wiki/decentralized-application) that can manage assets across multiple chains from a single interface. [\\[2\\]](#cite-id-ajK8PsUg2NAuxQGs)​\n\n## History and Development\n\nHOT Protocol was developed by HOT Labs, with its foundational architecture detailed in a whitepaper authored by [Peter Volnov](https://iq.wiki/wiki/peter-volnov), Georgii Kuksa, and Andrey Zhevlakov. The paper, titled \"HOT Protocol,\" was first submitted to the arXiv preprint server on December 1, 2025. It outlined the protocol's cryptographic design, security model, and technical implementation. [\\[2\\]](#cite-id-ajK8PsUg2NAuxQGs)​\n\nPrior to the paper's publication, a [testnet](https://iq.wiki/wiki/testnet) was launched, which featured 12 MPC nodes distributed across five different cloud providers. A notable proof-of-concept demonstrated on the testnet was a passkey-enabled [Bitcoin](https://iq.wiki/wiki/bitcoin) wallet operating on the [NEAR](https://iq.wiki/wiki/near-protocol) [mainnet](https://iq.wiki/wiki/mainnet), showcasing the protocol's ability to link modern biometric security with legacy [blockchains](https://iq.wiki/wiki/blockchain). [\\[5\\]](#cite-id-BjSYM3sZHrwqAU2e) As of February 2026, the protocol's Betanet is live and accessible to users. [\\[6\\]](#cite-id-Yce61bPx6rN2Xp5A)​\n\nThe project's launch followed a phased roadmap:\n\n1. Commencement of HOT mining.\n2. Setup of protocol [validators](https://iq.wiki/wiki/validator) and release of the MPC wallet SDK.\n3. Launch of HOT Chain Signature for EVM chains ([Base](https://iq.wiki/wiki/base), [Arbitrum](https://iq.wiki/wiki/arbitrum), [Optimism](https://iq.wiki/wiki/optimism)) and [TRON](https://iq.wiki/wiki/tron).\n4. Launch of the HOT Bridge and omni balances functionality.\n5. Implementation of 2FA, replaceable seed phrases for HOT Wallets, and launch of a cross-chain gas relay.\n6. Opening of the HOT token for public [staking](https://iq.wiki/wiki/staking) and transfers.\n\nBy February 2026, numerous features had been released, including integrations for [Bitcoin](https://iq.wiki/wiki/bitcoin), Ledger, and [Tron](https://iq.wiki/wiki/tron), cross-chain swaps, and the release of mobile and browser extension wallets. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\n## Technical Architecture\n\nHOT Protocol's architecture combines on-chain contracts for state management with a decentralized off-chain network for secure computation. It is designed around a pull-based mechanism where a third party can request a signature, which the MPC network produces only after verifying authorization from the key-owning [smart contract](https://iq.wiki/wiki/smart-contract) on its respective chain. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)​\n\n### Core Components\n\n* **MPC Network (HOT Chain Signature):** This is the core of the protocol, comprising a network of independent [validator](https://iq.wiki/wiki/validator) [nodes](https://iq.wiki/wiki/node) that collectively manage private keys. Instead of a single key, each validator holds a cryptographic share of a root key using Shamir's Secret Sharing. A transaction can only be signed when a predetermined threshold of validators (t-of-n) cooperate to generate partial signatures. The full private key is never reconstructed in a single location, which significantly enhances security by eliminating single points of failure. The protocol is designed as an open and decentralized network, in contrast to centralized MPC solutions controlled by a single entity. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)\n* **Trusted Execution Environments (TEEs):** Each node in the MPC network runs its software within a TEE, such as Intel [TDX](https://iq.wiki/wiki/tdx) or AMD SEV. A TEE is a secure and isolated hardware environment that ensures the confidentiality and integrity of code and data, even from the node operator. All private key share computations and contract authorization checks occur inside the TEE. Nodes must perform periodic remote attestation, a process where they cryptographically prove to the on-chain controller contract that they are running the correct, unaltered code within a genuine TEE. [\\[5\\]](#cite-id-BjSYM3sZHrwqAU2e)\n* **On-Chain State Layer (NEAR Protocol):** The [NEAR](https://iq.wiki/wiki/near-protocol) [blockchain](https://iq.wiki/wiki/blockchain) serves as the decentralized and efficient state layer for the system. It hosts two critical [smart contracts](https://iq.wiki/wiki/smart-contract):\n\n  * **MPC Controller Contract:** Manages the state of the MPC network, including the list of registered nodes, their public keys, and their attestation status. It also facilitates on-chain governance for network configuration changes.\n  * **Key Registry Contract:** Stores the mapping between a derived key identifier (`key_id`) and the address of the [smart contract](https://iq.wiki/wiki/smart-contract) that is authorized to approve its use. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)\n* **Gatekeeper Network:** This is an access control layer of relay servers that sits between users and the MPC network. Gatekeepers are responsible for aggregating user signing requests, sampling available MPC nodes, and preventing spam or DDoS attacks. They are stateless and do not handle any secret data. [\\[5\\]](#cite-id-BjSYM3sZHrwqAU2e)\n* **Key-Owner Contract:** A smart contract deployed on a target [blockchain](https://iq.wiki/wiki/blockchain) that \"owns\" a private key managed by the MPC network. Developers must implement a specific read-only function, `hot_verify(message, key_id, metadata)`, which the MPC nodes call to authorize or deny a signing request. This function contains the custom logic that determines whether a transaction should be signed. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)\n\n### Signature Generation Workflow\n\n1. A user or application submits a signing request for a specific message to a Gatekeeper.\n2. The Gatekeeper validates the request and forwards it to a quorum of `t` available MPC nodes.\n3. Each MPC node uses the on-chain Key Registry on [NEAR](https://iq.wiki/wiki/near-protocol) to identify the Key-Owner contract associated with the request.\n4. Each node makes a read-only call to the `hot_verify` method on the Key-Owner contract on the target blockchain to confirm the request is authorized.\n5. If authorized, the `t` nodes collaboratively compute their partial signatures inside their respective TEEs.\n6. The Gatekeeper collects the partial signatures and combines them using Lagrange interpolation to produce a final, complete signature.\n7. The final signature is returned to the user, who can then broadcast it to the target [blockchain](https://iq.wiki/wiki/blockchain). [\\[5\\]](#cite-id-BjSYM3sZHrwqAU2e)\n\n### Cryptographic Primitives\n\nThe protocol employs several established cryptographic techniques to ensure security and functionality.\n\n* **Distributed Key Generation (DKG):** Based on the protocol by Gennaro et al. (2007) to establish the initial key shares without a trusted dealer.\n* **Key Derivation:** Uses a deterministic derivation method inspired by BIP-32, enabling the creation of multiple child keys from a single root key without requiring a new DKG ceremony.\n* **Threshold Signature Schemes:**\n\n  * **ECDSA:** For [Bitcoin](https://iq.wiki/wiki/bitcoin), [EVM](https://iq.wiki/wiki/ethereum-virtual-machine-evm) chains, and [Tron](https://iq.wiki/wiki/tron), implementing the FastECDSA protocol.\n  * **EdDSA:** For [Solana](https://iq.wiki/wiki/solana), [NEAR](https://iq.wiki/wiki/near-protocol), [Stellar](https://iq.wiki/wiki/stellar), and [TON](https://iq.wiki/wiki/the-open-network-toncoin), using the FROST (Flexible Round-Optimized Schnorr Threshold signatures) scheme.\n    These schemes produce signatures that are byte-for-byte identical to standard single-key signatures, ensuring full compatibility with existing [blockchains](https://iq.wiki/wiki/blockchain). [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)\n\n## Ecosystem and Features\n\nHOT Labs has developed a comprehensive ecosystem of products and services built on the core protocol to showcase its chain abstraction capabilities. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\n### Omni Tokens\n\nOmni Tokens are a key feature, designed to exist natively across multiple [blockchains](https://iq.wiki/wiki/blockchain). Users can deposit or withdraw these tokens from any supported chain, with bridging designed to take approximately 30 seconds for the cost of a single token transfer fee. The protocol also enables gas-free swaps, allowing users to trade Omni Tokens for native assets on any supported chain directly within their omni balance. The [Solidity](https://iq.wiki/wiki/solidity) implementation for Omni Tokens has been open-sourced and audited by [Hacken](https://iq.wiki/wiki/hacken). [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\n### Products and Services\n\n* **HOT Wallet:** A non-custodial, multi-chain MPC wallet available as a Telegram Mini App, browser extension, and mobile app. It supports features like 2FA, replaceable [seed phrases](https://iq.wiki/wiki/seed-phrase), and integration with hardware wallets like Ledger. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[6\\]](#cite-id-Yce61bPx6rN2Xp5A)\n* **HOLD Wallet:** A hardware cold wallet for long-term asset storage.\n* **HOT Exchange (hex.exchange):** A multi-chain [decentralized finance](https://iq.wiki/wiki/defi) (DeFi) platform with a fully on-chain order book, powered by the protocol's underlying \"HOT Omni\" technology.\n* **HOT Craft (hotcraft.art):** An [NFT](https://iq.wiki/wiki/non-fungible-token-nft) marketplace that leverages chain abstraction for multi-chain asset trading and [staking](https://iq.wiki/wiki/staking).\n* **Developer Tools:** HOT Labs provides the Wibe3 / HOT Connect SDK, a toolkit allowing dApps to integrate multi-chain MPC wallet functionality. It also offers a \"Sign\" API for [smart contracts](https://iq.wiki/wiki/smart-contract) to use the protocol's message-signing capabilities. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)\n\n## Tokenomics (HOT)\n\nHOT is the native [utility token](https://iq.wiki/wiki/utility-token) of the HOT Protocol, essential for the network's operation, security, and economy. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\n### Utility\n\n* **Transaction Fees:** Users spend HOT to pay validators for signing transactions via the MPC network. The cost is dynamic, depending on factors like the required security threshold and network load.\n* **Staking:** [Validators](https://iq.wiki/wiki/validator) are required to stake HOT rewards.\n* **Gas Abstraction:** The HOT token can be used to pay for [transaction fees](https://iq.wiki/wiki/transaction-fee) on any [blockchain](https://iq.wiki/wiki/blockchain) supported by the protocol, removing the need for users to hold multiple native [gas](https://iq.wiki/wiki/gas) tokens. [\\[7\\]](#cite-id-LspzRqiZelySoONh)\n\n### Governance Model\n\nThe protocol's foundational whitepaper outlines a governance model centered around a [utility token](https://iq.wiki/wiki/utility-token) (referred to in the paper as `gTOKEN`, which corresponds to the public-facing HOT token). This model includes distinct participant roles with economic incentives to ensure network integrity. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)​\n\n* **DAO Members:** Govern the protocol, vet new participants, and process slashing reports. Must stake tokens.\n* **MPC Node Providers:** Run the hardware and TEE-enforced software to secure the network. They must stake tokens and earn rewards for honest participation.\n* **Gatekeepers:** Lease MPC network capacity and serve as public access points. They are also required to stake tokens.\n* **Fishermen:** Monitor the network for malicious activity and submit dispute reports to the DAO, earning rewards from slashed stakes.\n\nA slashing mechanism is in place to enforce network integrity. Validators and other staked participants risk having their staked HOT tokens \"cut\" or slashed if they engage in malicious behavior, such as non-compliance or replay attacks. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[5\\]](#cite-id-BjSYM3sZHrwqAU2e)​\n\n## Security and Audits\n\nSecurity is a central component of the protocol's design, employing a multi-layered approach. The use of a decentralized network of independent [validator](https://iq.wiki/wiki/validator) [nodes](https://iq.wiki/wiki/node), where no single entity possesses the full private key, forms the foundation of its security model. All communication between users and nodes is end-to-end encrypted, and the use of TEEs ensures that key material and cryptographic computations are isolated and confidential. [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\nThe threat model is designed to be secure against a computationally bounded adversary that can corrupt fewer than the threshold number of MPC nodes (`f < t`). The protocol assumes the security of its underlying cryptographic primitives and the TEE hardware. [\\[3\\]](#cite-id-eoIvNwux4oQOQw2y)​\n\nThe protocol's [smart contracts](https://iq.wiki/wiki/smart-contract) and infrastructure have undergone multiple third-party security audits from firms including:\n\n* Trail of Bits\n* [Hacken](https://iq.wiki/wiki/hacken) (specifically for the Omni Token Solidity contract)\n* Veridise (specifically for the HOT Bridge)\n  [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)\n\n## Adoption and Partnerships\n\nAs of early 2026, the protocol reported significant user adoption, with over 30 million wallets created and more than 1 billion transactions processed across over 100 supported [blockchains](https://iq.wiki/wiki/blockchain). [\\[1\\]](#cite-id-OrgArHUIw4aK60R6)​\n\nThe validator network is secured by a number of trusted partners running nodes, including:\n\n* EverStake\n* [NEAR Protocol](https://iq.wiki/wiki/near-protocol)\n* [Aurora](https://iq.wiki/wiki/aurora)\n* HAPI\n  [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) [\\[7\\]](#cite-id-LspzRqiZelySoONh)\n\nHOT Protocol has established collaborations and integrations with a wide range of projects across [DeFi](https://iq.wiki/wiki/defi), infrastructure, and security. Key partners include the [Stellar](https://iq.wiki/wiki/stellar) [Foundation](https://iq.wiki/wiki/foundation), [Kava](https://iq.wiki/wiki/kava), [PancakeSwap](https://iq.wiki/wiki/pancakeswap), [Jupiter](https://iq.wiki/wiki/jupiter), and [Helius](https://iq.wiki/wiki/helius). [\\[1\\]](#cite-id-OrgArHUIw4aK60R6) The team has also worked closely with projects like Gonka, for which it built the primary [decentralized exchange](https://iq.wiki/wiki/decentralized-exchange), and PublicAI, to enable NFT [staking](https://iq.wiki/wiki/staking) on the HOT Craft platform. [\\[6\\]](#cite-id-Yce61bPx6rN2Xp5A)​","summary":"HOT Protocol is a multi-chain infrastructure on NEAR for chain abstraction, using an MPC network and TEEs to enable cross-chain interactions from a single account.","images":[{"id":"QmVGhR55KMXQjzFxXUGkarpHUVCydXe86ChVL4nPJNJkD1","type":"image/jpeg, image/png"}],"categories":[{"id":"organizations","title":"organizations"}],"tags":[{"id":"Protocols"},{"id":"Blockchains"},{"id":"Developers"},{"id":"Ethereum"},{"id":"Solana"}],"media":[{"id":"QmcpcFiNz8yukVBG5BXQuqyXL4aK5D145kr6SxJ1WN7cvg","name":"aL6SkWGNHVfTOwRL_hotprotocol.avif","caption":"","thumbnail":"QmcpcFiNz8yukVBG5BXQuqyXL4aK5D145kr6SxJ1WN7cvg","source":"IPFS_IMG"},{"id":"QmYHVFx36dtoVXysyK1PVrDwhTk8C3hHHGpWcC3NsUXqfC","name":"Cópia de Design sem nome (1).png","caption":"","thumbnail":"QmYHVFx36dtoVXysyK1PVrDwhTk8C3hHHGpWcC3NsUXqfC","source":"IPFS_IMG"},{"id":"QmRNt8QkLmDPf5ZJxUVuFHfsRzaTJszjSC5Cpd8HCk4drP","name":"Cópia de Design sem nome.png","caption":"","thumbnail":"QmRNt8QkLmDPf5ZJxUVuFHfsRzaTJszjSC5Cpd8HCk4drP","source":"IPFS_IMG"},{"id":"QmVuqyTQWzVADq4TC59xo5r59qfHcnR7Lrc6aFRso6EDKi","name":"logo.svg","caption":"","thumbnail":"QmVuqyTQWzVADq4TC59xo5r59qfHcnR7Lrc6aFRso6EDKi","source":"IPFS_IMG"}],"metadata":[{"id":"references","value":"[\n  {\n    \"id\": \"OrgArHUIw4aK60R6\",\n    \"url\": \"https://hot-labs.org/\",\n    \"description\": \"HOT Protocol official website overview\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"ajK8PsUg2NAuxQGs\",\n    \"url\": \"https://arxiv.org/abs/2512.02287\",\n    \"description\": \"HOT Protocol academic paper abstract\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"eoIvNwux4oQOQw2y\",\n    \"url\": \"https://arxiv.org/html/2512.02287v1\",\n    \"description\": \"HOT Protocol whitepaper full text\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"a8m5CkLrmsSwbme6\",\n    \"url\": \"https://docs.hotdao.ai/\",\n    \"description\": \"HOT Protocol documentation on architecture\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"BjSYM3sZHrwqAU2e\",\n    \"url\": \"https://www.emergentmind.com/topics/hot-protocol\",\n    \"description\": \"Emergent Mind analysis of HOT Protocol paper\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"Yce61bPx6rN2Xp5A\",\n    \"url\": \"https://x.com/hotdao\\\\_\",\n    \"description\": \"HOT Protocol social media announcements\",\n    \"timestamp\": 1772120644433\n  },\n  {\n    \"id\": \"LspzRqiZelySoONh\",\n    \"url\": \"https://getblock.io/marketplace/projects/hot-protocol/\",\n    \"description\": \"HOT token for gas fee abstraction\",\n    \"timestamp\": 1772120644433\n  }\n]"},{"id":"website","value":"https://hot-labs.org/"},{"id":"twitter_profile","value":"https://x.com/hotdao_"},{"id":"references","value":"https://docs.hotdao.ai/"},{"id":"references","value":"https://hotscan.org/"},{"id":"references","value":"https://arxiv.org/abs/2512.02287"},{"id":"website","value":"https://holochain.org/"},{"id":"twitter_profile","value":"https://twitter.com/H_O_L_O_"},{"id":"reddit_profile","value":"https://reddit.com/r/holochain"},{"id":"github_profile","value":"https://github.com/holochain/holochain-rust"},{"id":"discord_profile","value":"http://t.me/channelHolo"},{"id":"medium_profile","value":"https://medium.com/h-o-l-o"},{"id":"etherscan","value":"https://etherscan.io/token/0x6c6ee5e31d828de241282b9606c8e98ea48526e2"},{"id":"nansen","value":"https://app.nansen.ai/token-god-mode?chain=ethereum&tab=transactions&tokenAddress=0x6c6ee5e31d828de241282b9606c8e98ea48526e2"},{"id":"contract_url","value":"https://www.oklink.com/eth/token/0x6c6ee5e31d828de241282b9606c8e98ea48526e2"},{"id":"commit-message","value":"\"Added organization page for HOT Protocol\""}],"events":[{"id":"a3af5e34-e8c5-436f-9b21-f1d4ffb13d08","date":"2024-02","title":"HOT Protocol Founded","type":"CREATED","description":"The official X account (@hotdao_) for HOT Protocol was created, marking the project's public-facing inception.","link":"https://x.com/hotdao_","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"a4702d41-b48d-4f39-82d1-7c9c9c1e9f11","date":"2025-12","title":"Foundational Whitepaper Published","type":"DEFAULT","description":"The research paper 'HOT Protocol' (arXiv:2512.02287) was submitted by its authors, Peter Volnov, Georgii Kuksa, and Andrey Zhevlakov, detailing the protocol's architecture.","link":"https://arxiv.org/abs/2512.02287","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"a8d0494b-6762-403e-98b5-5297aa0b3244","date":"2026-02","title":"Betanet Launch","type":"DEFAULT","description":"The HOT Protocol Betanet went live, enabling broader testing and development on the network.","link":"https://x.com/hotdao_","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"operator":{"id":"0xd5893989b9952c6568a99F854795AcC5Ae480D56"},"language":"en","version":1,"linkedWikis":{"blockchains":["near-protocol","ethereum","solana","stellar"],"founders":["peter-volnov"],"speakers":[]}}