# Institutional MPC Integration

For enterprise asset managers, treasuries, and major quant funds, maintaining self-custody cannot rely on simple hot wallets or single-signature keys. These entities require rigorous internal compliance, multi-party computation (MPC) infrastructure, and segregated authorization workflows.

Nexus Protocol is structurally designed to integrate seamlessly with standard Institutional MPC Infrastructure (supporting frameworks like Fireblocks, Safeheron, and similar institutional providers).

This integration allows asset management institutions to run high-frequency market-making operations on Bitcoin while strictly enforcing their internal compliance and policy engines.

#### The Operational Workflow

The enterprise integration separates the operational capability (quoting and responding to market demand) from the cryptographic authorization (signing the transactions).

{% stepper %}
{% step %}

1. Market Response (Asset Manager Node)

The Asset Management firm operates a Nexus Node configured with their proprietary quoting logic and quantitative models. This node connects to the Nexus Composer, calculates real-time liquidity curves, and responds to trading intents from the market.
{% endstep %}

{% step %}
2\. Transaction Submission

When a market-making match occurs, the Asset Manager's Nexus Node constructs the precise transaction (using PSBT) required to clear the trade. Instead of signing it directly, the node submits this unsigned transaction request directly into the institution's MPC Policy Engine.
{% endstep %}

{% step %}
3\. Policy Verification

The institutional MPC infrastructure evaluates the transaction request against pre-defined rulesets (e.g., maximum trade limits, whitelisted addresses, velocity controls).
{% endstep %}

{% step %}
4\. Auditor Node Approval

To ensure the transaction strictly satisfies the market-making criteria (e.g., confirming the slippage matches the expected yield mathematically), the client's internal auditors or risk-control teams run a separate Auditor Nexus Node. This Auditor Node independently verifies the mathematical integrity of the trade. If it passes, the auditor authorizes the signature via the MPC pipeline.
{% endstep %}

{% step %}
5\. L1 Output Execution

Once the MPC quorum is reached according to the enterprise policy, the PSBT is cryptographically signed and routed back into the Nexus Network for final L1 settlement or State Channel roll-up.
{% endstep %}
{% endstepper %}

#### Strategic Benefits

* No Compromise on Security: Market-making logic can be aggressively optimized by traders without exposing the private keys to hot execution environments.
* Separation of Concerns: Quants handle the pricing models (Asset Manager Node), while Risk/Auditing handles the verification (Auditor Node + Policy Engine).
* Deep Institutional Liquidity: By bridging the gap between high-frequency AMM software and institutional cold-storage/MPC constraints, Nexus unlocks unprecedented capital depth for the Bitcoin ecosystem.

***

#### Become an Institutional Partner

We actively welcome quantitative trading teams, asset managers, and institutional custody providers to establish strategic partnerships with OnNexus.

If you are interested in integrating with the Nexus network, deploying bespoke market-making nodes, or optimizing your enterprise custody infrastructure for High-Frequency Bitcoin Trading, please reach out to our team:

📧 Contact Us: <hello@on.nexus>


---

# Agent Instructions: 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.on.nexus/deployment-and-integration/institutional-mpc.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.