Thinking on operational security.
Written by the Particle CS team. For documentation, the whitepaper and security evidence, see the resource library.
7 posts
When the custodian’s signing desk is the breach
Leaving assets with an exchange means you inherit their people, tools, and signing stack.
When the approved withdrawal is the theft
A withdrawal can look approved inside the company and still be the theft.
The risk a valid signature doesn’t cover
A valid signature proves a key authorized a transaction. It doesn’t prove the destination, role or approval path matches your policy.
Multi-phase security: a practical framework for decentralized operations
Signing, approvals and team wallets each answer part of the problem. A governed operation is the operating model that holds them together.
Why approvals alone don’t prevent costly on-chain mistakes
Adding approval steps feels like control. If those approvals aren’t bound to what the chain will execute, irreversible mistakes can still ship.
Why multisig doesn’t solve team governance
More signers reduce single-key risk. They don’t define what your team is allowed to do on-chain — or prove why a move was permitted.
Why wallets don’t scale for teams
Team features help share access. They don’t turn a blockchain account into an operating environment for how an organization acts.
Looking for docs or the whitepaper?
The blog is one shelf of the library — documentation, source and security evidence live next door.