Skip to content
← selected work

Tooling · Various

Upstream & Open Source

Contributions upstream of Movement, and the tools I build for myself.

Period
2023 - 2026
Role
Contributor
Source
Public
View repository →

The problem

Movement runs on forks and third-party libraries, so plenty of the bugs that affect it live in someone else’s repository. Patching downstream means carrying that workaround indefinitely and re-applying it every time the dependency moves. Upstream is usually the cheaper place to fix it.

What I did

  • aptos-labs/aptos-core: an underflow fix, counterparty lock verification, a rate limiter, and fuzz tests.
  • LayerZero-Labs/devtools: rate limiter behaviour for incoming funds.
  • ThalaLabs/surf: ABI fetching and an optional address parameter.
  • fcescob/maldon: pattern-matching flags for the CREATE2/CREATE3 salt miner.
  • ethereum-lists/chains and electric-capital/open-dev-data: registered the Movement chains and ecosystem.
  • Personal: hypercore-helper for Hyperliquid, CTF work, and a set of Astro and Next sites.

Stack

RustMoveTypeScriptPython