Contact
Requests are evaluated based on the written brief. All requests should include a 2–4 page summary brief. If there is a fit, you will receive an engagement overview and a scope confirmation path.
Required: 2–4 page summary brief
Attach (or provide a secure link to) a 2–4 page summary brief. The brief should be written for an internal audience and should avoid marketing language.
- System context: what is being reviewed (architecture, protocol/ledger, payments/settlement)
- Decision pending: what decision you need to make and by when
- What is at risk: capital, regulatory exposure, operational risk, reputational risk
- Threat model: plausible adversaries and failure scenarios (internal and external)
- Assumptions: dependencies, trust assumptions, third parties, control boundaries
- Constraints: regulatory, operational, integration, timeline constraints
- Closure definition: what “done” looks like (e.g., memo suitable for GC/CRO/committee review)
- Confidentiality: whether an NDA is required before sharing materials
- Materials available: architecture diagrams, specs, threat models, prior audits, incident history (if any)
Requests that do not include the brief are typically not evaluated.