Author: Alexandre Kotcherguine, Vision Officer & Investor
Contributors: Georgi Gitchev, Governance Officer & Organisation Domain Lead; Matt Jackson, Growth Officer
This is Article 5 of Phase 1 of the Polity thought-leadership series on go-to-market, capital, and valuation for Web3 infrastructure. The four preceding articles built the framework – activation graph (Article 1), activation strategy and MVNS (Article 2), substitution curve (Article 3), and capital derivation chain (Article 4). This article walks the framework end-to-end on one explicitly hypothetical operator example: a European tokenisation operator launching across two MiCA jurisdictions. The example is didactic, not predictive; the operator is composite, not real; the numbers are illustrative, not calibrated to any specific entity. The purpose is to make the framework observable as a single coherent derivation rather than as five disconnected articles.
|
TL;DR. A hypothetical European tokenisation operator (Operator E) is walked end-to-end through the framework: activation graph drawn with R_DE and R_NL as first-class nodes, supply-side-first bootstrapping loop selected against the structural decision rule, per-class substitution curves designed, and capital derivation chain run to a round size of $11m–$14m with a ramp–plateau–descent burn profile across a 30-month runway. The R_j line is approximately 18–22 per cent of the central-case round. Numbers are illustrative for didactic purposes; the derivation chain is the contribution. |
|
Notice on the worked example. Operator E is a composite hypothetical operator. Its profile (European tokenisation, MiCA jurisdictions, supply-side-first activation) is constructed to illustrate the framework rather than to describe any specific entity, current or planned. The numbers in this article are illustrative and chosen to make the derivation legible – they should not be taken as Polity’s estimate of the cost or capital structure of any real operator. Readers applying the framework to a specific case should substitute their own calibrated inputs; the derivation chain is the contribution, not the specific anchor values. |
|
Hypothetical example. Operator E is a composite hypothetical operator constructed for didactic purposes. It does not describe, and is not intended to describe, any current or planned Polity operator-customer or any other identifiable real-world entity. Numbers, jurisdictions, and structural choices are illustrative; nothing in this article should be read as a recommendation, projection, or solicitation in respect of any real entity. |
Operator E is a hypothetical European tokenisation operator preparing to launch a regulated digital-finance infrastructure network. The operator’s thesis is that mid-market European corporate issuers want to issue tokenised debt and equity instruments, intermediated through regulated providers, distributed to qualified institutional investors and high-net-worth retail clients across multiple EU jurisdictions. Depending on the precise instrument structure, Operator E’s in-scope activities may fall under Regulation (EU) 2023/1114 (MiCA), MiFID II / MiFIR, the Prospectus Regulation, the DLT Pilot Regime (Regulation (EU) 2022/858), or some combination thereof – the worked example treats the regulatory-permission node R_j as a generic stand-in for whichever regime governs the Operator’s specific activities, and the licensing horizons used here are illustrative for a multi-regime regulated-finance launch rather than calibrated to any one regime.
Substrate. Operator E licenses substrate of the kind described in Article 1 §1.2 – multi-sided MSP-aware, with per-class participant identity, compliance posture as protocol-observable state, and per-class telemetry – and treats the substrate licence cost as a fixed line in the capital plan. The worked example uses Polity substrate as the assumed input, in line with the corpus’s vendor identity and as disclosed in the Article 4 §4.1 vendor-side practitioner anchors. The framework is designed to be substrate-agnostic; an operator selecting an alternative substrate would adjust the line-item accordingly without otherwise changing the derivation.
Target jurisdictions for the launch surface. Germany (BaFin) and the Netherlands (DNB / AFM). Both are MiCA-passportable for in-scope crypto-asset services, but the Operator’s view (on the legal advice it has commissioned from counsel in each jurisdiction) is that passporting alone is insufficient cover for the activities it intends to operate, which span both MiCA and securities-services regimes. Each jurisdiction’s licence is therefore activated independently, on its own timeline.
Target participant classes at MVNS. One Operator (Operator E itself, operating the network across both jurisdictions); nine to fourteen Providers across the two jurisdictions (regulated investment firms, custodians, paying agents); fourteen to twenty-one Merchants (corporate issuers and structured-product originators); thirteen to twenty-five thousand active Clients (qualified institutional and high-net-worth retail). Capital Contributors sit alongside the activation chain and are not in the participant-count vector. The vector is carried as a range because MVNS estimation is a research problem the framework opens rather than solves (Article 2 §2.2); the range width is itself the framework’s honest disclosure of estimation uncertainty.
Activation horizon. 28 to 34 months from round close to declared MVNS, set by the binding constraint (R_j activation cycles in BaFin and DNB / AFM, illustratively at 14 to 18 months and 18 to 22 months respectively, partly overlapping; the actual cycle for any specific operator and any specific licence will depend on the regime, the activity, and the supervisor’s case-load).
The activation graph for Operator E is drawn explicitly per Article 1 §1.3, with regulatory-permission nodes for both target jurisdictions:
Schematic 6 – Operator E activation graph: Operator_DE and Operator_NL as roots; R_DE and R_NL as first-class graph nodes upstream of the regulated supply-side classes in their respective jurisdictions; Providers and Merchants per jurisdiction as supply-side; Clients downstream; Capital Contributors off-graph.
Three features of the graph are worth noting before activation strategy.
R_DE and R_NL are jurisdiction-additive. The two regulatory nodes are independent: BaFin licensing in Germany does not credit DNB / AFM clearance in the Netherlands, and vice versa. Each carries its own activation cost and its own multi-month cycle (R_DE 14–18 months, R_NL 18–22 months – see §5.1). Neither passporting nor an MoU between supervisors changes this for the activities Operator E intends to operate.
Providers depend on R_j locally. A Provider is meaningfully present in jurisdiction j only when R_j is active. This pushes Provider activation behind R_j on the timeline, which in turn pushes Merchant and Client activation behind both. The graph implies that activation cannot run in true parallel across the two jurisdictions; one will lead, and the second will follow.
The DAG is shallow but the timeline is long. The forward-edge subgraph is four edges deep (R_j → Provider → Merchant → Client), but each edge carries a real activation cycle. The cumulative time-to-MVNS is the binding output of the graph, not the depth.
Per Article 2 §2.3, three bootstrapping-loop archetypes are available. Each is evaluated against Operator E’s graph and constraint set, and only one is structurally appropriate.
Operator E selects supply-side-first activation. The reasoning, in the form Article 2’s decision rule specifies:
The hard side is overwhelming. The regulated supply side (Providers, Merchants) carries the highest unit cost of acquisition (mid-five-digit to low-six-digit dollars per Provider; low-five-digit to mid-five-digit per Merchant), the longest activation cycle (six to twelve months per Provider including legal, integration, and custody clearance), and the highest structural retention. Activating Clients before this side is at MVNS produces a churn event the operator cannot recover cheaply.
There is no single-player tool. Operator E does not have a usable utility for end Clients in the absence of regulated Providers and Merchants. The demand-first loop is structurally unavailable; the operator has no surface to activate Clients against.
The graph is not saturable in parallel. Both R_DE and R_NL must activate before regulated supply can onboard at all in either jurisdiction; until R_DE clears, the German subgraph is inactive regardless of how many Providers have signed memoranda. The simultaneous loop is therefore not a serious option for the launch surface – there is no narrow surface across the two jurisdictions in which all sides can be activated together.
Demand-first is rejected because it produces, in this category, the cohort’s most expensive failure mode: mass user acquisition in advance of regulated supply, followed by churn when the regulated supply has not arrived. The framework’s Hypothesis 1 (Article 4 §4.6b) is that a regulated-finance operator activating demand before supply reaches MVNS will, within 18 to 24 months, decay weekly-active participants by ≥ 70 per cent from peak or raise a bridge round at flat or down valuation. Operator E does not stake against that hypothesis.
Simultaneous is rejected because saturating both jurisdictions in parallel during the R_j activation window means paying parallel subsidies to supply-side participants (Providers, Merchants) for 18 to 24 months in each jurisdiction with the regulated supply unable to transact. The capital cost of this is large and the activation gain is zero – the constraint binds at R_j, not at supply-side onboarding velocity.
The decision is therefore: supply-side-first, jurisdiction-sequential, with R_DE leading R_NL by approximately six to nine months on the activation calendar.
|
Activation Sequence Summary. Months 0–6: Substrate customisation; R_DE and R_NL programmes initiated in parallel; Provider pipeline development; no participant onboarding. Months 6–14: R_DE activation cycle in flight (target: live at month 14–18); first three Providers in legal and integration in DE; substrate live in test mode. Months 14–22: R_DE live; first three Providers go live; first four Merchants onboard in DE; R_NL approaching live (target: month 18–22); first qualified-institutional Clients onboarded in DE. Months 22–28: R_NL live; supply-side onboarding compresses in NL on the integration patterns established in DE; Provider count crosses MVNS in DE and approaches MVNS in NL; Merchant and Client classes begin to ramp. Months 28–34: All supply-side classes (Provider and Merchant in both DE and NL) reach MVNS thresholds; Client class crosses substitution curve last (per the Article 3 illustrative ordering); network at declared MVNS by month 28–34, after the 90-day stability period. |
Per Article 3 §3.1, the substitution curve is per class. For Operator E, three classes carry meaningful incentive budgets – Providers, Merchants, and Clients – and each has its own curve. Operators are not on a substitution curve in the framework’s sense (they are remunerated by network economics and the Operator’s commercial relationship, not by tapering subsidies).
Provider class. Incentive: integration grants and 12-month fee rebates, totalling approximately $300k per Provider. Decay: step-down at month 12 of the Provider relationship (50 per cent reduction), step-down to zero at month 18. Utility: post-go-live, regulated transaction flow to Provider’s book of business. Crossover target: month 14 to 18 of network time (early; the Provider class is structurally retained by the regulated transaction flow and by the cost of switching off the platform once integrated).
Merchant class. Incentive: listing-fee rebates and per-issuance subsidies of approximately $80k per Merchant for the first 24 months of the Merchant relationship. Decay: continuous exponential, half-life 8 months. Utility: post-onboarding, distribution to qualified institutional investors and HNW retail across the two jurisdictions. Crossover target: month 22 to 28 of network time (mid; the Merchant class crosses once the Client base is sufficient to justify the issuance).
Client class. Incentive: onboarding bonuses and reduced execution fees, totalling approximately $35 per Client at MVNS scale. Decay: continuous exponential, half-life 4 months. Utility: post-supply-side-MVNS, access to a settled supply of Provider-intermediated, Merchant-issued instruments across both jurisdictions. Crossover target: month 28 to 34 of network time (late; the Client class crosses last, gated on full supply-side MVNS).
Schematic 7 – Operator E per-class substitution curves (illustrative): Provider crosses earliest (~month 14–18), Merchant mid (~month 22–28), Client last (~month 28–34). Network MVNS gated by latest-crossing class.
The latest-crossing class (Client) sets the network-MVNS time. The Article 4 capital derivation must therefore carry a maintenance-incentive tail through approximately month 30 to 34, even though the Provider class has crossed by month 14–18. This is the substantive reason the post-MVNS maintenance tail (Article 4 §4.1 Step 3) is not a small line for Operator E.
Stability commitment. Per Article 2 §2.2, MVNS requires not just per-class threshold attainment but stability under subsidy withdrawal. Operator E carries a 90-day stability period after the Client class crosses, during which the Client incentive is withdrawn and per-class participation is monitored. The 28–34 month declared-MVNS horizon used in the capital plan is the all-in figure (network-time crossing of the latest class, plus the 90-day stability period, plus a 6-month execution buffer for realised slippage on any of the upstream cycles).
Per Article 4 §4.1, the derivation runs in five steps. Each step is shown explicitly so that the round size is observable as an output rather than a premise.
Using the §4.1 vendor-side practitioner CAC anchors at their lower-anchor variant (the framework offers a range; this worked example takes the lower-anchor variant for a smaller-treasury operator and notes the upper-anchor parenthetically), applied against E’s MVNS vector at the lower bound (range carried at upper bound parenthetically):
Step 1 subtotal (direct acquisition): $0.5m–$0.8m. As Article 4 §4.2 anticipates, direct CAC is not the dominant input.
Step 2 subtotal: $3.5m–$4.5m, of which the R_j component (R_DE + R_NL) is $2.0m–$3.0m, comfortably the dominant infrastructure line and one of the dominant lines overall.
Step 3 subtotal: $3.75m–$6.0m. The incentive budget is the largest single line in E’s capital plan, as Article 4 §4.1 anticipated.
Per Article 4 §4.1 Step 4, time-to-critical-mass is determined by the activation graph, the bootstrapping loop, and the external constraints. For Operator E:
Time-to-MVNS-declared: approximately 28 to 34 months from round close. The Step 5 capital total is computed against this horizon (the 30-month runway used in Step 2), with Step 2 and Step 3 maintenance lines scaled to it.
Per Article 4 §4.1 Step 5, the round size is the sum of Steps 1, 2, and 3, multiplied through the time-sensitive components by Step 4, plus a buffer for execution variance.
Sum of Steps 1+2+3: $7.75m–$11.3m base capital requirement (low-end-of-range to high-end-of-range). The R_j line ($2.0m–$3.0m) and the supply-side cold-start incentive line ($2.5m–$3.5m) jointly account for approximately 55 to 60 per cent of the central case.
Buffer for execution variance: 25 to 35 per cent (the regulated-finance Web3 category buffer specified in Article 4 §4.1 Step 5; wider than the conventional venture range because R_j activation cycle slippage, MVNS upper-bound calibration, and post-MVNS maintenance tail each carry meaningful probability mass beyond the central case).
Derived round size: ~$10m to $15m. The arithmetic: a low-end of $7.75m × 1.25 ≈ $9.7m and a high-end of $11.3m × 1.35 ≈ $15.3m, rounded to a $10m–$15m band.
Round structure: Operator E targets a round of $11m to $14m, structured as two tranches per Article 4 §4.3:
Why the round sits in the upper portion of the derived band. The chosen round ($11m–$14m) sits in the upper-middle of the derived band ($10m–$15m) rather than the centre. The binding constraints (R_j cycle slippage, supply-side cold-start incentive variance, post-MVNS maintenance tail) are right-skewed risks; under-funding is a more expensive failure mode than over-capitalisation. The lower $1m ($10m–$11m) is unallocated on this view; the upper $1m ($14m–$15m) is left out on the symmetric view that an under-utilised treasury creates its own incentive-discipline problems. The band itself is disclosed – the disclosure discipline §4.5 calls for. Market reception is a Phase 2 subject.
Per Article 4 §4.1 Step 5, the burn profile is ramp, plateau, descent – not flat. For Operator E (round size $12.5m central, 30-month runway):
The flat-burn alternative – sizing at $12.5m / 30 months ≈ $0.42m monthly – would under-provision the months-14–24 plateau (where actual burn runs $0.45m–$0.55m monthly) by approximately 7 per cent at the plateau floor and approximately 24 per cent at the plateau peak, and over-provision the months-24+ descent by approximately 30 per cent on average and over 100 per cent by the end of the descent period. This is the precise shape of the failure mode Article 4 §4.1 Step 5 identifies and Hypothesis 3 (Article 4 §4.6b) bets against.
Per Article 4 §4.2, three inputs dominate the round size. For Operator E, with the Step 1–4 derivation as the central case, the sensitivities resolve as:
The sensitivity ordering – time-to-critical-mass dominant, jurisdiction count second, CAC vector second-order – matches the Article 4 §4.2 prediction and is the substantive payoff of running the derivation explicitly: the operator can identify the variables to defend in diligence (time and jurisdiction count) versus the variables that are bounded by structure (CAC).
The worked example is didactic, not predictive. It is designed to make the framework observable as a single integrated derivation rather than as five disconnected articles. Three takeaways are worth naming explicitly:
The round size is an output. The operator did not start with an $11m–$14m number and reverse-engineer to it. The number arose from the activation graph, the bootstrapping-loop choice, the substitution-curve design, and the capital derivation chain. Each input is explicit and would propagate through the model if changed. This is the discipline Article 4 §4.5 names.
R_j is the dominant single line in the model. The combined R_DE and R_NL activation cost ($2.0m to $3.0m) is approximately 18 to 22 per cent of the central-case round. Treating regulatory permission as a constraint to be satisfied – rather than as a node to be activated – would have left this line out of the planning model and produced a round size approximately 15 to 25 per cent too small, with the operational consequence of treasury exhaustion 12 to 18 months in. The Article 1 §1.4 promotion of R_j to graph node is observable here as a $2m to $3m line in the model that would otherwise not exist.
The bootstrapping-loop choice is structurally derived. Operator E selected supply-first not because it was preferred but because the alternatives were structurally unavailable: there was no single-player tool for the demand-first loop, and R_j activation cycles made the simultaneous loop a paid-for-nothing budget item. The decision rule from Article 2 §2.3 produced one answer for this graph and constraint set; the same rule produces different answers for differently-shaped operators, which is what makes the framework portable across the category.
|
Closing observation on Operator E. The numbers in this worked example are illustrative and chosen for legibility. The specific values matter less than the fact that each one is the output of an explicit operation on the activation graph. An operator with different MVNS targets, different jurisdictions, or different participant-class costs will land at a different round size – but the derivation will still run. The framework’s contribution is the discipline that round size is derived rather than negotiated; Operator E shows that discipline applied. |
Phase 1 has now run end-to-end. Article 1 defined the activation graph with regulatory permission as a first-class node. Article 2 specified MVNS as a per-class vector and chose between bootstrapping-loop archetypes. Article 3 made the substitution curve formal and per-class. Article 4 derived capital requirements through the five-step chain and committed to three falsifiable mechanism hypotheses. Article 5 walked the framework end-to-end on one hypothetical operator example.
The two principal novelty claims of the corpus – the promotion of R_j to graph node, and the closed loop from activation strategy to derived capital requirement – are now both observable on a single page (the Operator E derivation) and stated as bets against the next 18 to 36 months of cohort evidence (Article 4 §4.6b). What Phase 2 takes up – beginning July 2026 with Model-Driven Fundraising – is how the derived round size shapes the round itself: investor composition, instrument choice, tranche structure, and the discipline of running a derivation-published round through the diligence cycle the Disciplined Fundraising series treated as the receiving frame.
Phase 2 begins in July 2026. The companion Methodological Appendix V.3.7.0 and Cohort Dataset V.3.7.0 are published alongside Article 1 and update with the rest of Phase 1.
The Polity substrate licence cost line and per-class CAC ranges are vendor-side practitioner anchors per the inline §5.5 disclosure. R_j cost ranges and activation-cycle horizons are anchored to the named cohort (Methodological Appendix V.3.7.0). §5.6 sensitivities are computed against the §5.5 central case and are illustrative of framework response, not predictive of any specific operator’s outcomes.
This article is published for informational and educational purposes only. It does not constitute investment, legal, tax, or financial advice, an endorsement of any product or security, or any offer or solicitation. References to named projects in the cohort and to named public events (token launches, recapitalisations, discontinuations, regulatory milestones) are factual public-record observations recorded for analytical purposes; they are not assessments of those projects’ merits or prospects, and the framework expresses no view on the future trajectory of any individual project. Readers should conduct their own due diligence and consult qualified professionals before acting on any of its content.
Polity is a B2B technology vendor that develops substrate infrastructure for the operators of regulated digital finance networks. Polity does not provide investment advice, custody, crypto-asset services under Regulation (EU) 2023/1114 (MiCA), or any other regulated activity; operator-customers are the regulated entities for any service delivered on Polity substrate. Polity has a commercial interest in the adoption of this framework (operator-customers typically build on Polity substrate); this conflict of interest is disclosed for transparency and is not cured by it.
Forward-looking statements in this corpus – including the §4.6b research hypotheses – are based on current expectations and may prove materially incorrect. Past cohort patterns are not a guarantee of future outcomes. The §4.6b hypotheses are stated for falsification, not as investment recommendations, financial promotions, or solicitations within any applicable regulatory regime.
Published from the European Economic Area; not directed at any person in a jurisdiction where its publication would be contrary to local law. This corpus is not a marketing communication relating to any specific crypto-asset within the meaning of Article 27 of Regulation (EU) 2023/1114 (MiCA); it is a category-level analytical framework. Personal data of natural persons (typically corporate officers of named cohort projects) is processed under legitimate-interest grounds (GDPR Article 6(1)(f)) and confined to the public commercial record.
Third-party names and sources are public-record events; their inclusion implies no commercial relationship, endorsement, partnership, or affiliation. Characterisations of causes, mechanisms, or outcomes of named cohort projects are this framework’s analytical interpretation of the public record, not statements of fact about any entity’s strategy or condition. Inclusion in the companion Methodological Appendix implies no commercial relationship.