Jurisdictions
EU-first jurisdiction strategy with phased expansion beyond the initial operating footprint.
The public compliance story is currently best understood as:
- EU-first
- passporting-oriented
- phased
Current Direction
The docs describe the network as pursuing an EU-centered authorization strategy first, with additional jurisdictional expansion treated as later-stage work. "EU-first" describes sequencing, not scope : ƒxyz is global infrastructure that started incorporation in Poland, and the EU node is where it starts rather than where it ends.
Current operating jurisdiction: the EU, where FXYZ Sp. z o.o. (Poland, KRS 0000816477) is the primary node. EU passporting logic is central to the authorization strategy, and the multi-entity design provides for additional nodes in other jurisdictions as the network grows. See Entity Structure. Non-EU corridors are staged, not the primary authorization frame.
Why This Matters
Jurisdiction is not just legal overhead. It affects:
- licensing path
- reporting obligations
- consumer protections
- operating costs
- where the platform can expand efficiently
Reader Rule
This page should be read as jurisdiction strategy, not as a definitive final map of every future operating market.
For current public docs, the key point is simple:
- the EU remains the primary frame
- passporting logic is central to the strategy
- non-EU expansion is selective and phased
Jurisdiction strategy, timing, and expansion logic remain subject to regulatory change and legal review.