Treasury the fund owns outright, working every hour.
Float, reserves and yield, allocated by rules the fund sets and can read — never leaving their keys.
A fund's cash usually sits idle outside banking hours, and its yield lives in an account someone else controls. Here the money stays under the fund's own keys, and simple rules — how much to keep liquid, how much to put to work — are enforced by code that runs around the clock. Every move is visible on-chain.
Reserves sat idle off-hours, and yield strategies lived in a managed account the team couldn't fully control or audit.
- 01Policy-driven allocation across operating, reserve and yield
- 02 — every action against keys the fund holds
- 03Isolated, opt-in yield with a full on-chain trail
Float is now allocated by rules the fund sets and can read, settling any hour, with nothing custody-critical leaving their environment.
The architecture, end to end.
Each box is a primitive we wrote and you own — legible all the way down, no black-box vendor in the path. Value flows left to right.
Operating, reserve and yield balances, all under keys the fund holds.
Limits, thresholds and sweeps you set, enforced in code, not by a desk.
Float moves between buckets automatically, any hour, within your limits.
Every sweep and rebalance is auditable from the chain itself.
- On-chain where enforcement matters; in your infrastructure where operation matters.
- Non-custodial by default — keys and funds stay with their owner.
- Audited line by line, then handed over: repository, runbook, and proofs.
The shape of the change.
One figure, measured honestly. The rest of the gains are in the table below.
- Operating 25%
- Reserve 35%
- Yield 40%
Legacy vs the system we built.
| The legacy way | With Govart | |
|---|---|---|
| Availability | Banking hours | 24/7 |
| Custody | Managed account holds funds | The fund holds the keys |
| Allocation | Manual, desk-dependent | Programmatic, rule-based |
| Audit | Statements after the fact | Live on-chain trail |
Primitives, not black boxes.
Each layer is code you own and can read — written in-house, audited, and handed over. No rented dependency in the path of your money.
Policy engine
Limits, thresholds and sweeps enforced in code, not by a trading desk.
Non-custodial vault
Every allocation signs against keys the fund holds — nothing leaves.
Yield adapters
Isolated, opt-in strategies, each capped, each with a full on-chain trail.
Built as if it’ll be attacked.
In crypto, one mistake is terminal. We threat-model before we build — here’s what could go wrong, and what stops it.
A vendor freezes or loses access to the funds.
Non-custodial — the keys never leave the fund's environment.
An allocation drifts outside the mandate.
Hard limits in the policy engine reject the move on-chain.
A yield strategy goes bad and bleeds reserves.
Strategies are isolated and capped; reserves stay ring-fenced.
Yours at the end. All of it.
The engagement ends — that’s the point. What stays is everything you need to run and extend the system without us.
The repository
Every contract and service, commented and documented — nothing withheld, no black box.
Audit reports
Internal review plus an independent third-party audit, your engineers reading along.
The runbook
How to operate, monitor, upgrade and recover — written for your team, not ours.
Keys & training
Full control transferred, and your engineers walked through it until it's theirs.
“The treasury answers to our rules, not a vendor's hours.”
Have something like this to build?
Disclaimer
Govart provides software engineering, technical advisory, and infrastructure services only. We advise on technology — not on financial, investment, legal, tax, or accounting matters. Nothing on this site is advice, an offer, a solicitation, or a recommendation.
We are not a bank, broker, custodian, exchange, payment processor, money-services business, or virtual-asset service provider, and we never hold, transmit, or take custody of client or end-user funds.
KYC, AML, sanctions screening, licensing, and regulatory compliance remain the responsibility of the operator that owns and runs each deployed system. We build the controls you specify; we do not act as your compliance function. Figures and examples shown are illustrative only.