microchainlabs GitHub

Independent cryptography lab

OPEN RESEARCH / WORKING CODE

Privacy starts
at the account.

We build the cryptography that lets smart accounts keep their signers, permissions, and policies private.

Built in Noir. Open to inspection.

A vermilion plane seen through layers of sculptural, ribbed optical glass
FIG. 01A matter of what you reveal.
THE ACCOUNT IS PUBLIC.
ITS INNER WORKINGS CAN STAY PRIVATE.
A closer look ZERO-KNOWLEDGE PROOFS
SMART ACCOUNT INFRASTRUCTURE

01 / The primitives

Four pieces.
Your account, your rules.

Start with the part your account needs. Each primitive handles a specific question about identity or permission, with a proof the chain can check.

01

ZK Labels

A role you can prove.IDENTITY

Bind a label such as “CFO” or “auditor” to a signer. Prove the binding belongs to a registry while keeping the rest of that registry private.

Merkle membershipRole-based identity
Explore ZK Labels
02

ZK Signer

Authorization. Discreetly.SIGNING

Verify an ECDSA signature inside a Noir circuit, then prove the recovered address belongs to the authorized signer set. The address, public key, and signature remain private.

secp256k1Private membership
Explore ZK Signer
03

ZK Multi Signer

A quorum, quietly reached.GOVERNANCE

Show that enough authorized signers approved a transaction. The chain checks the threshold proof; the identities of the participating signers and their signatures stay private.

M-of-N thresholdsPrivate approvals
Explore ZK Multi Signer
04

ZK Scope

Permission with boundaries.ACCESS CONTROL

Set the contracts an account can call, the data it can send, and the value it can transfer. Prove a transaction fits those rules while keeping the full policy private.

Transaction policiesValue & calldata checks
Explore ZK Scope
Circuits, examples, and the reasoning behind them.Read the source

02 / Our approach

Every transaction
leaves a trace.
We question how much.

A smart account can expose who signed, how approvals work, and what an account is allowed to do. Much of that information only needs to be checked. We work on the cryptography that makes the distinction possible.

A CLOSER LOOK / THRESHOLD AUTHORIZATIONConceptual flow
01 / KEPT PRIVATE

The account’s
inner workings.

Signer identities
Individual signatures
02 / CHECKED ONCHAIN

The approval
is valid.

A proof confirms that the signing threshold was met for this transaction.

Threshold satisfied

What a proof reveals depends on its public inputs. Each circuit’s documentation sets out that boundary.

Inspect the circuit

03 / From circuit to account

Built to find
its way into your stack.

Noir circuits sit at the core. Verifier adapters and account integrations carry the proof into an onchain transaction.

WORKING WITHNoir.SafeNexusBarretenbergCIRCUITS / PROOFS / ACCOUNTS

The work is open.

Start with
a circuit.

The toolkit includes circuit definitions,
example inputs, and interactive demos.

Open the toolkit
github.com/MicrochainLabs/zk-smart-account-kit