Controls and Risks
Multiswap currently has explicit administrative controls. The Dispatcher owner can install or replace modules and perform the configuration actions exposed by those modules.
Owner powers
Depending on installed selectors, these actions include registering pools and assets, configuring fees and elasticity, setting oracle relationships, preparing and settling epochs, and changing operational settings.
That authority applies to the modules installed behind the contract address. Check the current owner and selector mappings for the deployment you use.
Asset and portfolio risks
Each registered asset carries its issuer’s risk. Stablecoins can deviate from their references. Tokenized stocks and other RWAs carry the terms, backing, transfer behavior, and operating dependencies of their token structures.
An LP Token exposes its holder to pool backing. Portfolio composition, reserve concentration, market-price changes, and the liquidity available for an exit all matter. Returns measured at external market prices depend on the portfolio’s asset performance.
Execution and implementation
State can change between preview and transaction inclusion. Minimum receive amounts protect the submitted exchange; execution applies them to the state at transaction inclusion. Token restrictions or contract failures can cause settlement to revert.
Oracle configuration affects USD reads and epoch valuation. The execution quote view avoids the extra USD-display lookup, while other workflows retain their oracle dependencies.
Independent audit status requires a published assessment of the relevant code version. Smart-contract, administrative, token, and chain failures remain possible.
Decentralization
The intended direction is progressive decentralization as the protocol matures. Assess the current owner powers and installed controls for the deployment in use.
The current testnet details are in Deployments. Production audit reports, ownership controls, and final economic terms belong with their production release.