About Meridian

A small team building the settlement layer institutional treasuries already operate as if they had.

Meridian was started in late 2024 by a group of engineers and treasury operators tired of reconciling fiat ledgers against on-chain holdings by spreadsheet. The thesis is simple: the unit of work for an institutional treasury is the policy, not the transaction. The protocol is the technology to make that real.

01 — Principles What the protocol is governed by
01

Custody is not negotiable.

Meridian holds no principal. Ever. There is no hot wallet, no rehypothecation, no spread. If a feature would require us to take custody for an instant, we don't ship the feature. Architectural constraints are easier to govern than operational ones.

02

Determinism over cleverness.

Treasury policies are deterministic functions, not agents that "decide." An auditor reading the source can reconstruct what the system will do. The on-chain audit trail confirms what it did. Anything implicit is a bug.

03

Audit reports get published in full.

Including findings the protocol team disagrees with. Including findings that look bad. Selective publication is a tell, and our buyers can read the tell.

04

The boring institutional version is the version.

We design for the CFO who has to defend the integration in front of a board, not for the demo. If a feature looks impressive but is hard to explain to an auditor in one sentence, it gets cut.

05

Token holders govern the parts that should be community-owned.

Rule templates, fee curves, ecosystem grants. Not client funds, not executed transactions, not audit publishing. Governance is intentionally narrow, by charter, and the security council holds a veto on safety pauses only.

02 — Team Founders & senior staff

Built by people who've shipped financial software in production.

The founding team has prior experience at fintech and crypto-native infrastructure companies. We hire engineers who have worked under regulatory review and compliance officers who have written code. The blend is the point.

M. Aoyama
CO-FOUNDER · CEO

Previously built treasury automation at a global market maker. Wrote the first internal version of what became Meridian's policy verifier in a weekend in 2023.

L. Petrov
CO-FOUNDER · CTO

Smart-contract engineer. Author of three TON Improvement Proposals. Long history with deterministic rule engines and state-machine verification.

A. Chambers
HEAD OF SECURITY

Former lead reviewer at a top-tier audit firm. Founded the response team that has handled vulnerability disclosures across nine listed crypto-native protocols.

P. Okafor
HEAD OF FINANCE & COMPLIANCE

CPA, CISA. Spent eight years between Big 4 audit and stablecoin issuer compliance. Drives the SOC 2, ISO 27001, and jurisdictional posture.

S. Aalto
HEAD OF SOLUTIONS ENGINEERING

Former staff engineer at a crypto custody firm. Pairs with every design partner during the first 90 days to get the first policy into production.

R. Castellano
GENERAL COUNSEL

Cross-jurisdictional fintech and crypto practice — Cayman, Delaware, Singapore, EU. Drafted the Meridian token paper and the safe-harbor policy.

Detailed bios, prior work, and conflicts of interest are published in the Meridian information memorandum delivered under NDA. Meridian is hiring across engineering, security, solutions, and operations — see careers.

03 — Backers Strategic capital · independent governance

Meridian is backed by a small set of strategic investors aligned with the protocol's long-term posture. No investor holds operational control; no investor's allocation overlaps with the security council. All investor allocations are subject to a 4-year linear vest with a 12-month cliff, published on-chain.

Long-term capital Crypto-native treasuries Fintech operators Independent angels

Specific firm names are disclosed under NDA on request, in line with the preferences of the investors themselves. The full cap table including UBO disclosure is delivered alongside the security packet.

04 — Operating entities Jurisdictional structure

Want the long version?
Read the technical brief.

Architecture, settlement guarantees, threat model, economics, and the roadmap, in one document.