Bungee <> Eigen Collab

Introduction

Cross-chain markets/intents are highly inefficient today because they rely on fillers who use their own inventory (active liquidity) to fulfill user orders. It's obvious that the number of fillers in the ecosystem today is small and will likely remain small due to the high requirements of capital and complexity of the role.
To make cross-chain markets more efficient, we need to ease up on the requirements and reduce the cost of participation. Instead of market-makers who rely on "active liquidity," we want to have "passive liquidity" participate in the system as well.
NOTE: People usually refer to these "fillers" as solvers, but they are not the same. Solvers, as coined by Cowswap, are entities that "route," and fillers, as defined by Uniswap, are entities that "market make." The difference is important because the requirements and complexities of the roles differ a lot.

Enabling Real Solvers

Enabling Real Solvers
Solving in the cross-chain market would look like what people use aggregators like Bungee today for, i.e., route their cross-chain requests via the best available mechanism. We have a lot of capital-efficient solutions.
We have a lot of mint/burn bridges that are really capital-efficient; why use MMs when there is an alternate 0 cost solution?
Off-chain actors should be able to route via mint/burn bridges like CCTP, Native bridges, etc., as they are great for moving size and are secure.
Why hasn't this happened so far?

Solvers are possible in swap markets because we have atomicity, i.e., as a user, you can hand over funds to a solver, the solver can route, and the smart contract can ensure users get funds back at the end of "tx execution"
Solvers aren't possible across chains due to loss/lack of atomicity

So instead of atomicity in cross-chain markets for security, users need to rely on capital-at-risk.
Today, fillers/market-makers use active capital to do so, which is limiting as highlighted above; we want to use passive capital instead via StakeSure-like mechanisms.

Bungee has tried a version of this before, read more here but decided to end it as it was not the best implementation of the idea and hit the wrong tradeoff. Read more about bridge protection here

Cross-chain solvers will buy "capacity" to route via restaked capital. For example, if a user wants to move funds across chains, say 100 USD worth, a solver with 100 USD capacity (aka restaked capital) will be able to route user funds via any existing medium.
The capacity is replenished for the solver upon completion.
If the solver is unable to fulfill the intent, restaked capital is slashed.

Bungee Listing Service

Bungee Protocol will be a marketplace of solvers and fillers. Solvers will route and fillers will market-make.
Bungee Listing Component will have 3 listing methods:

Whitelisted Routes: 0 capital cost requirement, routes voted in by bungee governance, highly secure routes, native bridges, CCTP, etc., are target routes
Staked Routes: Restaked passive capital, used to buy capacity by off-chain agents to route user funds and fulfill user intents. Any bridge like Stargate, Hop, etc., are targets and will be auto-integrated by off-chain agents
Permissionless Routes: Off-chain agents using their own inventory to fulfill user intents

Bungee Auction

Bungee Auction will run off-chain, and solvers/fillers and other off-chain agents will compete to route user requests via all 3 listing methods, ensuring users always get the best outcome possible while Bungee gives them the guarantees they need.

EigenLayer Collab

We want to understand how to use EigenLayer to enable the staked-capital routes.