Name the job
For example: pay this vendor, run this maintenance call, or pause this contract.
PRIVATE ACCESS CONTROL ON STARKNET
Public rules.
Private operators.
Give someone a narrowly defined onchain permission without putting their operating wallet on your public role list.
Contract-enforcedPowered by STRK20Open source
PERMISSION / 001ACTIVE
B
VERIFIED JOBPay an approved vendor
- WHAT
- One payment
- MAXIMUM
- 0.01 STRK
- TO
- Policy-defined
- WHEN
- Before expiry
- RULES
- Public
- OPERATOR
- PRIVATE
IssuePassUseVerify
The permission is visible. The person using it need not be.
CHOOSE HOW TO START
One protocol. Three clear paths.
Go directly to the part of BlackBox that matches what you want to do.
FOR TREASURIES
Create a mandate
Set the recipient, budget, expiry, and private operator permission in one guided flow.
Open Studio ↗ FOR HOLDERSUse a permission
Connect your wallet to see and use the permission it holds.
View my capabilities ↗ FOR BUILDERSBuild with BlackBox
Read the protocol flow, integration guide, and security boundaries.
Open documentation ↗WHY BLACKBOX
Protocols need help. They do not need public operator maps.
Most onchain permissions reveal who can act and connect every action that person makes. BlackBox separates the rule from the wallet behind the rule.
- 01 Set one exact permission.
- 02 Give it to an operator as a private pass.
- 03 Let the contract enforce the rule.
SIMPLE BY DESIGN
Permission, not blind trust.
BlackBox is for protocols that want to delegate a small job without handing over a general-purpose key.
Set the boundaries
Choose the exact action, maximum amount, expiry, and whether it can happen once or repeatedly.
Let the contract decide
The Gatekeeper rejects actions outside those boundaries. A private pass does not become a master key.
BUILT FOR PROTOCOLS
Start with one useful job.
Private treasury operations are the flagship. Keepers, emergency response, and one-shot mandates use the same primitive.