# Supra’s Interoperability Model (HyperNova vs HyperLoop)

SupraNova integrates two types of bridging models depending on the destination chain and required trust assumptions:

| Protocol  | Use Case                                                        | Validation Model                                                          |
| --------- | --------------------------------------------------------------- | ------------------------------------------------------------------------- |
| HyperNova | Trustless bridging between major L1s (e.g., Ethereum to Supra). | Cryptographic proofs (Sync Committee signatures, Merkle proofs, Ancestry) |
| HyperLoop | Fast bridging across Layer2 rollups or high-throughput  chains. | Multi-signature validator committee with game-theoretic security          |

Both models are modular and selected based on use case.

HyperNova is used where trust minimization and security are critical and on-chain cryptographic verification of source chain events are possible, while HyperLoop is optimized for speed and cost in environments where a middle network of bridge nodes that are proven to be game theoretically secure needs to be trusted.<br>


---

# 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://supraoracles.gitbook.io/supra/supranova/supras-interoperability-model-hypernova-vs-hyperloop.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.