An announced AMM is not a liquid market until contracts, reserves and repeated trading are visible.
Early infrastructure concentrates contract, bridge, oracle and administrator risk.
Key takeaways
Confirm the execution environment. Kaspa-native assets and external representations may use different layers.
Inspect pool ownership. Liquidity can be removed or concentrated.
AMM math is only one layer. Routing, front ends and bridges can fail.
Incentives distort TVL. Capital may leave when rewards end.
Status audit
Locate controlled official documentation, deployed addresses, verified source, audits and recent transactions. If these cannot be cross-referenced, retain only an educational explanation.
Pool analysis
Measure reserves, price impact, fee tier, LP ownership and the exact asset backing. A ticker does not prove a canonical token.
User test
Use a separate wallet and small amount, then complete swap, LP deposit and withdrawal before larger exposure.
Decision checklist
Verify current official documentation, exact contracts or legal entities, administrator permissions, fees, liquidity and the full exit path. Test a small transaction and record what happens when an interface, oracle, bridge, operator or counterparty fails.
Keep a dated baseline of addresses, reserves, governance roles and normal withdrawal results. Separate technical execution from economic and legal outcomes: code can work exactly as designed while a user receives an illiquid claim or has no practical recourse.
Before increasing exposure, model four stresses: the main interface disappears, market depth falls sharply, an administrator changes a critical parameter and the normal redemption route stops. Decide which evidence triggers exit and retain enough native gas and independent wallet access to act without customer support.