Developers

Build on controls you did not have to write

Roles, waiting periods, and rules for external calls, already written as open contracts you compose — so the controls your reviewers ask for do not cost you a quarter.

Start quickstart View source

install

npm install @bloxchain/sdk @bloxchain/contracts viem

account.ts

import { SecureOwnable } from '@bloxchain/sdk';

const account = new SecureOwnable(publicClient, walletClient, address, sepolia);

// Who may act, and what is waiting — read straight off the chain.
const owner = await account.getOwner();

Open source: Read every line, and run it without us.; MPL-2.0
Your wallets: Any EVM wallet or WalletConnect. No account of ours in the signing path.; Non-custodial
No migration: Add one piece to a contract you already run.; Composed per deployment

Start

Start where you already are

Ways to build

However you reach it, the rules are the same

01
TypeScript SDK

Read state, see what is pending, and raise operations from your own application.
- Automation
- CI/CD
- You run signing
Core patterns
02
Solidity contracts

Deploy the governed account, extend it, or put it in front of something you already run.
- Custom modules
- Audited baseline
- You deploy bytecode
Deployment
03
Hosted workspace

The browser surface for the people who approve rather than build.
- Approvals
- No custom UI
- We operate it
Platform docs

Most teams run two: people approve in the workspace, automation goes through the SDK.

Compare the surfaces in detail

Supported

What runs where, and what to pin

Networks

Ethereum Sepolia: Official (opens in a new tab)
Ethereum mainnet: Coming soon; Core audited; official deployments and hosted availability are separate roadmap items.
Any other EVM chain: Bring your own (opens in a new tab); Public, private, or consortium — an RPC and a chain ID is the whole requirement.