Movement Explorer & Movescan

The problem

Maintaining a fork of an actively developed upstream while diverging on networks, branding and chain semantics. Each sync means resolving the conflicts by hand.

What I did

• Kept the fork synced with upstream Aptos Labs across repeated merges.
• Added the Suzuka, Porto and Bardock networks and cleared APT-specific assumptions.
• Labelled known addresses so users can read flows: Bybit, Gate, KuCoin, MEXC, LayerBank, MovePosition, Echelon. Upstreamed that work to Aptos Labs.
• On Movescan: fixed state initialisation, deduplicated token holdings, handled uninitialised accounts, and stopped counting zero-balance holders.

Stack