Comment on page
The swap widget is the GUI end users will use to perform their swaps. It will be integrated into each project's own app or website. Project teams can choose to use the default swap widget that Native created or create their custom widget using the Native SDK or API. Each project will have their own swap widget; these widgets are differentiated by their API keys.
The on-chain Router contract helps coordinate the single and multi-hop swaps, check to make sure that the slippage for the entire transaction is within the specified amount and wrap/unwrap of wrapped native tokens if necessary.
The on-chain Pool contract is where the swap logic is handled in a swap.
The Treasury is where the assets for pool are stored. This can be any EVM compatible wallet: Hardware wallets, EOA wallets or Smart contract wallets. The only linkage between the Treasury and the Pool is the allowance given by the wallet owner for the specific token.
The Native Backend is a relay hub for the frontend to help get and forward data to the other components of Native.
The only job for the Signer is to sign transactions. It will get the private key from the secured container by using the known public key. A signature will be generated based on the EIP712 spec.
The pricer is what houses the list of available pricing models teams can choose when setting up a pool. Both on-chain and off-chain pricing models are supported by Native. For on-chain pricing models like Uniswap V2, there are separate smart contracts for each pricing model.