Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridge Sponsored Gas (Initial) #835

Open
0xmovses opened this issue Nov 11, 2024 · 0 comments · May be fixed by movementlabsxyz/aptos-core#104 or #896
Open

Bridge Sponsored Gas (Initial) #835

0xmovses opened this issue Nov 11, 2024 · 0 comments · May be fixed by movementlabsxyz/aptos-core#104 or #896
Assignees
Labels

Comments

@0xmovses
Copy link
Contributor

Summary

Currently in testnet the bridge requests funds from the faucet and gives those funds to the recipient associated with the bridgeTransferId so that the user can call complete.

There is no upperbound to the limit and this implementation could be abused for mainnet, also the faucet is of course not available in mainnet.

Bridge Sponsored TX with upper bound

Instead of the bridge requesting funds from the faucet, the bridge operator can have an amount of MOVE in its account so that it can transfer those MOVE tokens to the user directly. If the bridge operator does not have enough balance, it will request those funds from a pool to replenish its sponsored TX.

This process should only occur IF the users MOVE balance is 0.

NB. The Bridge Operator Account takes this cost on initially. Later this cost will be covered by full gas estimation logic for both sides of the swap and the sponsored tx fee is included in that fee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant