Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Using unbacked emission of crvUSD for fast bridge from L2.
Purpose
L2 native bridges have 1 week delay what works bad for crvUSD peg and LLAMMA Lend. Can use unbacked emission to cover associated risks and allow crvUSD to peg better and grow
Contracts
Vault
Contract holding unbacked emissions. Should mint x crvUSD only when there is an associated x crvUSD in native L2 bridge. This should be abided by minters (e.g. bridge aggregator).
Contract doesn't support any minting queue, so minters might need to compete for transaction when vault is drained. Also usually native bridges need claim transaction on L1, so minters should claim funds before minting.
There can be several minters allowing it to be both: fast bridge on bridge to vault event and bridge through dedicated contract FastBridgeL2.
FastBridgeL2
Contract initiating bridge transaction and associated message to minters (bridge aggregator). It has own throughput limits to loosen Vault queue.
Open questions