Decision Document · Cross-Brand Liquidity

Shared liquidity is not achievable. Here's what is.

Compliance has assessed eight variants of cross-brand prize-pool sharing between MetaWin.us and MetaWin.com. None survive structural scrutiny. This document closes that exploration and presents three achievable adjacents that deliver meaningful commercial value. A decision is needed on which to pursue.

Decision owner · CEO + Commercial Lead Prepared by · Legal & Compliance Audience · Richard, Commercial Leadership Generated · 13 May 2026
§
Closure Document · Supersedes Prior Variant Assessments
This document closes a thread of eight successive variant assessments on whether MetaWin.us and MetaWin.com can share liquidity on a prize promotion (Friday Fire as the working example). The recommendation is to stop iterating on shared-liquidity structures and pick one of the achievable adjacents below.
Contents
01 / Summary

Executive summary

Headline

Genuine shared liquidity between MetaWin.us and MetaWin.com on any prize promotion is not achievable under the combination of US sweepstakes law and MetaWin.com's current licensing posture. Eight variants have been assessed across the thread; each fails on the same structural defect — any prize-determination calculation that takes inputs from both populations constitutes a single integrated promotion at the allocation layer, which collapses the .us / .com separation that makes both businesses lawful in their respective markets. Three adjacents are achievable and deliver substantial portions of the commercial intent. The decision needed is which adjacent to commit to.

Variants assessed
8
Variants defensible
0
Achievable adjacents
3
Compliance recommendation
Adjacent C
Iteration risk
High
Eight rounds — recommend close
Commercial value at risk
Recoverable
Adjacents capture ~70-80%
Time to decision
2 weeks
Pick adjacent → product scope
!
Why this needs leadership-level closure

The pattern of producing variant after variant of shared-liquidity structures, each marginally different from the last, is itself a strategic risk. Each iteration accumulates internal documentation that — in any future discovery process — would read as the operator looking for ways to engineer around US gambling law. Closing the iteration with an explicit decision protects the .us licensing posture from death by a thousand cuts.

02 / Structural conclusion

Why no version of shared liquidity works

The structural defect is consistent across every variant assessed. It can be stated in one sentence:

Any allocation mechanism that takes inputs from both .us and .com populations creates a single integrated prize-determination event, which constitutes a single sweepstakes operating across both platforms, which collapses the legal separation that makes each business lawful in its respective markets. — The structural conclusion, stated plainly

The form of the inputs is not the test. Entry counts, headcounts, revenue, activity levels — any input from both populations creates the same defect. The form of the payout is not the test either. SC, USD, crypto, on-chain tokens — any payout from a single allocation event constitutes the same integrated promotion.

The only structural construct that survives is one where the two populations are economically decoupled at the allocation layer — i.e. a fixed dollar allocation agreed in advance, where neither population's behaviour during the promotion affects the other's prizes. That construct is one of the achievable adjacents (Adjacent B below). It does not feel like shared liquidity to users because it isn't shared liquidity.

The three things that cannot be true simultaneously

Constraint 1
MetaWin.us operates as a US sweepstakes
Requires dual-currency SC construct, AMOE, US entity as sole operator of any draw with US participants, no cross-platform consideration pathways.
Constraint 2
MetaWin.com operates outside US licensing
Cannot accept US participation, cannot run US-targeting promotions, cannot integrate operationally with a US sweepstakes promotion.
Constraint 3
A single prize pool is shared between both
Requires both populations to compete for, or have prizes determined by, a single allocation event that takes inputs from both sides.

Pick any two; you cannot have all three. The variants in this thread have been successive attempts to find a third way that respects all three — and each attempt has failed because no such way exists within current US sweepstakes law combined with MetaWin.com's licensing posture.

i
What would change this

Only two things would unlock genuine shared liquidity: (1) MetaWin.com obtaining US iGaming licensing, fundamentally changing its business model; or (2) MetaWin.us pivoting from sweepstakes to a licensed gaming operator. Both are multi-year strategic moves with capital implications that sit far above this decision.

03 / Work done

Variants assessed

Eight distinct variants of shared liquidity have been considered. The table below summarises each, the structural defect that defeats it, and the analysis depth applied. None are recoverable through further iteration on the same structure.

