Voting Neuron Grants – Season 2

Governance NNS Governance
, ,
36

CO.DELTA △ - IC OS Version Election

Voting Neuron Grant Application

  • Topic: IC OS Version Election
  • Total Team Size: 9
  • Specialist Team Size: 3
  • We’re different △ - verifiably decentralised, high quality, publicly shared proof of due diligence, provided by experienced members of the community, for the community. CO.DELTA has no hierarchy. All team members are co-owners of the neuron, the fund dispersal canister, and all other aspects. This is enforced by threshold consensus. Each specialist sub-team within CO.DELTA thereby acts as a distinct entity covering their respective topic.

Specialist Team Members

Name:

Zane

Applied Topic(s):

IC-OS Version Election

Why IC-OS Version Election:

IC-OS Version Elections are in my opinion one of the most important aspects of governance on the IC, no matter how many nodes the network has or how carefully the providers are vetted, if a few malicious lines of code were to sneakily make their way into a release, the consequences would be catastrophic. Since Dfinity is the main contributor to the protocol, this issue might not be very pressing right now, but as the project grows, so will the number of external contributions and the incentives to attack the network.
Over the last two years I’ve been diligently doing code reviews for this topic, specializing in the Execution/Runtime layers of the stack, my motivation to perform this kind of work is to ensure the credible neutrality of the IC isn’t compromised as well as to gain better knowledge of the protocol’s inner workings so I can actively contribute to it, hopefully paving the way towards a future where the foundation isn’t the only organization pushing the IC forward.

Some of my previous reviews:

About me:

I discovered the IC in 2021 and have been actively involved with the ecosystem since. Prior to this, I worked as a full stack developer across diverse environments, from conventional Web2 companies to leading a small team tasked with scaling infrastructure for one of Italy’s largest gaming communities, this experience in particular introduced me to the complexities of distributed systems and sparked my interest in them.
My primary focus over the past three years has been on IC canister development using both Rust and Motoko. During this time I’ve built public utilities, supported teams in delivering their projects and used my technical knowledge to assist the local hub during community events such as crypto conferences and workshops, helping to expand awareness and adoption.
Since the beginning, I’ve been actively engaging in governance discussions and, as of 2023, started performing code reviews on technical topics.

Name:

Gautier Wojda

Applied Topic(s):

IC OS Elections, Application Canister Management, Service Nervous System Management, Protocol Canister Management

Why IC OS Elections:

I’m managing nodes in ge1, ge2 since 3years, and helped for the deployment in es1. It’s important for me to follow the development of ic-os topics for this reason.
I started to review IC-OS ~1month ago with codegov, and i stopped to do it freely before new election and working with co.delta. I enjoyed doing it and i know how important it is to follow the development here to make sure no malicious stuff are added.

Example 1
Example 2
etc..

About me:

I’m a backend and infrastructure specialist with 7+ years of experience. I’m currently co-CTO of GoldDAO and Origyn, and I manage Dfinity nodes for Extragone and DEF. My past work includes kernel development (FreeBSD bootloader/kernel security) and cybersecurity. I’ve been building on the IC for 2+ years, mostly with Rust, and sometimes Motoko.

Notable contributions:

Latest and biggest contribution to IC is the first production ready ICRC7 & ICRC37 NFT implementation, but i also worked on a lot of differents subjects for dfinity. Check my profile for more (icrc3 and stuff like that)

Name:

Rok

Applied Topic(s):

Subnet Management & API BN Management, IC OS Version Election

Why ICOS Version Election:

Version elections ensure that the software running on every replica node in the IC network is reviewed before being released to production.
I see this as a natural extension from managing subnet topology into deeper aspects of consensus, routing, and cryptography - ensuring both security and reliability.

About Me:

I’m Rok. I’ve been working as a software developer for over 9 years now. I first came across the IC in 2017, being in an ICO list. I received an airdrop of 100 tokens in 2021 and started following the project. Over time I stumbled on things like passkeys in 2022, and later the first chain-key integrations in 2023. Around then I found a dapp called Taggr — which was the thing that pulled me into governance and the more technical side of the IC. From there I started reading proposals, doing code reviews, and eventually building a few features.

Earlier this year, Alex reached out and asked if I wanted to help with Subnet Management reviews and form a decentralized group. Five months later we were already covering API BN Management as well, had grown to 9 reviewers, and now running in elections for all topics.

7 Likes