Bursar

Private, on-chain budgets for AI agents. Built for tokenized assets and agent commerce.

[Bursar @UseBursar]

Bursar is an on-chain control layer for agent spending. @robinhoodapp

Principals set private budgets, counterparties and payment rules. Each transaction is checked against its mandate at settlement.

Stealth wallets and ZK proofs protect details while providers verify auth.

[Bursar @UseBursar]

Bursar gives AI agents spending mandates not unrestricted wallets.

Budgets are enforced on-chain, funded by tokenized treasuries, and restricted by spend class, counterparty and RWA rules.

ZK proofs and stealth wallets keep mandates private while providers verify compliance.

[Bursar @UseBursar]

The Bursar test plan is built around failures that should be boring

The fourth spend over a cap fails. A stale RWA price defers.

After hours stress liquidates only the needed slice. An observer cannot link principal to agent.

That is a protocol property, not a demo promise.

[Bursar @UseBursar]

A collateral vault needs more than a token balance to describe its condition.

Bursar records the vault reference, raw assets and health in basis points.

That gives the health worker a concrete state to monitor instead of relying on a front end interpretation.

[Bursar @UseBursar]

The private part of an RWA purchase does not end when the order fills.

Bursar settles the eligible asset through the router, then shields the resulting position in the agent vault.

The mandate controls the purchase without turning the completed holding into a public signal.

Soon on @RobinhoodApp

[Bursar @UseBursar]

A dispute worker should not make a decision from one incomplete event.

Bursar replays the escrow and dispute history before the bonded resolver quorum acts.

The decision is based on the recorded sequence of the agreement, not whichever update arrived last.

[Bursar @UseBursar]

Hard to judge a protocol before the market around it is fully here, butursar is focused on one specific layer; private spending mandates for agents, with defined rules checked before payments settle.

[CoinGecko @coingecko]

Undervalued protocol?

[Bursar @UseBursar]

@Bybit_Official Gm

[Bursar @UseBursar]

Deposit. Check health. Withdraw.

Bursar collateral router keeps those actions tied to the same vault state.

Eligible stock and treasury tokens enter with their asset data, health is updated against debt, and withdrawals cannot ignore the position current condition.

[Bursar @UseBursar]

One principal can operate several agents without giving every wallet a public connection back to the same source.

Bursar StealthAgentFactory provisions agent wallets from a hidden principal reference, keeping the relationship private while the mandate still controls what each wallet can do.

Built on @RobinhoodApp

[Bursar @UseBursar]

A mandate can sit idle for hours or days before an agent needs to spend.

Bursar park manager watches NAV and schedules the required unpark instead of leaving the full balance exposed.

Treasury funding remains productive until settlement calls for it.

[Bursar @UseBursar]

Bursar database is not meant to become a second ledger.

It stores mandate commitments, receipt hashes, state changes and references to private values.

Plaintext mandate terms, spend records and principal agent links are kept out of the server side data model.

[Bursar @UseBursar]

The contracts enforce the rules. Someone still needs a clean way to write, amend, revoke and inspect a mandate.

Bursar separates that workflow from the contracts and carries each action as a signed message.

Usability sits above the authority layer.

Soon on @RobinhoodApp

[Bursar @UseBursar]

Proof verification is expensive enough to treat as infrastructure, not a throwaway request.

Bursar facilitator caches verified results for repeat checks while settlement still follows the mandate path.

It avoids identical work without making the cache the authority.

[Bursar @UseBursar]

Private by default does not mean every dispute becomes impossible to inspect.

Bursar DisclosureRegistry can grant a resolver a scoped slice of information for a specific case.

The mandate stays private outside that decision.

[Bursar @UseBursar]

A provider does not always need to know which agent is acting.

It may only need to know that the agent belongs to an approved set.

Bursar membership proof verifies that group membership without exposing the agent full identity or private history.

Built on @RobinhoodApp

[Bursar @UseBursar]

Allowing a provider is only half of counterparty control. A mandate may also exclude an address or set of addresses.

Bursar supports a blacklist root beside the allowlist.

The proof checks both before settlement, so a forbidden counterparty cannot pass through.

[Bursar @UseBursar]

A payment system should not depend on one worker remembering what happened last.

Bursar keeps replayable trust events beside settlement receipts.

After a restart, the service can rebuild holds, settlements and reputation from recorded events instead of guessing from balances.

[Bursar @UseBursar]

The control plane can carry a mandate update. It cannot authorise one by itself.

Bursar write, amend and revoke actions arrive as signed messages from the principal.

The service handles the request, while authority stays with the signer.

[Bursar @UseBursar]

A mandate does not store every approved address as loose text.

Bursar commits the counterparty and RWA permissions as roots.

The proof checks membership against those roots, so a payment can be validated without publishing the full allowlist.

Soon on @RobinhoodApp

[Bursar @UseBursar]

Prefunded and collateralized spending are separate by design.

In Bursar, debt can exist only inside the collateralized lane.

A normal prefunded mandate cannot quietly turn into credit because an agent asks to spend more than it has.

[Bursar @UseBursar]

One rule in the Bursar spec is easy to miss and important to keep.

Exit is never gated.

Funds can be screened on entry, mandates can stay private and solvency can be proven publicly, but leaving the system does not depend on an operator approving the withdrawal.