Anoma Explained: Intents, Solvers and Privacy-Preserving Coordination
An intent describes acceptable outcomes rather than a fixed transaction path.
Solvers can improve coordination while introducing competition, censorship and information-leakage questions.
Key takeaways
Users state constraints. The system searches for compatible state transitions.
Solvers find matches. Their incentives and access to order information matter.
Privacy requires defined leakage boundaries. Hiding values is not the same as hiding metadata.
A broad architecture needs working deployments. Research claims must be separated from production capability.
Intent execution
A wallet expresses an outcome, such as exchanging within a limit. Solvers or counterparties discover compatible intents, construct a candidate transaction and submit it for verification under the resource rules.
Benefits and tradeoffs
Users can avoid prescribing routes and may receive better matches. They also need protection from solver manipulation, delayed execution and unwanted disclosure.
Developer evaluation
Build one narrow flow, measure completion and failure, inspect settlement and prove which privacy properties hold under realistic adversaries.
Decision checklist
Verify current primary documentation, exact contracts or legal entities, permissions, fees, liquidity and the complete exit path. Test the smallest practical transaction and record what happens when an interface, oracle, bridge, operator or counterparty fails.
Keep a dated baseline of addresses, reserves or collateral, governance roles and normal withdrawal results. Define a stop condition before increasing exposure: lost liquidity, a missed redemption, changed administrator powers or unsupported software.
Separate technical success from economic success. A transaction can execute exactly as coded while the user receives a poor price, an illiquid claim or an outcome with no legal recourse. Record both the on-chain result and the off-chain party responsible for support, custody or redemption.