For businesses
The problem we work on
A wallet accumulates. Assets end up spread across addresses and networks, and the only way to move them is to sign transactions one at a time and hope the result matches what you had in mind. MovingWallet writes the plan first — the route, the estimated fees and what arrives — so the owner reads it before signing anything.
This page is about what that is, and is not, available to other companies today.
Who has this problem
Wallet and app builders
Your users already hold assets across several addresses and networks. When they want to consolidate or move out, the hard part is not the transaction — it is knowing what will happen before signing.
Treasury and operations teams
Moving funds between the organisation's own addresses is routine work done from memory. A written plan, with the route and the fees itemised, is what makes it reviewable by someone other than the person clicking.
Teams moving users off an address
A deprecated wallet, a rotated key, a product being wound down. The work is the same shape every time, and every team rebuilds it.
Where this is going
The part of MovingWallet worth sharing is the readable plan, not the interface around it. The direction is to make that plan something another product can point at — so a wallet, a dashboard or an operations tool can show an owner what a move would do, without rebuilding the routing and the fee arithmetic.
This is a direction, not an offer. Nothing on this page is available to third parties today. There is no signup, no waiting list and no programme to join.
The order is deliberate. The owner-facing flow has to be right before anything is exposed to other products; a plan that is wrong is worse embedded than standalone.
Nothing changes about custody. Whatever gets exposed, the server will not hold keys and will not sign. That is a property of the product, not a phase of it.
What exists, and what does not
One list, one state per capability, read from the same registry the Developers pages read. Nothing here is labelled by hand, so a capability cannot be one thing on this page and another thing on that one.
Preview means it exists but is not reachable from a stable address. Roadmap means it is not built, or not offered to third parties. A capability moves up only when an outside person can really reach it.
If you want the detail
What exists today, for developersThe three steps of the flow and the state of each surface.
The API, as it actually isWhy it is not open to third parties yet, in concrete terms.
What MovingWallet never doesNon-custodial by construction: the server holds no keys and signs nothing.
Cross-chain migration, end to endThe supported networks, and the limits stated as limits.
Consolidating several walletsThe shape of the problem, written for someone doing it once.
Talking to us
If your product runs into this problem, tell us what you are building and what you would need. Concrete cases are what decide which of the rows above moves first.
Talk to us about wallet migrationTo be straight about it: this is a mailbox, not a sales channel. We are not promising a response time, an onboarding path, access or terms — none of those exist yet, and saying otherwise would put this page in the same place as the claims it is here to replace.