§ 01 — ORIGIN

Why we exist. A custody gap that everyone could see.

Three observations led to Fund Base Camp. None of them are new; they're just what happens when private-market activity moves faster than the infrastructure underneath it.

For decades, investors in private-market vehicles have relied on a soft form of trust: the sponsor says "we hold your subscription documents," and the investor accepts that statement, often forever, often without ever asking what would happen if it stopped being true. For institutional allocators, the soft form is supplemented by fund-administrator paperwork that takes days to retrieve and reads, when retrieved, exactly like the email the sponsor would have written anyway. Fund Base Camp was created to provide a public verification layer for custody records that investors can access directly.

The first observation was simple: investors in private-market SPVs do not have, and have never had, a way to verify their custody record on demand. Public-market investors take this for granted — a brokerage statement, a transfer-agent record, a blockchain explorer — but the private-market equivalent stops at "ask your fund admin and wait." The asymmetry has nothing to do with technology and everything to do with the absence of an entity whose only job is to make custody verifiable through an independent verification portal.

The second observation was about cost. Traditional fund administrators charge $25,000 to $75,000 per year per SPV, and their "custody" is a spreadsheet cell that says yes. Bringing one on for a single-asset $5–20M SPV destroys the unit economics. The sponsors we know skip the admin, the investors notice, and the trust gap propagates. Fund Base Camp addresses this through streamlined custody pricing and scalable verification infrastructure.

The third observation was that the missing piece — verifiable, cryptographically-anchored document custody — is a small enough operation that one focused entity could provide it across many SPVs at unit economics that work, provided that entity was independent of any one sponsor. The cryptography is free. The storage is cheap. The attestation and insurance are the cost basis, and they amortize across every record under custody. More technical details are available on our security and custody architecture page.

We did not invent any of the primitives here. We assembled them into something that didn't exist as a service, and gave it the legal entity and the insurance and the attestation that turn primitives into a credible custodian. FBC · founding note

So Fund Base Camp was set up as the missing piece. A separate legal entity, separate signers, separate bank accounts, separate insurance, separate operational discipline. Sponsors send us documents; we hash them, anchor them, and stand behind the cryptography with insurance and an annual independent attestation. Investors verify on demand at a public URL with no account through the Fund Base Camp verification system.

§ 02 — INDEPENDENCE

Operational separation. Disclosed, structured, covenanted.

FBC is under common ownership with Limen Markets Private. We disclose this in every PPM that references our custody, on every page of this website's footer, and to every prospect on the discovery call. The reason we can still be a credible custodian for Limen-sponsored SPVs is that operational independence is structured and enforceable — not just claimed. Additional disclosures are outlined in our legal and compliance documentation.

The independence covenant works at four layers:

  1. Legal entity. Fund Base Camp LLC has its own EIN, its own articles, its own operating agreement, its own registered agent.
  2. Authorized signers. At least one signer on FBC is not a signer on any Limen entity. That signer is required by covenant to consent to material custody actions.
  3. Banking and books. FBC maintains its own bank accounts and its own ledger. No commingling. Where shared services exist (e.g. shared software vendors), they are invoiced and paid at arm's length.
  4. IT environment. FBC's AWS account, its KMS keyrings, its CloudTrail logs, its identity provider — all separate from any Limen environment. Cross-account access is itself logged.

The covenant is reviewed quarterly by FBC's own counsel, disclosed in the Custody Services Agreement, and reaffirmed at each insurance renewal. The annual AUP includes a procedure to verify that the covenant continues to be in force as represented.

REQUIRED DISCLOSURE

The Limen Markets affiliation, stated plainly.

Fund Base Camp LLC is under common ownership with Limen Markets Private. Fund Base Camp operates as a separate legal entity with its own bank accounts, authorized signers, insurance, and operational infrastructure, and provides custody services to Limen Markets-sponsored SPVs and to other unaffiliated clients on arm's-length terms.

Investors and other users should evaluate this affiliation when considering the independence of Fund Base Camp's custody function. We believe the structural and operational separation described above is what makes the affiliation tolerable; some investors will reach a different conclusion, and we'd rather you know the structure upfront than be surprised later.

§ 03 — PRINCIPLES

Four things we won't compromise on. Even quietly.

Principles in this kind of business are easy to write and harder to keep. These are the four we orient around — they constrain product decisions, hiring decisions, and pricing decisions.

Principle 01

Trust is mathematical, not promised.

Every claim our verification page makes can be re-checked against a public artifact — the Bitcoin blockchain — by anyone with the proof file. We will not introduce primitives that require trusting us.

Principle 02

Disclosed beats opaque, always.

Insurance carriers, attestation firm, architecture, personnel controls — published openly at our security disclosures and architecture page. The Limen affiliation — disclosed in every PPM and in every page footer. We default to publishing.

Principle 03

Investors don't pay to verify their own records.

The verification endpoint is public, free, and forever. The receipt PDF is free. The API for verification is free. Investors should never be asked for credentials, payments, or accounts to confirm that what they were told to expect is in fact in custody through the public verification system.

Principle 04

Independence is structural, not aesthetic.

The independence covenant is real or it isn't. Separate signers, separate banking, separate IT — or none of it counts. We will refuse engagements that require us to commingle.

§ 04 — HORIZON

Where this goes. Honestly.

A custodian's credibility compounds — by SPV count, by attestation cadence, by the boring track record of every verification request returning the right answer. The roadmap below is what compounds the credibility further.

Year 01 · 2026

First sponsor live · first AUP

Onboard Limen Markets Series 2026-A as the first custody client. Engage CPA firm; publish first AUP report. Bind insurance lines. Ship verification endpoint, receipt PDF, dashboard, ingestion API, and sponsor onboarding tools described on the For Sponsors page.

Year 02 · 2027

First external sponsor · SOC 2 Type I

First unaffiliated sponsor live, materially strengthening the independence story. SOC 2 Type I issued. Webhooks, JS widget, RFC 3161 co-anchor available. Insurance limits scaled with AUM-under-custody. Future infrastructure support will expand through additional integration and automation capabilities.

Year 03 · 2028

SOC 2 Type II · institutional onramp

SOC 2 Type II issued; the AUP becomes complementary rather than primary for institutional audiences. Multi-sponsor scale; named contacts for Tier 03 platforms. Public proof-file mirror, in case anyone wants belt-and-suspenders.

DISCLAIMER   The roadmap above describes intent, not commitments. Insurance limits, attestation cadence, and feature rollouts are subject to operational and counsel review and may shift. Material changes are announced in our quarterly note and reflected within our security disclosures.