Eddie
Eddie
As a bridge user, when I exceed slippage limits I need to be notified and have clear/working options
There are two parts to this: 1) https://github.com/connext/nxtp/issues/2094 2) https://github.com/connext/nxtp/issues/1878
> @just-a-node Do any major integrations need this ASAP for the initial launch? ruthlessly prioritizing the issues Not for initial launch - if they need callbacks executed they can specify...
Makes sense to group by domainId and time range. This will be similar to how Pool metrics like volume and APY will be broken down. Even further, we might want...
We have a contrived permissioned example but I'd like to keep this up to implement a governance-focused example.
Default slippage on UI is 3%, can be overridden on sdk call. Currently, UI offers 1%, 2%, and 3% as well as custom input. WETH pool exists and there is...
This can be calculated using `calculateTokenAmount` on the user's input for tokenX and tokenY.
Zapping into position isn't necessary for our pools because users can add liquidity in any proportion of tokenX/tokenY, even fully single-sided. Depending on the current reserves, the deposit can have...
Fixing individual bugs for this.
Close as we will basically have this done with the chain abstraction UI template