Last updated
Last updated
Pangolin's UI was originally a Uniswap V2 fork. As we've progressed on our multi-chain journey, it has become apparent that Uniswap's codebase was never designed to take into account a multi-chain paradigm. As part of the migration to our new UI, we've moved all our new multi-chain components into a separate repository that will allow us to decouple from the original Uniswap code incrementally.
We are firm believers in modular architecture and as such any widget you can see on Pangolin's new UI is available as a component. For example, Honeycomb allows any project to import Pangolin's customizable swap widget into their website.
Another common use case is supporting a Multi-VM-Wallet via your application. Now all you need to do is import Pangolin's wallet component.
Note: We may move this data to our Directus Headless CMS in the future.
We use Directus for our headless CMS and deployed the following data end points:
Our token lists will eventually come directly from the API.
We currently use the following external APIs:
We use Gelato in the backend to feature limit orders through Pangolin's swap widget.
Subgraph schema for querying Pangolin Exchange's contracts
We have linked our deployment to our branches, specifically dev and master. This means that anytime a deployment occurs on the dev branch, a deployment will automatically trigger to deploy the updates to and for master it will deploy to .
Key thing to take note of here is the interface. This interface will define each chain Pangolin is live on as well as the key contract addresses. The Interface repository will then use a in the package.json which will then dynamically display the chains that are live.
Also refer to our chain-specific Contracts for , , , , and .
Coingecko API - → provide historical prices data on our portfolio component
DeBank API - → to show your portfolio balances
News
Knowledge Base
Tokens
dApp Overview