# Variant Why it fails Status
1 Shared pool, .com-operated draw, US users enter via SC Imports US users into a .com-operated promotion. .com is unlicensed for US. Collapses .us / .com separation. Operator-identity defence fails. Blocked
2 Equity in the .com pool, SC payout to US users Payout currency is downstream of participation. US users still participating in a .com promotion. Same operator-identity defect. Blocked
3 DAP purchase on .com grants entries to .com draw, open to US The .com prize draw construct is not built to US sweepstakes standards. AMOE pathway, dual-currency separation, redemption mechanics all absent. Cannot be retrofitted. Blocked
4 SC payout on both .com and .us SC label does not carry US legal construct across platforms. Creates fungibility bridge between .us and .com. Worse than the original, not better. Blocked
5 .us-operated draw, .com users enter as international entrants Workable in principle if .com users onboard to .us. Without that, .com purchases granting entries on .us is a cross-platform consideration bridge. Cannot survive. Conditional only
6 On-chain draw via smart contract US gambling law is technology-agnostic. Smart contracts have no legal personhood. Operator is whoever deploys/markets/funds. Attracts rather than avoids regulatory attention. FinCEN exposure on crypto payments to US residents. Blocked
7 Two draws, single pool, allocation by entries Allocation event takes inputs from both populations. Constitutes single integrated promotion at allocation layer. Substance-over-form analysis defeats two-draws framing. Blocked
8 Two draws, single pool, allocation by headcount Same defect as #7 with a different input. Headcount is still a cross-population allocation input. Couples populations through prize-determination calculation. Operational data sharing between platforms reinforces the defect. Blocked

The pattern across all eight variants: each is an attempt to engineer around the structural conclusion by varying the surface mechanics. None varies the underlying defect, because the underlying defect is the construct itself — combining .us and .com prize determination in any form.

04 / What works

Achievable adjacents

Three constructs deliver substantial portions of the commercial intent (scale perception, cross-brand moment, family branding) without breaching the structural constraints. They are not interchangeable — each optimises for a different commercial outcome.

Adjacent A · Parallel mirrored draws

Both brands run Friday Fire simultaneously. Same theme, same creative, same week. Two genuinely separate draws, two separate prize pools (each funded by its own entity), two separate winner lists. No financial linkage, no cross-platform entry, no shared allocation. Users on each platform see synchronised family branding.

DimensionAdjacent A
Commercial outcomeCross-brand FOMO, shared moment, family narrative
Structural riskMinimal — two genuinely independent promotions
Effort to buildLow — both brands already run promotions; this is coordination
LimitationNo prize-pool scale benefit on either side. Each entity bears its own cost.
Best fit if commercial wantsA coordinated marketing moment across the family

Adjacent B · Single budget, fixed split, two operationally separate draws

A single committed budget for Friday Fire across the family. The split between .us and .com is agreed in advance and held constant — e.g. .us gets $60k, .com gets $140k, decided at the start of the period, doesn't move based on user activity. Each entity then runs its own draw under its own legal construct for its allocated share. Marketing has to be precise — the pool is presented as "two draws across the family", not "one shared pool".

DimensionAdjacent B
Commercial outcomeShared budget framing, larger combined prize visible to both populations
Structural riskLow — fixed allocation decouples populations at the allocation layer
Effort to buildLow-medium — coordinated funding mechanics + marketing discipline
LimitationAllocation cannot float with user activity. Marketing cannot claim "one shared pool" — must say "$200k across the family, $60k on .us, $140k on .com" or equivalent.
Best fit if commercial wantsThe appearance of scale through a shared family-wide budget

Adjacent C · Standalone .us Friday Fire, .com-funded prize pool

A single .us Friday Fire, operated by MetaWin.us under the standard US sweepstakes construct, with the prize pool funded substantially by inter-company contribution from MetaWin.com. No .com user participation. The .us draw is scaled up by .com's funding contribution. .com gets co-branding rights on .us marketing (subject to separate review of crypto-casino-adjacent marketing exposure).

