Entity Structure
Current and planned entity-structure framing for the ƒxyz Network.
This page explains the legal-entity layer as planning and structure, not as a substitute for the app’s legal-entity route docs.
Current Publicly Referenced Entity
The public docs reference:
- FXYZ Sp. z o.o. : Polish registered entity, KRS 0000816477, as the current operating entity anchor in the EU-facing story. Currently VASP-active (spot-crypto scope); MiCA CASP Level 3 application in process with IAS Katowice (case 2401-RRDR.4225.244.2025.1).
Planned Structure
The public planning model also assumes:
- an EU licensing entity posture for later authorization phases
- possible additional entities for later corridor or jurisdiction expansion
Why It Exists
The entity layer exists to support:
- licensing
- regulated operations
- legal accountability
- separation between operational and regulatory obligations
What It Is Not
It is not the same thing as the live app route surface.
For the routed product surface, use:
Entity plans, future structures, and licensing relationships are subject to change and should not be treated as binding commitments.
Licensing Roadmap : VASP, MiCA CASP & Payment Institution Pathway
The phased regulatory licensing strategy for fxyz Network. Details on Polish VASP registration, MiCA CASP Class 3 authorization, and the PI/EMI e-money roadmap.
Token Compliance
MiCA classification analysis for each ƒxyz Network token, white paper requirements, and current compliance status.