> ## Documentation Index > Fetch the complete documentation index at: https://docs.inkwell.finance/llms.txt > Use this file to discover all available pages before exploring further. # Market objections > Timing vs. Arcium/Umbra, TAM, positioning risk, kill criteria. Why we believe this still works. > **CONFIDENTIAL & PROPRIETARY © 2026 Inkwell Finance, Inc. All Rights Reserved.** > > This document is for informational purposes only and does not constitute legal, tax, or investment advice, nor an offer to sell or a solicitation to buy any security or other financial instrument. Any examples, structures, or flows described here are design intent only and may change. **Pre-alpha vs production.** Pages that describe "the operator holds the session-to-ephemeral-key mapping" describe today's single-operator implementation. Production Dagon will distribute this custody across an [Ika 2PC-MPC dWallet network](https://ika.xyz) — no single "operator" entity will hold the mapping, and no unilateral disclosure (lawful or otherwise) will be possible without the network agreeing. The two-party composition described here is strengthened, not weakened, by the migration. See [Design Philosophy](/inkwell/design-philosophy) for the full decentralization roadmap. ## "Arcium / Umbra shipped first. Timing moat is gone." Acknowledged. Arcium launched Solana mainnet-alpha in Feb 2026. Umbra built a live dark pool on top with \$155M raised. Dagon's bet is that **mechanism moat outlasts timing moat** in institutional flow venues. Specifically: * **Uniform clearing price per batch** (Dagon) vs. per-order pricing (Arcium CLOB model). Institutional MMs quoting curves prefer uniform; retail price-takers don't notice the difference. * **Two-party composition for compliance** (Dagon) vs. per-application identity (Arcium substrate). Matters for counsel-backed institutional adoption; doesn't matter for retail. If the market wants a crypto dark pool today, Arcium wins. If the market wants a curve-based institutional venue with coordinated- disclosure compliance, Dagon is the only one building it. Kill criterion KC-1: if no market-maker design-partner LOI by 2026-06-16, pivot. ## "TAM is small. Crypto OTC is what, \$2B/day?" Wintermute alone does \~\$2.24B/day in OTC. Total crypto OTC is materially larger, as is cross-venue block flow that currently runs over Telegram RFQ. Dagon's addressable slice is: * **Block-size crypto flow** — 7-fig+ tickets looking for venue quality. * **Cross-venue arbitrage** — MMs wanting to quote without leaking curves to competitors. * **Institutional onboarding** — crypto-native funds whose compliance model now requires selective-disclosure receipts. Total addressable: order of \$100B+/month if fully captured. Realistic initial capture: sub-1% of that at launch, scaling with product maturity and MM onboarding. ## "No design-partner MMs signed yet." Correct. Kill criterion KC-1 names a specific deadline (2026-06-16) for first MM LOI. Outreach is active with Wintermute, B2C2, Galaxy, Cumberland, GSR. No signed LOI as of this writing. A pre-alpha venue is hard to sign before the product demonstrably works. We accept the chicken-and-egg; we're building the demo product that makes the signing decision easy. ## "Why would an institutional MM share its curve parameters with your operator?" They don't, in plaintext. The curve submission is encrypted before it reaches the operator. The operator processes ciphertexts and settles against an aggregate. The MM's curve is known only to the MM and the FHE circuit. The adoption question isn't "will they trust us with their curves" — it's "will they trust the FHE primitive to not leak their curves via side channels." That is a question answered by audits, formal verification of the matching circuit, and observable behavior over time. We do not ask anyone to take it on faith. ## "Pre-alpha to mainnet is a long road." Correct. Our dependency chain: Encrypt REFHE shipping → Dagon mainnet contract audit → MM design-partner integration → production launch. Realistic timeline: * Encrypt REFHE production: mid-to-late 2026 (Encrypt's own target). * Dagon mainnet audit + MM integration: 3–6 months after that. * Production launch: Q1–Q2 2027 if everything slots. If Encrypt REFHE slips past end-of-2026, Dagon stack pivots to gMPC (kill criterion KC-2). Pivot cost is material but not terminal. ## "Compliance angle in a crypto-native product kills the vibe." Fair positioning concern. Pure-crypto audiences read "two-party compelled process" as selling out. TradFi audiences read "decentralized non-custodial FHE" as unserious. Our positioning is that the two-party composition is stronger privacy than the crypto-native default (operator-held keys), and more compliant than a mixer. It is the middle, and the middle is where institutional crypto lives. See: [What Dagon is not](/dagon/what-dagon-is-not). ## "Why will institutions trust a pre-alpha protocol with real size?" They won't, until it is proven. Phase 1 is proving the mechanism works with small notional at low risk. Phase 2 is MM onboarding with tracked execution-quality benchmarks. Phase 3 is institutional onboarding after benchmarks are durable. Trying to skip phases is how pre-alpha venues die. We are not skipping phases. ## Kill criteria (public) * **KC-1 (2026-06-16):** First MM design-partner LOI required, or rethink go-to-market. * **KC-2 (2026-12-31):** Encrypt REFHE mainnet required, or pivot substrate (gMPC). * **KC-3 (6-month window):** If Arcium ships symmetric Walrasian clearing over encrypted schedules, mechanism moat compromised. * **KC-4 (3 months post-pilot):** If first pilot MM volume \< \$10M/q, re-test thesis. ## Further reading * [Is there a minimum trade size?](/dagon/faq/minimum-size) * [Decentralized or not?](/dagon/faq/decentralized-or-not)