> For the complete documentation index, see [llms.txt](https://crosschain-alliance.gitbook.io/hashi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-alliance.gitbook.io/hashi/apps-integrations/openfort-chain-abstraction.md).

# Openfort Chain Abstraction

Hashi provides a trustless fallback proving mechanism for Openfort’s chain-abstraction project, ensuring seamless cross-L2 proof generation

### Overview

Hashi has been integrated as a fallback proving mechanism for [Openfort’s](https://github.com/openfort-xyz/openfort-chain-abstraction) chain-abstraction project. Openfort, a wallet solution focused on enhancing chain interoperability, utilizes Polymer for cross-L2 execution proofs and leverages Hashi as a robust backup. This setup ensures continued security and reliability in case Polymer or Openfort's primary proof solution becomes unavailable.

### How the Integration Works

When Openfort's primary proof provider (Polymer) is unavailable, Hashi steps in to ensure liquidity providers (LPs) can still generate valid proofs for their fronted funds. This is achieved by using a local Hashi RPC API that wraps Ethereum methods like `eth_getProof` for storage proofs or `eth_getTransactionReceipt` for event proofs. The proof generated by Hashi is then submitted through the `fallbackRepay` function of Openfort's `InvoiceManager` smart contract, enabling refunds solely with public on-chain data and avoiding reliance on third parties.

#### Key Steps:

1. **Proof Generation:** LPs run a Hashi RPC API locally to generate proofs.
2. **Proof Submission:** The generated proof is submitted via the `fallbackRepay` function.
3. **Repayment Processing:** Openfort's `InvoiceManager` contract handles the repayment using only on-chain data, ensuring a trustless and permissionless fallback strategy.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://crosschain-alliance.gitbook.io/hashi/apps-integrations/openfort-chain-abstraction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.