nolus-protocol / webapp Goto Github PK

При въвеждане на голямо число, което превишава максималния допустим обхват на цели числа (Number.MAX_SAFE_INTEGER) или попада извън минималния допустим обхват (Number.MIN_SAFE_INTEGER), се появява грешка със съобщение 'Integer out of range'.
Освен това, полето за down payment се скрива

При смяна на активите от DYDX с NTRN, стойността в полето със сума се предава грешно към към актива NTRN.
Стойността се появява като "0.000000000000000000" и се прехвърля към полето на NTRN, въпреки че стойността на NTRN не е толкова много нули.

Users can currently request to withdraw more assets from the LPP than the contract balance has as available, leading to failed transactions without clear feedback. Implementing a validation check to inform users when their withdrawal amount exceeds the available balance would enhance usability and reduce unnecessary errors.

Upon attempting a withdrawal, if the requested amount surpasses the available balance, an error message should be displayed : "Withdrawal amount exceeds available balance: [LPP's Available Balance]"

LPP balance can be queried with lpp_balance:[]

When switching the network from "NLS" to another, "NLS" is still displayed in the picker while loading

1. При изтегляне на стейкинг награди, вместо да се показва сумата във валутата NLS, тя се показва във валутата OSMO.
2. В допълнение, десетичните цифри на сумата се закръглят неправилно, като например сумата 12.416491 се показва като 12.000000

When entering an invalid amount for a transfer in the subsection #receive, the system does not display the message "Invalid amount", similar to the subsection #send

Objective:
To create a consistent transaction confirmation flow for both swaps and token transfers by reformatting the data on the confirmation, pending, success, and error screens.

Confirmation Screen

Design Reference: Figma Design - Confirmation Screen

Requirements:

• Display the following information:
  • Amount (from)
  • Address (from)
  • Network (from)
  • Amount (to)
  • Address (to)
  • Network (to)
• If the transaction requires two signatures, display the following warning text:
  • "This route requires 2 transactions to be completed. You will be prompted for a second signature after the first transaction is finalized."

Pending Screen

Design Reference: Figma Design - Pending Screen

Requirements:

• Display the following information:
  • Amount (from)
  • Address (from)
  • Network (from)
  • Amount (to)
  • Address (to)
  • Network (to)
  • Transaction state
  • Transaction hash (with a link to the explorer)
• Include an option to minimize the popup.
• Include the following information text:
  • "You can minimize this window and track the progress on the History page."
• If the popup is minimized, the transaction confirmation or error screen should not be displayed.

History Page

Design Reference: Figma Design - History Page

Requirements:

• Display pending transactions with a loader and a pending state.
• Include a "More Details" button for pending transactions:
  • If clicked, it should lead users to the Pending screen where a signature can be invoked if required.
• If the transaction has failed, the "Details" button should lead the user to the error screen where the error details will be displayed.

We aim to enhance the transfer functionality by utilizing the Skip API for all supported Cosmos assets/chains and enable direct transfers from EVM networks via CCTP and Axelar. This enhancement will initially support transferring assets from Ethereum, Arbitrum, and Base to Nolus.

Supported Transfer Routes:

NLS (Axelar)
Ethereum <--> Nolus (Axelar)

WBTC (Axelar)
Ethereum <--> Osmosis <--> Nolus
Arbitrum <--> Osmosis <--> Nolus
Base <--> Osmosis <--> Nolus

ETH (Axelar)
Ethereum <--> Osmosis <--> Nolus
Arbitrum <--> Osmosis <--> Nolus
Base <--> Osmosis --> Nolus

USDC (CCTP)
Ethereum <--> Noble <--> Osmosis <--> Nolus
Ethereum <--> Noble <--> Neutron <--> Nolus
Arbitrum --> Noble --> Osmosis --> Nolus
Arbitrum <--> Noble <--> Neutron <--> Nolus
Base <--> Noble <--> Osmosis <--> Nolus
Base <--> Noble <--> Neutron <--> Nolus

Designs
Recieve From Cosmos Chains
https://www.figma.com/design/dUbyvg5tejjYPVf69Haixv/Protocol-Webapp?node-id=12-4500&m=dev

Receive From EVM
https://www.figma.com/design/dUbyvg5tejjYPVf69Haixv/Protocol-Webapp?node-id=5726-10532&m=dev

Send To Cosmos Chains
https://www.figma.com/design/dUbyvg5tejjYPVf69Haixv/Protocol-Webapp?node-id=12-2488&m=dev

Send To Nolus
https://www.figma.com/design/dUbyvg5tejjYPVf69Haixv/Protocol-Webapp?node-id=3755-6345&m=dev

Send To EVM
https://www.figma.com/design/dUbyvg5tejjYPVf69Haixv/Protocol-Webapp?node-id=5726-10532&m=dev

Tasks:

• Integrate Skip API for all supported Cosmos assets/chains.

• Enable direct transfers from EVM networks via CCTP and Axelar.

• Implement transfer routes for NLS, WBTC, ETH, and USDC as specified above.

• Ensure proper handling and routing of assets between Ethereum, Arbitrum, Base, Osmosis, Neutron and Nolus chains

Known Complications that Need to be Handled in the UI:

• Two transaction routes
• Long pending states

Or put it differently, define a DEX-specific currency package and let most of the other packages depend on the generic one.