hashi
  • Welcome
  • Introduction
    • What is Hashi?
    • Why Hashi?
    • Key Features
    • The SSN
  • Getting Started
    • How Hashi Works
    • Quick Start
      • Verifying foreign event
        • Setting the scene
        • Getting the Event Proof
        • Validating your statements
      • Reading foreign state
        • Setting the scene
        • Getting the Storage Proof
        • Validating your statements
      • Pushing a message
        • Writing your message sending contract
        • Implementing your callback
        • Waiting for the cross-chain execution
  • Core Concepts
    • Block Header Relaying
    • Message Dispatching
    • Oracles
    • Additive Security Model
  • Deployments
    • Blockchains
    • Oracles
  • Smart Contracts
    • Key Contracts
    • HashiProver API
  • TOOLS
    • SP1 storage proof verifier
    • Solana integration
  • APPS / INTEGRATIONS
    • Safe Crosschain
    • Aragon UCG
    • Openfort Chain Abstraction
  • META
    • Developer resources
    • Audits
    • Explorer
    • Community
Powered by GitBook
On this page
  • Overview
  • How the Integration Works
Export as PDF
  1. APPS / INTEGRATIONS

Openfort Chain Abstraction

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

PreviousAragon UCGNextDeveloper resources

Last updated 3 months ago

Overview

Hashi has been integrated as a fallback proving mechanism for 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.

Openfort’s