Fee Structure in SupraNova
SupraNova’s fee model is designed to sustain a permissionless, decentralized bridging ecosystem while incentivizing critical actors like relayers and committee updaters.

Fee Overview and Responsibilities
SupraNova applies two levels of fees internally but simplifies the user experience by exposing only the Service Layer Fee during transaction confirmation.
Verification Fee
An internal fee that compensates Committee Updaters for:
- Proof generation
- Signature validation
- Validator public key updates
Paid by: Service Layer (not the user directly)
Service Layer Fee
Visible to users and deducted upon initiating a bridge transaction. It covers:
- Operational costs
- Treasury accumulation
- Relayer and Committee Updater rewards
Then the system separates fees into two distinct layers:
| Fee Type | Purpose | Source of Funding |
|---|---|---|
| Verification Fee | Covers cryptographic proof verification on Supra | Funded from service fee. |
| Service Layer Fee | Specific to the token bridge service, customizable by service providers | Paid by bridging users |
Message Passing Layer Fee
This fee is charged for:
- Verifying Sync Committee proofs
- Verifying ancestry and receipt proofs
- Managing public key updates (Committee Updater work)
- Safe validators committee handovers through public key updates.
Who Charges It?
- The HyperNovaCore verifier contract charges this fee internally. Service-contracts calling the message-passing layer for validation pay this fee as part of the process.
Service Layer Fee (Token Bridge Specific)
This fee is charged by service-specific components like the Token Bridge and includes:
- Operational Service costs.
- Relayer rewards.
Who Sets It?
- The Token Bridge smart contract service owner (typically the protocol team).
How is it Collected?
- A small cut is deducted from the bridged amount (in bridged assets like supETH or supUSDC) at the time of minting.
What Does It Fund?
- Relayer incentives
- Operational treasury buildup
Fee Breakdown Example During a Bridge Transaction
| Fee Component | Example |
|---|---|
| Message Passing Verification Fee | 0.001 $SUPRA equivalent |
| Service Layer Fee (token bridge) | 0.1% of bridged amount |
| Relayer Reward (from service fee) | Paid after periodic treasury disbursal |
| Committee Updater Reward | Paid after periodic treasury disbursal |
- The net amount minted as supETH will be slightly less than 1 ETH after fees.
- All fees are transparent and visible during the bridge confirmation step.
Incentivizing Liveness
Both relayers and committee updaters are permissionless roles that ensure network liveness and decentralization.
They are incentivized through fee rewards:
| Actor | Task | Incentive Source |
|---|---|---|
| Relayer | Submit proof bundles | Treasury payouts via Service Layer Fee |
| CommitteeUpdater | Update Sync Committee public keys | Payouts via Verification Fee |
Without sufficient rewards:
- Relayers may delay proof submissions
- Committee updates may lapse, compromising security
SupraNova’s modular fee and reward system ensures both roles remain sustainably incentivized.
Testnet Fee Settings
- Some fees (especially the Verification Fee) are reduced or set to zero for testing purposes.
- The full fee model will be enforced at Mainnet launch.
Fee Model for our Ethereum to Supra Bridge protocol
This protocol involves a Token Bridge Service and a Message Passing Layer. The model details various fees and rewards, including:
- Service Fee (S)
- Relayer Rewards (RR)
- Committee Updater Rewards (CUR)
- Relayer Expense (RG)
- Committee Updater Expense (CUG)
- Verification Fee (V)
Key points of the model:
- Users pay a Service Fee (S) and gas costs when initiating a bridge request.
- Relayers are compensated with Relayer Rewards (RR) that cover their expenses (RG).
- Committee Updaters (CU) are rewarded (CUR) for updating Ethereum sync committee public keys to Supra, covering their expenses (CUG).
- RG and CUG are treated as constants determined by the Admin.
Fee Derivation Formulas
Given traffic estimate X, and gross margins SM, VM, CUM, RM:
CUR = CUG / (1 - CUM)V = (CUR / X) / (1 - VM)RR = (V + RG) / (1 - RM)S = RR / (1 - SM)
Tiered Service Fee Structure
To accommodate varying bridge volumes, SupraNova introduces a tiered service fee model based on the value bridged in USDT:
| Tier | Bridged Value Range | Service Fee Rate |
|---|---|---|
| Micro | < $5,000 | 0.5% |
| Standard | $5,000 – $100,000 | 0.3% |
| Whale | > $100,000 | 0.2% |
SupraNova Address Details
| Network Name | Hypernova | Token Bridge |
|---|---|---|
| Ethereum Sepolia | 0x50888Fc24e1224E12f5C8a31310A47B98b2A7f75 | 0x71eb89D6D0d6ED44526dd8EAcb956735934eC2d5 |
| Supra Testnet | 0x3ab1136a5dbb76b923d2b02f95b042f5d80b70218a0395755eafb63d4eefc340 | 0x76b38ad503118cb7749a835d965b023a2fe4801dba736bfa66e18d1f0339695c |
| Ethereum Mainnet | 0xEF7238503Fdd7671d85F3Cc5e4B9d7D90e99bFF1 | 0x7cECd42A15A691EF693512b1D508F1465ec5DA16 |
| Supra Mainnet | 0xda20f7d0ec813c751926f06004a10bc6ee1eefc96798f6a1aa31447ee146f932 | 0xda20f7d0ec813c751926f06004a10bc6ee1eefc96798f6a1aa31447ee146f932 |
Asset Details
Testnet
| Asset Name | Ethereum (Lock) | Asset Name | Supra (Mint) |
|---|---|---|---|
| WETH | 0xfFf9976782d46CC05630D1f6eBAb18b2324d6B14 | supETH | 0x1a57888bfcd31ef82a8e3dac93db14335b36f9228d5f050b722151ae2a77153a |
| USDC | 0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238 | supUSDC | 0x3ca17a5b04d826f9be112c319e003b3a79b2682c40613876023758dbb0d03e96 |
| USDT | 0xaA8E23Fb1079EA71e0a56F48a2aA51851D8433D0 | supUSDT | 0x2946e0f1a942ab8eb6f763f19da3d7540609aba8b00fb54e680cac5e048f8d0 |
| SolvBTC | 0xE33109766662932a26d978123383ff9E7bdeF346 | supSolvBTC | 0x420c8751a043b5b216cf02a011b0d563f3638eb082f91f0d879254e388f2b53a |
| WBTC | 0x29f2D40B0605204364af54EC677bD022dA425d03 | supBTC | 0x7ca33bcce4f4bb7904ac7b46e3613b6b62dae55cc89923706aac1ad1c244e3e6 |
Mainnet
| Asset Name | Ethereum (Lock) | Asset Name | Supra (Mint) |
|---|---|---|---|
| WETH | 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 | supETH | 0xe4af154ade9551e7f58a23b8f727ae2dca050f1b74582bb518ba361c889d246d |
| USDC | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | supUSDC | 0xf90b4b9d4a9d87c39fb3140513e52edc3ead5eaddcb9881b02becdeb63c5793d |
| USDT | 0xdAC17F958D2ee523a2206206994597C13D831ec7 | supUSDT | 0x7b6463ca7a54ee37e113c8333db9c0af49de39555ee1cb44837db4c085f8964 |
| SolvBTC | 0x7A56E1C57C7475CCf742a1832B028F0456652F97 | supSolvBTC | 0x224bee573e0ae84ba7f1eee4f7063a945ad7a268bea7ab9e004f6890177a480b |
| WBTC | 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 | supBTC | 0x348b1a4fa68803cbda3b50326a90e59b21e80c3ced93588b20950b5c0697a67e |
Asset Transaction Limit
Mainnet
| Asset Name | Max Global Limit | Per Transaction Limit |
|---|---|---|
| ETH | 23000000000000000000 (23 ETH) | 4500000000000000000 (4.5 ETH) |
| USDC | 100000000000 (100K USDC) | 20000000000 (20K USDC) |
| USDT | 100000000000 (100K USDT) | 20000000000 (20K USDT) |
| SolvBTC | 1000000000000000000 (1 solvBTC) | 200000000000000000 (0.2 solvBTC) |
| WBTC | 100000000 (1 wBTC) | 20000000 (0.2 wBTC) |