fund.factsheet
- Version
- 0.1.1
- Desk
A factsheet shows, for a vault an agent's filing links on chain 4663, figures read from the chain with their evidence: what the vault holds, the value of a share over time, its fee rates and its high-water mark, money in and out, the actions of its owner, and the largest fall from a peak. Figures only: no opinion, no grade, no ranking by return, no advice, and no depositor named. A factsheet changes no status: rulebook version 1 does not read it.
Changelog
| Version | Date | What changed |
|---|---|---|
0.1.0 | 2026-11-20 | First version: links signed by the identity's owner, shown on chain and checked again each day; a daily reading at a minute drawn at random for each vault; the sanity rule; the drawdown over complete readings; and the vault's events as daily totals. |
0.1.1 | 2026-11-20 | A factsheet sums its money in and out over the 20 newest days read, not 30, so that one reads at most 55 rows (docs/BUDGETS.md section 21). No vault was linked. |
Which vaults have a factsheet
Only a vault an agent links. The identity's owner signs the link as EIP-712 typed data
CharterFundLink { agentId, identityRegistry, vault, nonce, issuedAt, expiresAt }in the domain filings use:FACTA, version 1, chain 4663. It is sent toPOST /v1/.funds/ links The agent has a filing in force, and links at most 3 vaults. One agent links a vault at a time.
The link is shown on chain, at one block, on two endpoints run by different operators. The server reads the identity's owner and the vault's
owner(),factory(),asset()anddecimals()at the head on both, and their answers must agree. It accepts the link only when:- the identity's owner is the owner who signed the filing in force;
- the vault's owner is the identity's owner or a wallet of that filing;
- the vault answers
asset()anddecimals()as an ERC-4626 vault does.
The link is checked again at each daily reading, and ends when:
- the agent has no filing in force;
- its filing in force was signed by an owner other than the one who signed the link;
- or the vault's owner is neither the identity's owner nor a wallet of that filing.
The factsheet then says when the link ended and why, and the vault is read no more. A link that ended may be made again.
How the vault is read follows its factory:
- Sherwood's
SyndicateVault, when itsfactory()is Sherwood's factory0x619af1488f32b4797f6fada3c3a8de72a5b693e0, whose vault code is verified on the explorer; - ERC-4626 only, otherwise.
- Sherwood's
The daily reading
- Once a UTC day, at a minute drawn at random for each vault, between 00:00 and 20:00 UTC. A secret drawn at random each day gives each vault its own minute. It is kept in the reading job alone, so nobody, FACTA included, knows a vault's minute before it passes, and one vault's reading tells nothing of another's.
- One block, these calls:
- for every vault:
totalAssets(),totalSupply(),convertToAssetsof one whole share,owner(), the vault's own balance of its asset, and the asset'sdecimals(); - for a Sherwood vault, also:
activeStrategyAdapter(),highWaterPricePerShare(),managementFeeBps(),agentFeeBps(),paused(),depositsLocked()andredemptionsLocked().
- for every vault:
- A vault is a contract FACTA does not trust. Each call to it may use at most 5,000,000 gas, and its answer is capped in size.
- A call that fails, or whose answer does not decode exactly, is
not readwith why. It is never shown as a value, and never as zero. - A running strategy. Sherwood's strategies do not report a value, and the vault does not mark them. A reading taken while a strategy runs leaves out what the strategy holds, and it is marked "strategy running".
- The sanity rule. A share value that moved more than 50% since the previous reading, with no strategy running at either reading, is
not readfor that day, with the size of the move.
The largest fall from a peak
- The drawdown is the largest fall of the share value below its earlier peak, in basis points, over the 30 newest readings.
- It uses complete readings only: a share value read, with no strategy running. A reading taken while a strategy ran is left out, since the vault's value leaves out what the strategy holds.
- Below 3 complete readings, no drawdown is computed, and the factsheet says so.
Money in and out, and the owner's actions
- Read once a day by the batch lane, from the explorer: every log of the vault in each whole UTC day, from the day of its first link.
- What a day keeps:
DepositandWithdraw: how many, and their totals in the asset's units;- the number of distinct depositors, and never an address of one;
- each new high-water mark, change of owner, code upgrade, pause and unpause, with its transaction and block.
- A day is stored once, and only when it is over. A day the chain or the explorer cannot read is read again on the next run.
- A factsheet sums the 20 newest days read. The owner's actions it lists are those of the same days.
What is not read, and why
- The fees taken at each settlement. Sherwood's governor records them. Its code (
0xa81dee59d865aebddea3472f508627c864cead5f, behind a beacon) has no verified source on the explorer, so its records are not read. The fee rates and the high-water mark are read from the vault, whose source is verified. - What a running strategy holds, for the reason above.
- For a vault read as ERC-4626 only: strategies, fee rates and the high-water mark. No verified source of its protocol was found.
Thresholds
The method's thresholds are its constants: FUND_LIMITS in packages/contracts/src/fund.ts.
| Threshold | Value |
|---|---|
Vaults one agent may link | 3 |
A share value's move, with no strategy running, above which it is not read | 50% |
Readings a factsheet shows, and the drawdown reads | 30 |
Days of events a factsheet sums its money in and out over, the newest read | 20 |
Complete readings a drawdown needs | 3 |
Gas each call to a vault may use | 5,000,000 |
Readings a vault gets | 1 a UTC day, at a minute drawn at random from 00:00 to 20:00 UTC |
Terms and evidence
- A factsheet outputs no term from the fixed vocabulary: it shows figures, and
not readwhere a figure could not be read. - Each reading carries its block and its time. Each event carries its transaction and its block. The link carries its signature and the block at which it was shown on chain.
Recomputation
Every figure can be repeated by anyone with an endpoint of chain 4663:
- a reading: the same calls at the reading's block;
- a day's events: the vault's logs over that day's blocks, decoded as the ERC-4626 and Sherwood events they are.
No script is published for this version.
Known ways to game it
- A gift to the vault. Anyone can send the asset straight to the vault, which raises the share value without a deposit. A jump of more than 50% with no strategy running is left out for that day. A smaller one shows as it is, and the money-in figures show no matching deposit.
- Timing a strategy around the reading. The minute is secret until it passes, and a reading taken while a strategy runs is marked and left out of the drawdown.
- New code. The vault's owner can upgrade its code. Each upgrade shows among the owner's actions, with its transaction.
- A vault that changes hands. Its new owner is not the agent's. The link ends at the next reading, and the factsheet says so.
- A protocol's own error. The figures are what the vault reports at the block. A fault in the vault's code is not detected.
Limits
- Chain 4663 only. Version 1 reads Sherwood vaults and plain ERC-4626 vaults.
- Factsheets write no notice in this version: a link's end is shown on the factsheet and in its API.
- A factsheet is not advice, not a rating, and not an offer of, or an invitation to buy, any share in a fund.
What exists elsewhere
Sherwood publishes its own funds' results, recorded by its governor. A factsheet adds what FACTA adds everywhere: an independent reading, the evidence behind every figure, and one method across protocols.