If you want the baseline overview of Analog first, start here: Analog (ANLOG) – The Omnichain Liquidity Hub Ambition. This note focuses on what investors often miss: how to evaluate omnichain liquidity projects as operational systems with measurable traction and risk.
1) The real problem: fragmentation costs and who pays
Omnichain liquidity sounds abstract until you price the friction. Fragmentation creates hidden costs: slippage, duplicated liquidity incentives, delayed settlement, and security overhead. The first diligence step is to map who is expected to pay for coordination and where value capture can realistically sit.
- Identify the fee payer: end users, apps, LPs, or integrators.
- Define the paid unit: message, routed volume, execution, or listing.
- Check substitution risk: can users simply stay on one chain and avoid the product.
2) Adoption signals that matter more than announcements
Partnership counts are weak signals. In interoperability, the durable signals are usage and retention. Track what is hard to fake and expensive to sustain without real demand.
- Routed value and frequency: not just peaks, but steady weekly flows.
- Active integrators: number of apps sending meaningful traffic, not just SDK downloads.
- User repeat rate: wallets returning after first use, indicating product market fit.
- Cost curve: does usage grow faster than incentives paid out.
3) Security posture: assume cross-chain is hostile territory
Cross-chain failures are historically among the most expensive incidents in crypto. A serious diligence process treats security as the product, not an appendix.
- Audit coverage and recency: multiple independent audits plus remediation evidence.
- Operational safeguards: rate limits, circuit breakers, and incident playbooks.
- Validator and signer design: how keys are protected and how upgrades are governed.
- Bug bounty economics: bounty size that is credible relative to assets at risk.
4) Token value capture: where the economics can actually close
Many infrastructure tokens struggle to convert activity into token demand. The key is a clear link between usage and scarce resources: staking security, fee payments, or privileged execution.
- Fee sink: are fees paid in token, and are they meaningful relative to emissions.
- Staking demand: is security demand proportional to routed volume and risk.
- Unlock schedule: supply releases that can overwhelm organic demand.
- Treasury runway: how long incentives can be funded without harming price stability.
5) Competitive edge: integration depth beats a better slogan
Interoperability is crowded. A durable moat is usually not a feature list but an integration wedge that becomes costly to replace.
- Developer experience: time to integrate and time to debug are decisive.
- Latency and finality handling: predictable execution under real network conditions.
- Liquidity efficiency: less duplicated capital for the same user experience.
- Composable partnerships: integrations that compound rather than one-off pilots.
How to use this checklist with Analog
Analog is positioned as an omnichain liquidity and messaging layer. The diligence question is simple: are real apps routing real value repeatedly, with security controls that can survive adversarial conditions, and with economics that can outgrow incentives. If the answers trend positive across quarters, the thesis graduates from narrative to infrastructure business.
