> For the complete documentation index, see [llms.txt](https://docs.hypersig.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypersig.xyz/getting-started/how-it-works.md).

# How It Works?

### Why Hypersig

Most multisigs in crypto are implemented through smart contracts. Hypersig takes a different path: it is built directly on **HyperCore’s protocol-level multisig support**, the same primitives designed and secured by the Hyperliquid team themselves.

This means that every approval rule, signer threshold, and transaction is enforced by the **core blockchain consensus**. The result is a system that is **native to HyperCore**—fast, efficient, and secure—while giving users the peace of mind that their assets are protected at the protocol level.

### How it works?

#### Protocol-Level Security

Hypersig is built directly on HyperCore’s native multisig functionality, which integrates security rules at the blockchain's core consensus level. This creates a direct and streamlined system for managing on-chain operations.

* `ConvertToMultiSigUser` actions register signers and thresholds natively on-chain.
* From that point, every action must pass through HyperCore’s protocol-level multisig enforcement.
* No third-party contract logic is ever involved—reducing attack surfaces to zero.

**Every Signature Verified On-Chain**

Transactions are wrapped in a `MultiSig` action containing:

* The target multisig account
* The leader (who submits the transaction)
* The required authorized signatures

HyperCore consensus **individually validates each signature**, enforces thresholds, and applies nonce-based replay protection. This ensures:

* **Strong ordering** → no double spend or race conditions
* **Immutable audit trail** → all actions logged directly on-chain
* **Cryptographic verification** → signatures cannot be faked, replaced, or bypassed

**Flexible, On-Chain Governance**

* Add or remove owners, or change thresholds, with a `MultiSig` action.
* Convert back to single-sig by submitting an empty signer set.
* All governance changes are **immutable, auditable, and enforced by HyperCore itself**.

**Why This Matters for You**

* **Non-custodial by design**: You retain full control of keys and assets. Hypersig only streamlines the user flow.
* **Blockchain-enforced trust**: Security rules live at the protocol layer, not in Hypersig’s UI or contracts.
* **Peace of mind**: You get a **battle-tested, Hyperliquid-native primitive** wrapped in an elegant UX.

**The Hypersig Difference**

With Hypersig, you don’t have to choose between security and usability.

* Security comes directly from **HyperCore’s protocol-level multisig**.
* Usability comes from **Hypersig’s next-level UX**: one-click approvals, sub-accounts, and agent wallets.

**Result:** Institutional-grade protection + next-level UX, purpose-built for the pace of Hyperliquid.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hypersig.xyz/getting-started/how-it-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.