Solutions / Capital Allocators
Onchain products on POY rails execute according to your fund mandate as code rather than side letters. Every action carries a proof you can hand straight to your LPs.
The problem
You can read the strategy, meet the team and model the drawdown. What you cannot do is know, on any given Tuesday, that the thing you diligenced is still the thing being run.
It describes what should happen. Nothing in the product refuses an action that contradicts it, so compliance rests on the operator choosing to comply.
Leverage taken between reports, a strategy that drifted, a position outside the agreed universe. You see all of it once it is history.
The obligation lands on your side of the table. You are answering for constraints you had no mechanism to enforce.
The gap you are carrying
From the wire onward, the mandate is a document somebody is meant to be following. You find out at quarter end, from the party you are checking.
Quarterly reporting
Four self-reported moments a year, each describing a period that has already closed.
Continuous proof
One verification per action, produced by the contract at the moment it executed rather than by the manager afterwards.
What POY enforces
Your mandate compiles into the circuit the onchain product runs. An action that violates it is not flagged for review. It does not settle.
Position limits, eligible assets, leverage ceilings and drawdown bounds are compiled into the program the vault must prove against.
What the proof settles is that the committed program produced the action. Whether the mandate is well drawn stays your judgement.
Every action carries a proof verified onchain at the moment it executed, so compliance is a property of the record rather than of a report.
Each proof points at a specific bytecode hash. Changing that hash takes a timelock and a depositor exit window, so nobody swaps the strategy quietly.
The record leaves as CSV, JSON or a packaged audit trail, in the shape your fund administrators and auditors already consume.
Every row carries its verification status and its committed hash, so whoever receives the file can re-check it instead of trusting it.
Who this is for
Funds of funds, treasuries, family offices and anyone deploying against a mandate they did not write and cannot unilaterally change.
How it works today
The mandate lives in a side letter and is enforced by relationship
Assurance arrives quarterly, from the party being assured
Reconciliation is manual, and bespoke to each manager
A breach is discovered after the capital has already moved
With POY
The mandate lives in the circuit and is enforced by the product
Assurance is per action, produced at the moment it executed
One export format, verifiable by anyone who receives it
An out-of-mandate action reverts instead of settling
Deploy onchain without inheriting a blow-up you had no way to see coming.