Solutions · Team collaboration

Share the work without sharing keys

Each person gets the access their job needs — nobody inherits a master key.

Who may act on Transfer Assets

The argument

Instead of — Sharing a key instead of sharing control

Shared control without a shared key

Each person acts with their own key inside their own role. Nobody inherits anyone else’s — and every action is attributable.

Instead of — Co-signing that makes every action heavy

Grant exactly the operations a teammate needs, so day-to-day work moves while sensitive work still waits for a second person.

Instead of — Work that lives in one person’s browser

Requests, approvals, and cancellations are recorded as operations — what is waiting, and who it waits on, is visible.

Instead of — People changing faster than wallets do

Permissions change while the account keeps running. Someone leaving is a role change, not a migration.

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