Skip to main content

Bloxchain Protocol

Build the same rules into your own product

The open-source foundation the Platform itself runs on. Read it, check it, and use as much or as little of it as you need.

Start quickstart (opens in a new tab) View source (opens in a new tab)
install 
npm install @bloxchain/sdk @bloxchain/contracts viem
ownership.ts 
// One person asks —
await account.transferOwnershipRequest({ from: owner });

// — and after the waiting period, a different person approves.
await account.transferOwnershipDelayedApproval(txId, { from: approver });

Reference implementations

Start from one of these, not from scratch

Each of these is already in the repository, together with the building blocks it uses. Adapt one to your own case rather than designing the governance from first principles.

  • A governed account

    The full set: named roles, waiting periods, and limits on what may be called — one account your whole team works through.

    All three building blocks

  • A vault

    Hold assets under ownership controls and a waiting period, without taking on roles you do not need.

    One building block

  • A token or tokenized asset

    Issue and manage supply through the same approvals as everything else, so issuance is not a separate trust story.

    One building block

  • A payment schedule

    Recurring or conditional payouts that still have to clear the same checks before anything leaves.

    One building block

  • Rules over a multisig you already use

    Keep the setup your team knows, and add waiting periods and limits on what it may call.

    One building block, as a guard

You choose how much to take, and you choose it per deployment. Nothing here is all-or-nothing and nothing is a mandated pattern — start from the shape closest to your case, take the building blocks it needs, and leave the rest.

See the reference implementations (opens in a new tab)

Why open

Why we give it away

Published under MPL-2.0. Use it commercially, combine it with your own closed code and keep that yours — the only ask is that changes to these files stay open.

Security you can read
A control layer you cannot inspect is a promise, not a guarantee. The contracts, the tests, and the audit report are public, so you can verify the enforcement rather than take our word for it.
No dependency on us
The policy lives in your own contracts. If you never use our hosted Platform — or stop using it — the rules still hold. There is no vendor whose failure becomes your outage.
The barrier was economic
Bank-grade operational controls existed, priced for institutions. Publishing the policy layer as open source removes cost as the reason a team ships without protection.
No framework to adopt
You are not signing up to a way of building. Add one piece to a contract you already run and leave the rest of it exactly as it is — nothing here asks you to start again.

And here is what you can check

Licence
MPL-2.0
Independently reviewed
Nethermind (NM_0828) — scope: core protocol contracts
Packages
@bloxchain/sdk and @bloxchain/contracts
Networks
Sepolia today. Ethereum mainnet coming soon.

What ships

What you build with

Packages, source, and a path from an empty project to a first governed operation.

What these contracts enforce

Build on rules you did not have to invent

Start quickstart, or read the code first. Both start in the same place.

MPL-2.0 · Sepolia today. Ethereum mainnet coming soon.

Start quickstart (opens in a new tab) View source (opens in a new tab)
Prefer not to build? Explore Platform