Every operation that matters

Questions

• 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 →
• Can someone bypass the rules through the interface?

  No — the interface cannot override policy. The same on-chain rules apply whether the request comes from the Platform, from your own application through the Protocol, or from a script, because enforcement sits in the contract rather than in any of the things asking.

  Pre-execution security →
• Do we have to use your application?

  No. The Platform runs these operations in the browser; the Protocol builds the same rules into systems you already run. They enforce identically because they enforce in the same place — the contract — so the choice is about where your team works, not about how much control you get.

  Build on the Protocol →