Some things
stay yours.
An open world shouldn’t require
an open door to everything you own.
Crypto makes it easy to move between markets, applications, and new ideas. But the wallet you use to explore can also be the place where you keep your savings. Every new connection then sits uncomfortably close to your entire balance.
PHASE is a personal vault concept for Solana. We’re building around a simple principle: separate the money you use from the money you want to keep.
Two spaces.
Different permissions.
Your everyday wallet is for activity. Your vault is for reserves. Moving funds between them should be a deliberate decision, governed by rules you understand.
Reserves with deliberate access.
A defined budget for everyday activity.
The connection between them is a boundary, not unlimited access.
For example, you might keep most of your USDC in the vault and a smaller amount in a separate trading wallet. Connecting that wallet to an application should not, by itself, grant access to your vault.
One balance.
Two different jobs.
Imagine starting with 10,000 USDC. You choose a separate amount for everyday trading and keep the rest as reserves.
Your vault
9,000 USDCSet apart from your trading budget.
Trading wallet
1,000 USDCThe amount you choose for activity.
9,000 USDC stays outside the illustrated trading budget. In the planned product, moving additional funds would require separate approval.
This slider changes an illustration only. It does not connect a wallet, move assets, or configure permissions.
Set your starting budget.
Decide what stays in reserve and what belongs in your active wallet.
Connect the active wallet.
Use it with trading apps. The intended design keeps vault authority separate from that connection.
Review before adding more.
A top-up should require a new approval under your vault rules, rather than an app automatically reaching into your reserves.
Concept illustration, not a live account or a suggested allocation. Controls are still in development. Separate balances alone do not guarantee protection; program design, permissions, and key management matter.
Set the terms.
Then move on.
We’re exploring a small set of controls that make access intentional. These are design goals, not features available today.
Spending limits
Define how much a permitted wallet can receive within a period. A useful limit accounts for repeated withdrawals, not just the size of one transfer.
Approved destinations
Choose where funds may go. Adding a new destination should require its own review, rather than quietly bypassing existing restrictions.
More than one key
Require independent approval for important moves. Multiple keys only add meaningful protection when they are kept independently.
Time to reconsider
Delay selected withdrawals so you can review them before execution. Any cancellation mechanism must be enforced by the underlying system; a notification alone cannot stop a transfer.
A way out
Plan for recovery and access beyond the PHASE website. Self-custody should not depend on our interface remaining online.
Limit exposure.
Be clear about risk.
The aim is to reduce how much a compromised everyday wallet can reach. It is not to promise that funds can never be lost.
Protection is a set of enforceable boundaries.
Not a badge on a screen.
A vault still depends on its underlying programs, key management, recovery design, and the assets it holds. Bugs, compromised approval keys, and incorrectly configured permissions can undermine those boundaries. Delayed withdrawals cannot reverse transactions that have already executed.
Changes to keys, limits, and recovery settings need protection too. Otherwise, a withdrawal rule could be bypassed by changing the rule itself.
The Phase mainnet integration has not undergone an independent security audit. Read the beta limitations below before creating or funding a vault.
Two keys.
One deliberate decision.
Who controls withdrawals?
Phase creates autonomous Squads v4 vaults with two members and a threshold of two. Both members hold proposal, voting, and execution permissions. There is no external configuration authority and no withdrawal time lock. The first member proposes a SOL or USDC transfer; the second approves; either member can execute the approved transaction.
What can I deposit?
The interface supports SOL and native Solana USDC. Deposit to the displayed vault address, never the multisig configuration account called the vault ID. Keep SOL in the signing wallets for transaction fees and in the vault for token-account rent when required.
What if I lose a key?
There is no Phase recovery service. Losing either required key can permanently lock funds. Keep independent backups. Two wallets on the same compromised device are not independent protection. Member and policy changes through Squads require the vault’s on-chain approval rules; Phase does not currently expose those controls.
What if Phase goes offline?
The vault and proposals exist on Solana under the Squads v4 program, not in a Phase database. Save your vault ID and signer information. The underlying program can be accessed with Squads tooling and the required signing keys. Verify this fallback with your setup before relying on it.
What are the limitations?
Phase’s integration has not been independently audited. The underlying program, its upgrade authority, the Solana network, wallet software, and key management remain dependencies. USDC also depends on its issuer. No insurance or guaranteed protection is provided. Spending limits, destination allowlists, delayed withdrawals, and recovery are not implemented in this interface.
A working foundation.
The mainnet beta supports Phantom and Solflare, 2-of-2 vault creation, opening existing compatible vaults, SOL and USDC balances and deposits, and proposing, approving, rejecting, and executing simple withdrawals. Every operation requires your wallet signature. The server relays RPC requests and never receives private keys.
Creation incurs the Squads protocol fee, account rent, and network fees. Proposals and token accounts can also require rent. Review the transaction in your wallet. A simulation is a preflight check, not a guarantee of safety or execution.
Open Phase Vault ↗Only what you choose to share.
When you join, we store your email address, signup time, and consent to receive PHASE early-access and launch updates. If you choose to provide them, we also store your name or alias, X and Telegram handles, your intended use, and your feedback. These optional details help us understand early users and plan the product. The registration list is held in a private database, with access restricted to the project owner.
We do not ask for a wallet address, seed phrase, payment, or deposit. Automated email delivery is not active yet. Any future launch messages will include a way to opt out.