# Proposal: Bridge Back to the CarbonDeFi Vortex

- Space: [Bancor](https://snapshot.box/s:bancornetwork.eth.md)
- Author: 0xdfCAD9Da6649a47D808a30A7707de5a54aA0aa21
- State: Rejected
- Voting type: Basic
- Start: 2025-01-19 15:00 UTC
- End: 2025-01-22 18:00 UTC
- Votes: 7
- Quorum: 4,722,576 voting power
- Discussion: https://gov.bancor.network/t/proposal-bridge-back-to-the-carbondefi-vortex
- Open in Snapshot: https://snapshot.box/#/s:bancornetwork.eth/proposal/0x07f6e49549caa27f4bbc25821d97450bc603c19e896a950cbb753c10731c4c3e

## Results

- For: 667,895.94 voting power, 25.0%
- Against: 0 voting power, 0.0%
- Abstain: 2,000,000 voting power, 75.0%

## Proposal

# TL:DR

* Bancor protocols, CarbonDefi & ArbFastLane, have generated fees on multiple EVM chains
* A recent proposal has described how these fees should be converted into a single token https://vote.bancor.network/#/proposal/0x82b918fd7d51809102bb0c3620ce22959e49b5ccdf29228da42360e48edadd46
* This proposal outlines a specific method to send these tokens to the Carbon Vault on Mainnet (https://etherscan.io/address/0x60917e542addd13bfd1a7f81cd654758052dadc4)
* From the vault, anyone can send these to the vortex by calling execute: https://docs.carbondefi.xyz/contracts-and-functions/carbon-vortex-functions/write-functions/execute
* After execute is called, the specified tokens are sent to the Carbon Vortex on mainnet (https://etherscan.io/address/0xD053Dcd7037AF7204cecE544Ea9F227824d79801)
* This new contract is something that anyone can trigger via a public function

## New Bridge Function

* A new contract associated to each Carbon Vortex will have a new public function called “bridge()”
  * This does not include Ethereum
* The details of this function on each chain will be different to fit the relevant bride available for this chain
* On execution:
  * Indicate amount or send the full currently available budget of the token
  * Submit a transaction to the bridge
  * Destination on Ethereum will always be the carbonVault address

Note 1: This proposal suggests no caller incentive for this Function as it is likely to be triggered by someone in the community who does not require a financial incentive - this also simplifies the contract.

Note 2: For safety, we should enforce minReturn to prevent bridge actions that "leak" funds in the process as a result of low bridge liquidity.

## Bridge Function

1. SEI to Ethereum

Consolidate all tokens into wETH
Bridge: Stargate V2

2. Celo to Ethereum

Consolidate all tokens into wETH
Bridge: We will use their upcoming native bridge

3. Base to Ethereum

Consolidate all tokens into ETH
Bridge: Stargate V2

4. Fantom to Ethereum

Consolidate all tokens into wETH
Bridge: Stargate V1

5. Mantle to Ethereum

Consolidate all tokens into wETH
Stargate V2

6. Linea to Ethereum

Consolidate all tokens into ETH
Stargate V2

7. Blast to Ethereum

Consolidate all tokens into wETH
Bridge: Across

8. Telos to Ethereum

Consolidate all tokens into wETH
Bridge: LayerZero

9. IOTA to Ethereum

Consolidate all tokens into wETH
Bridge: Stargate V2

# For:

Bridge back to the mainnet as described above

# Against:

Take no action

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

