We’re excited to announce a major milestone for the Swiss Subnet — the first batch of node providers from Liechtenstein and multiple Swiss cantons are now beginning onboarding to the Internet Computer Protocol (ICP). This marks a big step toward the go-live of a secure, compliant, and high-performance blockchain infrastructure purpose-built for the next generation of digital services.
Decentralization is at the heart of this initiative. All node providers are completely independent — from us and from each other — ensuring the Swiss Subnet’s resilience, security, and integrity.
Please join us in welcoming these providers to the community — together, we’re building a stronger, more decentralized Internet Computer.
We’re excited to officially join the Swiss Subnet as one of the new node providers from Switzerland
Our company is based in the canton of Vaud near Lausanne and has 15 years of experience in delivering reliable datacenter services, mainly in the French-speaking part of Switzerland. We operate with a strong focus on security, availability, and energy efficiency, ensuring our infrastructure is fully aligned with the high standards expected in the Swiss digital ecosystem.
We are interested in running nodes for the IC/Swiss Subnet as it combines data sovereignty, geographic exclusivity, and regulatory compliance - values that match our company philosophy. This allows us to support institutional clients who require strict security and compliance, while contributing to the resilience and decentralization of the network.
Shortly, we will submit the following proposals to onboard ourselves as node providers for ICP:
It’s important to rigorously assess all new Node Provider registrations. This proposal showed an appropriate level of transparency and due diligence.
About Krzysztof Żelazko
Independent reviewer and Governance Lead at ICP Hub Poland. Votes manually on NNS proposals related to decentralization, node operations, and governance integrity. Aims to support transparency and the long-term health of the Internet Computer ecosystem by making fair and well-reasoned decisions.
Aviate Labs is a team dedicated to supporting node providers since 2020. Our mission is to make high-performance infrastructure management on the Internet Computer (ICP) as seamless as possible, while adhering to the principles of decentralization.
We are known for our contributions to the ecosystem, including the go-agent and developer work packages on GitHub, as well as the Node Monitortool, which alerts Node Providers as soon as any of their nodes go down.
In the NNS, Louise reviews and votes independently on ‘Node Admin’ and ‘Participant Management’ proposals on behalf of the Aviate Labs Neuron.
The Aviate Labs known neuron is configured to follow Louise for these topics and other trusted entities for broader proposals. We strive to be a credible and reliable Followee, committed to voting on every proposal and supporting decentralization within the ICP ecosystem.
We believe the audits should be conducted only for new node providers that the community considers controversial or raises concerns about. We do want to have multiple node providers audited, but resources are limited. Once the pilot is complete and the process is established, the expectation is that node providers will cover the cost of their own audits. So please let us know if any of the SSN NP applications require a closer look. We’ll be watching as well!
We are AITUBI and have previously onboarded as a node provider, awaiting an opportunity to start operations. This has now become a reality by joining the Swiss Subnet.
We are an innovation company with track record and focus on launching tech enabled start-ups specifically in the area of distributed systems.
Previously we invested and worked in insurtech, cybersecurity insurance and data protection businesses. Our focus as an ICP node provider is to help enter new segments that complement the existing network, in particular in emerging markets and sovereign subnets, of which Swiss Subnet is a first example.
We are based in Switzerland in the canton of Zug, also known as the “crypto valley”. You can find our credentials here
About CodeGov CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, API Boundary API Boundary Node Management, Node Admin and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons' Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Can I ask how you generated your pdf documents? The text isn’t searchable or highlightable. It appears to be embedded as an image. This makes it harder to cross-reference with other material.
@ic.aitubi and @alpinedc, can you confirm that you’re happy to comply with this requirement in the near future?
@alexu, can I ask why we don’t currently have a syndication phase for new node providers (much like for prospective SNSs)? I would far prefer an announcement a week or so in advance of any proposal. This gives the community the chance to inspect the documents and hashes before the proposals are raised, and also provides more time (with less rush) for interested parties to engage and ask pertinent questions without the feeling of some sort of rush.
If a syndication phase is a requirement for SNSs, I would like to propose that it should be a requirement for new node providers.
I’m interested in hearing the opinions of other reviewers on this.
The Swiss Subnet is rented, and would be removed if rent is not paid. It’s the first of it’s kind which is very exciting. But there are also aspects I’m currently uncertain about. In the event that the proposer of the subnet no longer wishes to continue paying this rent, what should the NNS assume becomes of the node providers that were onboarded expressly for participation in said subnet?
TLDR: I’m planning to await answers to the questions I have raised above followed by further inspection before voting on this proposal. I’d like to ensure my vote is as informed as it can be.
You may wish to follow the CO.DELTA known neuron if you found this analysis helpful.
CO.DELTA △
We’re a verifiably decentralised collective who review IC deltas (changes applied by NNS proposals). We follow a common code:
Look: We observe the details and context of NNS proposals
Test: We test and verify the claims made by those proposals
Automate: We automate as much as possible by building increasingly sophisticated tools that streamline and strengthen the reviewal process.
Every vote cast by CO.DELTA is the result of consensus among diligent, skilled and experienced team members acting independently. The CO.DELTA neuron follows the vote of D-QUORUM on NNS topics that the CO.DELTA team does not handle directly. You can therefore follow CO.DELTA on all topics and rely on the highest quality of vote.
Forum Introduction
