Jorge Valdeiglesias
Menu

Selected work · 01

Building Phantom Money Movement and Phantom Cash

Phantom was extending from a consumer wallet into a broader financial product. I helped validate the direction, built the first prototypes, led the production platform and roadmap through GA, and built the engineering team that took ownership before I left.

Consumer wallet · Stablecoins, payments and money movement

Visit Phantom

My role

Technical lead for Money Movement and Phantom Cash, from validating the direction and building the first prototypes through the production platform, roadmap, GA launch, and transition to a team with durable ownership.

Context

The conditions that shaped the work.

Context
Phantom was extending from a consumer wallet into Money Movement and Phantom Cash. The work brought banking, identity, payments, and multichain systems into one consumer experience.
Constraints
New regulated surfaces had to preserve a model without taking custody. Identity, compliance, data, product, and external provider responsibilities still needed clear boundaries.
Core tension
The first product needed to move quickly without turning every provider, chain, and regulated responsibility into a separate path that would be harder to extend.

Timeline

How the work progressed.

  1. 01

    Validate

    Make the direction credible

    Product definition and early platform execution moved together so the team could validate the experience and system boundaries at the same time.

  2. 02

    Prototype

    Make the product concrete

    The first prototypes exposed the provider, banking, identity, payments, stablecoin, and multichain decisions the product needed to resolve.

  3. 03

    Production

    Build and ship the platform

    The work became a production Money Movement platform and roadmap that carried Phantom Cash through GA.

  4. 04

    Ownership

    Build the team that carries it forward

    The engineering team grew around the platform and took durable ownership before I left.

Decisions

Key choices and their tradeoffs.

Preserve the custody boundary

Keep the financial experience compatible with a model where Phantom did not take custody of customer assets.

Tradeoff

The product needed more explicit responsibility boundaries across the wallet, regulated surfaces, and external providers.

Build a platform, not a sequence of isolated launches

Create Money Movement foundations that could support multiple providers and capabilities.

Tradeoff

More platform judgment was required during the first version, but later work gained a stable place to build.

Keep product and engineering connected

Use hands-on technical execution to make product questions and system constraints visible together.

Tradeoff

Early work stayed intentionally close to uncertainty instead of optimizing for a finished organization too soon.

Decision path
  1. Consumer intent
  2. Money Movement
  3. Banking and identity
  4. Payments and multichain systems

Outcomes

What changed.

  1. Built the initial Money Movement platform behind Phantom Cash.
  2. Established foundations spanning banking, identity, payments, and multichain systems.
  3. Shipped the product to GA and established the engineering ownership needed to carry it forward.

Lesson learned

When regulation and product ambition meet, clear responsibility boundaries create room to move quickly.

Continue

Next: FalconX

Building custody from first principles.

Read the FalconX case study See all selected work