← Back to Docs
DOCS / 01 / OVERVIEW

A permission is a
small contract promise.

A protocol defines one allowed action. A capability pass lets its holder trigger that action, while the Gatekeeper rejects everything outside the public rule.

PROTOCOL MAP

From a public rule to one bounded action.

The wallet handles the private note and proof. BlackBox’s contracts own the policy checks and permitted execution.

01 / ISSUER

Defines the job

Chooses the target, selector, cap, expiry, recipient, and reuse mode.

02 / POLICY

Stores public limits

The Gatekeeper records the exact boundaries that every use must satisfy.

03 / PRIVATE PASS

Moves to a holder

A one-unit STRK20 note represents authority to request that job.

04 / WALLET

Builds the proof

The holder wallet proves fresh pass delivery without giving BlackBox the note plaintext.

05 / GATEKEEPER

Enforces and forwards

Only a valid, in-policy request reaches the protected adapter or contract.

PUBLIC ONCHAIN

Policy limits, contract addresses, shielding or deposit address, token and amount, and the final target action remain public.

PRIVATE BOUNDARY

The private note and its ownership stay inside the privacy wallet. Sender separation also depends on the wallet’s relay path.

THREE RESPONSIBILITIES

Each part has one job.

01

Issuer

Defines the target, allowed action, cap, expiry, and whether the pass is reusable.

02

Holder wallet

Owns the private note, prepares proof-backed execution, and asks the holder to confirm.

03

Gatekeeper

Checks fresh delivery and the public policy before forwarding only the allowed call.

NEXTIntegrate a target →