Learn it. Verify it. Build with it.
Our writing on operational security, the documentation and code behind the technology, and what has — and hasn’t — been independently reviewed.
Thinking on operational security.
Written by the Particle CS team. Filters and the full index live on the blog.
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.
Go deeper.
How accounts, roles and execution conditions work — for operators and developers — and the source behind them.
Quickstart
Integrate one control and test an allowed, a denied and a governed request.
docs.bloxchain.app → (opens in a new tab)Integration guide
How applications connect to the Protocol’s controls.
Developer docs → (opens in a new tab)Source code
The open-source Bloxchain Protocol (MPL-2.0; examples licensed separately) — read the enforcement yourself.
GitHub → (opens in a new tab)Protocol whitepaper
The design of the Bloxchain Protocol, in long form — state abstraction and secure on-chain operations.
Read the whitepaper →What’s been reviewed — and where the review stops.
We state scope before conclusions. A deployment, an audit and a product release are different facts, and we keep them separate.
Reviewing the technology in depth?
Security reviewers, integrators and researchers — we’re happy to go through the details.