Solutions · Personal holdings

A pause before your money moves

Cancel a transfer you did not mean while it is still waiting to settle.

Transfer Assets

Waiting

3.2 ETH

Policy delay18h → 0h

CancelApprove

The argument

Instead of — Hardware that protects the key, not the decision

A pause you control

High-value operations wait before they execute. Unintended requests can still be cancelled while pending.

Instead of — Backups that solve loss, not misuse

Designated parties can restore access. Changes to ownership and recovery run through the same governed path.

Instead of — Custody that trades one risk for another

Particle CS never holds your keys. Rules live in your account on-chain — with or without our interface.

Instead of — No window to change your mind

Personal holdings use the same operation model as treasury, so habits transfer if you grow into a team workspace.

This covers

Who is allowed to move funds?

Whoever you name, and only for the operations you name them for. Roles decide who may request, who must wait, who may approve, and who may execute — and the contract refuses an unauthorised call before it reaches your funds, rather than relying on an interface to prevent it.
Roles and approvals
Do you ever hold our keys?

No. Particle CS never holds your keys. Operations are authorised by your own accounts against policy that lives on-chain, so there is no custodian to trust and none to fail.
How we can be checked
What actually happens between asking and executing?

Five steps, the same under every solution: Request, Wait, Approve, Execute, Evidence. A pending operation can still be cancelled inside the waiting window.
See lifecycle
Which networks can we use today?

Sepolia today. Ethereum mainnet coming soon. The Platform is alpha · testnet · personal workspace, so treat today's scope as the honest limit rather than a roadmap.

Platform in the browser, or Protocol in your own systems.

Alpha · Testnet · Personal workspace