Company
A firm that runs its own book, and sells the method
Diligentia deploys its own treasury across DeFi and licenses the risk method it uses to do it. We take no outside money and hold no third-party assets, and that is a permanent choice rather than a stage we are waiting to grow out of.
Everything on this site describes design and work in progress. Nothing is deployed, no capital is deployed, and no outside money is accepted.
How we work
Three habits that shape the code
The constraint is written before the code
The properties a vault must never violate are written as executable tests first, and the implementation is shaped to fit them. Written afterwards, a test suite only confirms whatever the code already does.
A success is only a success if the chain says so
Nothing is reported from what we asked for — every number comes from state read back afterwards. A transaction being accepted is not a fill; capital arriving is not a return.
The correction gets published too
When the rubric mis-scored lending markets, that went on the method page with the wrong number still in it. A method with no published corrections is a method nobody has checked — and we are asking people to buy this one.
Where we are
The build, without rounding up
Published because a pre-launch site with no status is asking you to guess, and people guess generously.
| Piece | State | Detail |
|---|---|---|
| Method and threat model | Built | The scoring rubric, the trust boundary, the invariants and the risk log |
| Whitelist and caps contract | Built | Exposure goes up slowly and comes down immediately, with 29 passing tests |
| Risk rubric | Built | Six dimensions, published weights, 18 tests pinning the direction of each |
| Invariant suite | Built | Eleven properties with the allocation key driven as an adversary over 16,384 fuzzed calls. It found a real defect in the vault and two mistakes in the properties themselves |
| Vault | Built | Built to fit those properties rather than the other way round: caps, liquidity buffer, and behaviour when a venue stops answering |
| Allocator | Built | Applies a whole reallocation or none of it, and holds the loss bound the vault cannot see — the vault limits one move, this limits the sequence |
| First venue adapter | Built | One adapter covers every ERC-4626 venue at once, tested against the live Gauntlet, Spark and Steakhouse USDC vaults on Base — including a real position accruing 4.36% over 30 simulated days |
| Allocation engine | In progress | The optimiser and the data layer behind it. The on-chain half now has a shape to submit against |
| Concentrated liquidity adapter | Next | A DEX range position is not an ERC-4626 balance — it has a price range, goes one-sided, and accrues fees that must be collected. A second adapter shape, not a variation on the first |
| External audit | Not started | Not booked. Nothing carries capital before it reports |
Still undecided
Open questions we have not answered yet
Four closed when the firm settled on running its own book — fee level, queued redemption, risk tiers and whether there is a token all existed only because of deposits. What is left is smaller, and different.
- Whether the vault can be upgraded at all. This moved in the opposite direction when the firm did. An immutable vault was the stronger promise to depositors; with only our own capital at stake, operational flexibility costs nobody else anything.
- Whether the timelock is needed at all. A delay protects people who need warning to leave, and there is nobody to warn. It may survive purely as self-discipline, which is a weaker reason but not a bad one.
- The shape of the software product. API, periodic report or dashboard — and whether the rubric is published openly with the data sold, or the reverse.
- How concentrated liquidity gets scored. A range position needs a risk treatment the current six dimensions do not cover, starting with impermanent loss.
Contact
Getting in touch
The most useful thing anyone can send us is a hole in the method — in the rubric, in the trust boundary, or in something on this site stated more confidently than we have earned.
The domain is registered and the mailboxes are not live yet. Rather than print an address that would bounce, this says so.
Addresses appear here the day they work.