DimensionAdjacent C
Commercial outcomeBigger .us prize pool / scale perception on .us. Family branding via co-branding.
Structural riskLowest of the three — fully standalone US sweepstakes, .com is purely funder and marketing partner
Effort to buildLow — inter-company funding mechanics + standard .us promotion mechanics
LimitationNo .com user participation. .com gets brand benefit, not user benefit. May not satisfy commercial if their goal is .com user retention.
Best fit if commercial wantsMaximum scale perception on .us with minimum legal complexity

Comparison at a glance

Outcome priority Adjacent A Adjacent B Adjacent C
Bigger .us prize pool / scale Weak Moderate Strong
Cross-brand family moment Strong Strong Moderate (via co-brand)
.com user benefit Direct (.com runs own draw) Direct (.com share) None directly
Structural defensibility Highest High Highest
Build complexity Low Low-Medium Low
Marketing discipline required Low High Medium (co-brand framing)
05 / Recommendation

Compliance recommendation

Recommend Adjacent C — standalone .us Friday Fire, .com-funded

Adjacent C is the recommended path on grounds of (a) strongest match to the stated commercial priority of scale perception on .us, (b) lowest structural complexity, (c) cleanest defensibility, and (d) lowest marketing risk. It preserves the .us licensing posture absolutely and creates the smallest evidentiary surface for the related-entity narrative.

Recommended
Adjacent C
Acceptable alternative
Adjacent B (if family-wide pool framing is essential)
Acceptable alternative
Adjacent A (if scale matters less than coordination)
Not recommended
Further variants of shared liquidity

If commercial pushes for Adjacent B over C

Adjacent B is the closest available construct to genuine shared liquidity. It is defensible only with strict discipline on two points: the allocation must be fixed in advance and unchanging, and the marketing must accurately describe the construct as separate draws across the family rather than as a single pool. If either discipline slips, Adjacent B drifts toward the failed variants. Compliance support for Adjacent B is conditional on a marketing-approval gate where copy is reviewed before publication.

If commercial wants .com user participation specifically

None of A, B, or C delivers genuine .com user participation in a .us-operated draw. The only construct that did was the earlier variant where .com users voluntarily create .us accounts to participate (referenced in the prior report as the "Constraint A" version). That construct is defensible and remains available. It was set aside earlier in the thread on a "no .com user touches .us" preference; if commercial is willing to revisit that constraint, the Constraint A version is the genuine shared-participation path.

!
What compliance cannot support

Any further variant of shared liquidity that combines .us and .com population data in a single allocation event, regardless of how the allocation is mathematically structured. This has now been declined eight times. The next decline will be referred upward as a structural disagreement rather than a per-variant analysis.

06 / Decision

Decision needed

One decision is needed from leadership to close this thread and unlock the next step:

Option 1
Adopt Adjacent C
Standalone .us Friday Fire, .com-funded prize pool. Compliance-recommended. Lowest risk, strongest scale outcome on .us. Move to product scoping immediately.
Scale outcome Strong Risk Low Build S
Option 2
Adopt Adjacent B
Single budget, fixed allocation, two operationally separate draws. Acceptable if family-wide pool framing is commercially essential. Requires marketing-approval gate.
Scale outcome Moderate Risk Low Build M
Option 3
Adopt Adjacent A
Parallel mirrored draws, no financial linkage. Lowest commercial ambition. Useful if scale matters less than a coordinated brand moment.
Scale outcome Weak Risk Minimal Build S
Option 4
Revisit "no .com onboarding" constraint
If commercial's real priority is genuine .com user participation in a shared draw, the Constraint A version (.com users voluntarily onboard to .us) is defensible. Requires accepting account-creation friction in the user journey.
Scale outcome Strong Risk Medium Build M-L

Sequence to decision

Week 1 · This week
Commercial confirms primary outcome priority (scale on .us / family pool / coordination / .com participation).
Week 1 · This week
Richard's signoff on selected adjacent. One option, written down, committed.
Week 2
Product scoping for chosen adjacent begins. Compliance available for design review.
Ongoing
Shared-liquidity exploration thread is closed. Future cross-brand promotion design starts from the chosen adjacent as the baseline.
What good looks like

Leadership picks one adjacent, commits in writing, and the team moves to building it. No further variant analysis. Future cross-brand questions reference this document as the structural baseline rather than reopening the same exploration.