DFINITY Foundation

Wenzel

ICDevs.org

CryptoIsGood

Anvil

ICPL.app

ysyms

The Accumulators’ Neuron

RawTech Venture

Paul Young

ICPMANUAL

8YearGangDAO

Isaac Valadez

Krzysztof Żelazko

Nicolas.ic

Smaug’s Neuron for Retail Investors

ICLight.io

Synapse (see neuron merger plan with the Wenzel known neuron)

Taggr Network

CodeGov.org (see neuron merger plan with the Wenzel known neuron)

Sonic AMM

Rakeoff.io

OpenChat

ELNA AI

GEEKFACTORY

ICP Hub México

ICP Hub Poland

Jerry Banfield

WaterNeuron

ICP Hub Bulgaria

Gold DAO

NeuronPool

LORIMER ♾️ 🐶

B3Pay

ZenithCode

Aviate Labs

D-QUORUM

Yuku AI

CO.DELTA △

DragginCorp

Gwojda

Thyassa

🌮 TACO DAO Neuron

Ωmega-reject

Ωmega-vote

αlpha-vote

Cybersecurity

cyberowl

Dexter Caff/acc

This motion proposes to realign and formally rename the current European subnet as the EU/EEA Subnet, approve the immediate replacement of the Switzerland-based Geneva node with an EU-based node in Warsaw, and authorize the onboarding of up to six additional Gen-2 nodes operated by independent node providers in EU member states to establish a fully EU/EEA-jurisdictional, Gen-2-only subnet. Please refer to the summary of the proposal for the full details of the motion.

This motion proposes to realign the current public European subnet and formally designate it as the EU/EEA Subnet, ensuring that it operates exclusively under EU and EEA jurisdiction and aligns with applicable European regulatory and data protection frameworks, including GDPR, DMA, DSA, and Schrems II.

The current European subnet includes nodes located outside the EU/EEA (notably Switzerland), infrastructure operated by non-European data center owners subject to extraterritorial legislation such as the US CLOUD Act, and a mix of Gen-1 and Gen-2 hardware. Together, these factors introduce jurisdictional ambiguity, legal uncertainty, and an inconsistent security baseline that can inhibit adoption by developers and enterprises requiring clearly defined EU-only deployment environments.

This proposal seeks to remove these ambiguities by:

- Ensuring that all nodes in the subnet are physically located within the EU or EEA

- Strengthening the subnet’s security posture by standardizing on Gen-2 hardware with AMD SEV, enabling encryption of data in use and supporting GDPR principles of data protection by design and by default

- Establishing a clearly defined, auditable EU/EEA-compliant subnet that is easier to adopt for regulated workloads

### What This Motion Explicitly Approves

If adopted, this motion proposal explicitly approves the following actions:

1. **The realignment and formal renaming of the current European subnet to the “EU/EEA Subnet.”**

2. **One immediate node replacement**, swapping the existing Switzerland-based node in Geneva with a node located in Warsaw (EU).

3. **Authorization to onboard up to six additional Gen-2 nodes**, operated by independent node providers and located in EU member states, to complete the transition to a fully EU/EEA-based, Gen-2-only subnet.

Together, these enable the transformation of the existing European subnet into a clearly defined, jurisdictionally consistent, and GDPR-aligned EU/EEA Subnet.

Realignment and Rebranding of the European Subnet to an EU/EEA Subnet