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

Tempest Decoders #43

Closed
5 tasks
junkim012 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #44 or #45
Closed
5 tasks

Tempest Decoders #43

junkim012 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #44 or #45
Assignees

Comments

@junkim012
Copy link
Contributor

junkim012 commented Jan 8, 2025

Goals

  • Full LP management functionality on Tempest.
  • Tempest runs on Ambient DEX, which is different from UniV3.

Requirements

  • deposit with zap
  • deposit without zap (deposits with an s)
  • redeem with zap (withdraws with an s)
  • redeem without zap
  • How are rewards claimed?

Tempest Research:

Pairs w/ ETH

  • Only Zap ETH

Deposit ETH/rswETH: https://etherscan.io/tx/0xe42cb96363a276cde0be9300fdfc7c20fc28a483fc2d15b0f44b253f178a3369

Withdraw: https://etherscan.io/tx/0xf59b668c1572d72641593a041fe29610e8e41a2a289cb92b355e2f6ff7c8255d

Normal Pairs

Questions:

  • what is liqSlippage and swapSlippage (Ambient)?
    • on provide and burn liquidity, liqSlippage is only used if checkSlippage is true to create lower and upper bounds
    • When swapping tokens for LP to zap into LP, it checks the received amount after the swap. This is the swapSlippage
  • What is the bool checkSlippage? What is it's significance?
    • See above, on provide and burn liquidity if checkSlippage is true then it checks the liqSlippage value for liquidity
  • How does Ambient liqSlippage work?
    • If the price is out of this range at the time of trying to add liquidity (pre-tx) it fails. Seems like a variation of the deadline rather than slippage but referring to price change rather than time
This was linked to pull requests Jan 9, 2025
@CarsonCase CarsonCase removed a link to a pull request Jan 9, 2025
@CarsonCase CarsonCase linked a pull request Jan 9, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants