💱Deployed from factory DEX
This contract would be deployed after calling add_pool the Factory entrypoint. Contract is almost close to Standalone version of DEX contract by ABI and storage. The distinction of contracts described in The main difference in implementations.
Initialization of contract
The initialization section describes methods that are called only by the Factory
contract. These methods are included in start_dex call and used for initial setup and start DEX pool.
Contract storage
Storage of contract differs from Standalone only with excluding developer config in exchange of adding factory address and pausing of contract.
📄Storage and types overviewCore DEX methods
Main methods of DEX, that are able to use by anyone. These methods include investing, swapping, and divesting. Also, there are additional methods for staking QUIPU tokens for earning additional rewards and claiming referral rewards.
🔵DEX methodsDeveloper method
This entrypoint should be called only by developer
address of Factory contract.
This entrypoint is designed to claim developer rewards from a specific contract (DEX pool).
claim_developerAdmin methods
These entrypoints should be called only by admin
address.
The next section is about entrypoints for managing fees, "A" constant change, editing the manager list, and changing an admin address.
🛑Admin methodsLast updated