The documents that apply today.
The rules for running a fund on ETP Foundry, what we ask of the parties who sign, and how the service is run. Every document is versioned, and each new version starts with a short summary and what changed.
Read these as drafts. Every document here is a draft, and the policies are pending review by counsel. Methodology v1.1 governs: where any other document differs from it, the Methodology wins. No outside party holds a seat yet, and ETP Foundry is not authorised or registered anywhere.
Start here.
| Document | What it answers | Version |
|---|---|---|
| Methodology | How a fund’s daily NAV is calculated from existing price providers and signed on the ledger by the fund’s own parties, what happens when they do not agree, and how a mistake is corrected. Full text: methodology-v1.1.md | 1.1 · 19 Oct 2026 |
| How it works | The fund model in plain words: set up, create and redeem, value it every day. | Web page |
| Regulatory status | What ETP Foundry is not, and what a real fund needs before it launches. | Web page |
For the parties who sign.
Token issuers, administrators, lenders, custodians and others who hold a seat on a fund. Seats are free.
| Document | What it answers | Version |
|---|---|---|
| What we ask of each seat | In plain English, per seat: what you send, what stays private, and why it is not a rubber stamp. | 3 · 19 Oct 2026 |
| Committee terms of reference | Who may hold a seat on a fund’s committee, for how long, what they must do, and how they are removed. | 1.4 draft · 19 Oct 2026 |
| Rulebook | Who does what each day, and what happens when a value cannot be made. Process only, under the Methodology. | 0.3 draft · 19 Oct 2026 |
| Conflicts of interest | What stops ETP Foundry acting in its own interest, including the conflicts we cannot remove and disclose instead. | 0.3 draft · 19 Oct 2026 |
| Complaints, errors and corrections | How to complain, how changes are consulted on, and how an error is corrected. | 1.1 · 19 Oct 2026 |
How the service is run.
| Document | What it answers | Version |
|---|---|---|
| Security overview | How the service is hosted and protected, what is not in place yet, and how to report a vulnerability. | 0.2 · 19 Oct 2026 |
| Privacy notice | What personal information we hold, why, for how long, and your rights. | 0.2 draft · 19 Oct 2026 |
| Sub-processors | Which outside providers host or carry the service, and which of them receive personal data. | 0.2 draft · 19 Oct 2026 |
| AI use | What the assistant in the signed-in desk can and cannot do, and what is stored. | 0.2 draft · 19 Oct 2026 |
| Incident response | How incidents are classified and handled, and when you are told. | 0.2 draft · 19 Oct 2026 |
| Business continuity | What happens if a component fails, or if the person running ETP Foundry cannot continue. | 0.2 draft · 19 Oct 2026 |
Not written yet, listed so the gaps are visible: an independent oversight function (not set up), and an external audit of the code and of how the Methodology is followed (not done). A material change to the Methodology needs at least 30 days of public consultation and 30 days’ notice, and no change is ever retroactive (Methodology §9).