# Bridging Flow

This section explains how to use the SupraNova Bridge dApp to bridging ETH from Ethereum to supETH on Supra network, with each technical stage explained clearly.

{% stepper %}
{% step %}

### Connecting Your Wallets

Before initiating a bridge transaction, you must connect two wallets:

| Wallet                                   | Purpose                                               |
| ---------------------------------------- | ----------------------------------------------------- |
| MetaMask (Ethereum) or any source wallet | To send the ETH and sign the bridge transaction       |
| Supra Wallet                             | To receive Supra wrapped ETH (supETH) minted on Supra |

#### Getting Started:

* Open the SupraNova Bridge dApp.
* Click “Connect Wallet” on the top right corner.
* Approve the MetaMask pop-up to connect your Ethereum wallet.
* Choose your Supra Wallet (StarKey Wallet) or manually enter a recipient address using the “Type Recipient Address” toggle.

<figure><img src="https://3966986543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVkhtPwRHCu7dT1kTMvdp%2Fuploads%2F7g83yhMvTK5KcA01GcZ3%2FBridge%20flow_connect%20wallet.png?alt=media&#x26;token=fde4ab19-b93b-4b69-b688-5425d75c2cff" alt=""><figcaption></figcaption></figure>

<p align="center">The toggle is notated as 1 and the existing wallet is notated as 2.</p>

{% hint style="success" %}

* **The Supra Wallet is where your minted supETH will arrive after successful bridging.**
* **Make sure the address is correct before proceeding.**
  {% endhint %}

{% endstep %}

{% step %}

### Initiating the Bridge Transaction

After wallets are connected, follow these steps.

Under the Bridge tab, **select**:

* Source Chain: Ethereum
* Destination Chain: Supra
* Token: ETH –>  supETH
* Enter the amount of ETH you wish to bridge.

**Review**:

1. Estimated bridge time
2. Bridge fee breakdown (in ETH and $SUPRA)

Click **“Confirm”** to proceed.

<figure><img src="https://3966986543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVkhtPwRHCu7dT1kTMvdp%2Fuploads%2FgHJLpZ7DBT7eWFrGqy1u%2FSupra%20Bridge%20service.png?alt=media&#x26;token=6acdcd06-3fe5-49b3-b02e-e94fa1481695" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**This action calls the HyperNovaCore smart contract on Ethereum, locking your ETH and emitting a LOGX event signaling a bridge request.**
{% endhint %}
{% endstep %}

{% step %}

### MetaMask Transaction Confirmation

Upon clicking **“Confirm”**:

* MetaMask prompts you to confirm the transaction.
* Gas fees are shown (normal Ethereum fees apply).
* Approve and confirm the transaction

<figure><img src="https://3966986543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVkhtPwRHCu7dT1kTMvdp%2Fuploads%2F3Eysveq978vbNagJTIGt%2FBridge_Transaction_request.png?alt=media&#x26;token=3320e4cf-c472-4db8-b6b1-6cf909141099" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Event Capture and Proof Generation by Relayer

After the bridge event is emitted, The Event Listener captures the bridge event from the ethereum chain and stores it in a message queue. The Relayer Driver then consumes the event. detects the bridge event from the Ethereum chain.

It generates the following proofs:<br>

* **Sync Committee Proof** – Block signed by the Sync Committee
* **Receipt Proof** – Proof that the transaction succeeded
* **Ancestry Proof** (if the block lacks enough signatures)

{% hint style="info" %}
If required, Ancestry Proof connects the event’s block to a more recent, heavily signed block.
{% endhint %}

#### The Technical flow is as follows:

**Ethereum Event → Relayer captures → Builds Proof Bundle → Prepares Submission to Supra**
{% endstep %}

{% step %}

### Proof Submission and On-Chain Verification

Once proofs are generated:

* The Relayer submits the proof bundle to Supra’s HyperNovaCore verifier smart contract.
* The verifier checks:
* Validity of the block header signatures
* Correctness of transaction existence and execution
* Authenticity of the event data (right source, token, amount, recipient)\
  If all checks pass, the verifier marks the bridge request as valid.
  {% endstep %}

{% step %}

### Token Minting and Fund Receipt

Upon successful verification:

* The Token Bridge Service Contract is triggered.
* Supra Wrapped ETH (supETH) is minted on Supra in a 1:1 ratio to the locked ETH.
* The minted supETH is sent to your connected (or specified) Supra Wallet address.

You can now:

* View transaction history under Explorer > My Transactions.

<figure><img src="https://3966986543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVkhtPwRHCu7dT1kTMvdp%2Fuploads%2FvH9uuDBlZJKcKNI4cywN%2FBridge_Transaction%20Detail.png?alt=media&#x26;token=17ecbc31-08b8-4f32-b188-476065470571" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### &#x20;Transaction Lifecycle Summary

| Stage              | System Action                             | User Action           |
| ------------------ | ----------------------------------------- | --------------------- |
| Wallet Connection  | Connect MetaMask and Supra Wallet         | Click Connect Wallet  |
| Initiate Bridge    | Lock ETH on Ethereum                      | Enter Amount, Confirm |
| Event Emission     | Emit bridge request log                   | Wait                  |
| Relayer Proofs     | Generate, Sync , Receipt, Ancestry proofs | Wait                  |
| Supra Verification | Validate proofs on-chain                  | Monitor Explore       |
| Token Min          | Mint supETH to recipient wallet           | Receive tokens        |

{% hint style="warning" %}
**During Bridging these are the in-built safeguards:**

* **Incomplete Proofs: Bridge request remains pending until sufficient proofs arrive.**
* **Relayer Failure: Another permissionless relayer can submit the proof.**
* **Committee Key Rotation: If Sync Committee public keys expire, Committee Updater submits fresh keys to Supra automatically.**
  {% endhint %}