Roadmap

From one transaction to living in your workflow.

The analysis engine is a standalone library. The goal is to put it where the work actually happens — your editor, your tests, your CI — and to pair static structure with real simulation. Date ranges are approximate and tentative.

Timeline
Now Phase 1

Multi-chain transaction analyzer

Analyze any transaction on Sui, Aptos, or Movement — by digest, hash, version, or pasted JSON, on mainnet or testnet. For Sui: Kinetics builds the dataflow graph, tracks taint from inputs to sinks, checks linear-resource conservation, and attributes gas. For Aptos and Movement: it decodes the payload, balance movements, events, and write-set. All in your browser, free, no account.

Next Phase 2 · Q4 2026

Library, CI checks, and private simulations

Ship the analyzer as a library you call in tests and CI — assert no dangling results, a bounded dependency depth, or that only expected inputs reach transfer sinks. Then simulation: counterfactual dry-runs against live mainnet state, in private environments where your inputs and outputs stay encrypted, enforced by Move policies on Sui's Seal framework.

Planned Phase 3 · Q1 2027

Virtual testnets

Fork mainnet state into isolated environments in seconds, and deploy and test against real liquidity before touching mainnet. Cross-chain analysis across Sui, Aptos, and Movement already ships in Phase 1; this phase adds stateful forking on top of it.

Planned Phase 4 · Q3 2027

Safety proofs and enterprise features

Cryptographic proofs that a contract passes defined safety properties, allowing audit confidence can be shared without revealing implementation details. Plus, the controls teams need to run Kinetics across an organization.