What is Bloxchain?

Bloxchain is a platform for governed blockchain operations. Operate with the Bloxchain Platform (bloxchain.app) or build with the open-source Bloxchain Protocol (smart contracts plus a TypeScript SDK). Both enforce the same on-chain policy: the Platform orchestrates, the chain enforces.

Alpha · Testnet · Local-first. The Platform runs on Sepolia today. Ethereum mainnet is coming soon. Your account list lives in your browser. The Protocol core is audited by Nethermind (NM_0828), core framework scope. Custom extensions and your own configuration are not covered by that audit. See Audit status.

Two ways to use it

Bloxchain Platform

Bloxchain Protocol

What it is

The hosted app at bloxchain.app

Open-source smart contracts and the @bloxchain/sdk TypeScript SDK

You use it to

Deploy, import and operate smart accounts without writing code

Build integrations, automations and custom deployments

Who holds the keys

You

Where rules are enforced

On-chain

The Platform never holds a key and never custodies assets. It reads on-chain state and submits the requests your wallet is allowed to make. If policy denies an action, the contract rejects it no matter which tool sent it. Integration surfaces helps you choose a surface.

What a smart account is

A Bloxchain smart account is an on-chain contract you own. It holds assets (native currency and tokens) and executes actions only through governed requests. Every account has:

Three protected roles set at deploy: Owner (controls the account and approves delayed requests), Broadcaster (one to three addresses that may submit signed transactions and pay gas) and Recovery (a fallback address that can take ownership in an emergency).
A time lock: the minimum wait before a delayed request can be approved.
Custom roles, the signers who hold them, the actions the account may perform, the gates that let a role run an action, and allowlists that restrict where value can go.

A freshly deployed account is a Vault: it holds assets but has no spending capability until you configure actions, permissions and allowlists. That is a finished, locked state, not an error. See what a new account already has. How it works walks through the full lifecycle.

Who it is for

Individuals protecting funds. Put savings behind a time lock so a transfer you did not mean can be cancelled while it is still waiting to settle, and keep a recovery address in case you lose your main wallet.

Teams running a treasury or issuing assets. Separate who may request, who may approve and who may execute. Every payment waits, is reviewed and is recorded on-chain. Mint, pause and admin changes follow the same rules for the life of the asset.

Developers. Deploy the same governed account from your own code, automate requests and approvals with the SDK, or extend the Protocol contracts for a custom deployment.

AI agents. The docs are written so an agent can read them as context and act through the SDK under the same on-chain policy as a person. See For AI agents.