For agent platforms
Your agent negotiates, sources, and commits. The counterparty can't tell if it's real, what it may commit, or whether it will pay, so deals stall in credit desks and prepayment demands. A mandate makes the commitment verifiable in milliseconds.
For institutions
Your controls live in custody consoles, treasury policies, signer lists, and approval queues. A mandate compiles them into one key that execution cannot exceed, enforced before value moves.
Market shift
Both sides of every transaction are turning into software. The rules that govern them are still paperwork.
01
Procurement agents award POs. Negotiation bots close deals. Treasury automations move funds. Software now signs for real money.
02
Stablecoins, deposit tokens, and tokenized assets create 24/7 settlement legs. Funds, T-bills, receivables, and collateral move as digital records.
03
Every rail got faster. Nothing proves what the thing signing is allowed to do, or who pays if it overreached. That layer is the mandate.
Product
The mandate is compiled into authority that can authorize a transaction only when the institution's conditions hold. The sensitive logic stays private; approved parties receive control evidence.
INPUT
A transaction an institution, employee, or autonomous workflow wants to send.
BLISK MANDATE
fails → no valid instruction
OUTPUT
Bank rail, tokenized deposit network, custodian, CSD, transfer agent, smart contract, broker, or RWA venue.
BLISK does not replace the bank, custodian, CSD, transfer agent, or chain. It gives them a mandate boundary to consume.
The supplier or counterparty joins nothing. One signature check plus a read of a public registry. That's the whole integration.
Interactive constructor · Demo
Pick the rules, set their parameters, and compile. The result is a single cryptographic key that only authorizes instructions the mandate allows.
Each rule is a live control with parameters, not a checkbox.
// live mandate expression
mandate :=
access(agent_ops_01
∧ 2of3(treasury)
∧ compliance_officer)
∧ eligible(WL-EU-07)
∧ risk(venues, caps, tenor≤90d)
∧ liquidity(window, buffer)
∧ derisk(oracle → safe_mode)
5 rules set · monotone policy · ready to compile
Capabilities
01
Who may initiate, approve, delegate, revoke. Roles and quorums, native to the key.
02
Investor, beneficiary, account, instrument. Proven by attested credentials, not promises.
03
KYC, sanctions, jurisdiction, transfer rules. Signed screening results become signing conditions.
04
Exposure, tenor, venue, counterparty limits. An oracle attests the bound holds; the key requires it.
05
Settlement windows, buffers, cash availability. Time and treasury state enter as attested facts.
06
Haircuts, margin, concentration, substitution. Collateral state feeds in via oracle attestation.
07
On an attested breach, authority collapses to the safe branch. No meeting, no interaction.
08
Every signature carries proof a valid rule was satisfied. Show it to auditor, insurer, counterparty.
This is why BLISK is more than policy. It is the executable rulebook for institutional asset movement.
Landscape
Honest scope: BLISK raises bypass cost and shrinks the trusted surface. It is not trustless and does not replace MPC vendors, auditors, or SLAs.
Research foundation
The mandate layer is based on a construction authored by our team and published as a public cryptography preprint, with an open reference implementation.
Public research record