Voting Neuron Grants – Season 2

Governance NNS Governance
, ,
37

CO.DELTA △ - Subnet management & API BN Management

Voting Neuron Grant Application

  • Topic: Subnet management & API BN Management
  • 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:

Alex Lorimer

Applied Topic(s):

Subnet management & API BN Management, Participant Management & Node Admin, SNS & Neurons’ Fund

Why Subnet management & API BN Management:

These topics are foundational to deterministic decentralisation, which the IC depends upon. I have been iteratively improving tooling for performing Subnet Management reviews over the last year, most recently encompassing API Boundary Node Management proposal reviews. I’ll soon also finish removing a dependency on the IC API, ensuring all metrics come from verifiable sources. Other work-in-progress tooling includes a decentralisation step optimiser. I’ve been conducting subnet management proposal reviews as an elected reviewer since the end of last year. I’m proud of each and every review, and I do my best to go above and beyond. Here are some notable examples:

  • 137677 - A proposal that would have left the subnet in a vulnerable state during synchronisation (due to proximity to the consensus threshold)
  • 136565, 136566 - My first API Boundary Node Management reviews
  • 135248, 134971, 134674 - Detailed analysis of public/private subnet changes
  • 133444 - A proposal that would have unwittingly left the subnet with fewer nodes
  • 134256, 134318 - Another example of catching things that others missed
  • … there are many, many more. Please consider browsing.

About me:

I’m an experienced full-stack software developer, with an MSc in Computer Science and a ResM (research masters) which focused on mass-participatory design. I’m passionate about Web3 governance, and I’m dedicated to improving tooling, as well as processes and procedures relating to NNS participation. “Power tends to corrupt, and absolute power corrupts absolutely.” The IC is the solution, and I’m very driven to help it succeed. I’m also heavily staked in the IC. I’m devoted to securing that long-term stake, and that of all other ICP stakers. I regularly review IC code and have received numerous bug bounties in the IC ecosystem. I’m also extremely active in governance matters and regularly post reviews, and vote on a range of topics. I’m always looking for opportunities to build tooling for the topics that I focus on in order to improve reliability, robustness and attention to detail.

Name:

Malith Hatanachchige

Topics Applied:

Participant Management & Node Admin
Subnet management & API BN Management
Application Canister Management

Why Subnet Management & API BN Management

I’ve reviewed over 120 proposals in Subnet Management & API BN Management. My reviews are based on independent tools and direct infrastructure experience, which helps catch issues and improve the quality of decisions.

Notable contributions

  1. Highlighted the lack of a proper validation method for Nakamoto Coefficient calculations when reviewing a new US application subnet. This feedback supports Dfinity in defining better parameters for country-based topology.
    → Discussion
  2. Helped with quick adoption of vetKey deployment while ensuring proper validation.
    → Discussion 1
    → Discussion 2
  3. Early tooling and reviews for subnet proposal validation.
    → Example

About me:

Hi, I’m Malith. I’ve been working in software and infrastructure for over 13 years, across everything from frontend/backend development to AI/ML and large-scale infrastructure for Web2, Web3, and AI inference workload. I’ve been part of the ICP community for the past two years, contributing by building useful tools for node providers, actively participating in the AI Technical Working Group, and operating as a node provider covering the South Asia region. And, as a Subnet Management & API BN Management reviewer, I’ve reviewed over 120 proposals.

My voting principle has always been to respond quickly, even if it’s to reject, while keeping my decisions fair and focused on the long term, so people can move forward with their tasks faster. To support this, I’ve built automation tools to handle background fact checking and research, which I then manually double check. Before casting my vote, I make it a point to consider the bigger picture.

In the blockchain industry as a whole, ICP is setting a strong precedent for driving mass market adoption of DApps, and the progress so far has been remarkable. I believe that supporting ICP by ensuring the safety and integrity of the community is crucial, as it allows the core team to focus on advancing the ICP and accelerating meaningful change.

I have been continuously contributing to the community, and I intend to maintain the same effort beyond the grant period.

DFINITY forum
LinkedIn
GitHub

Name:

Rok

Applied Topic(s):

Subnet Management & API BN Management, IC OS Version Election

Why Subnet management & API BN Management:

Subnet management is essential for maintaining proper decentralization - what we call ‘deterministic decentralization’. ‘Deterministic’ means we can explicitly calculate the Nakamoto Coefficient (NC) for network nodes across different characteristics.
We measure NC based on a pre-agreed target topology, assess provider quality, and monitor clusters - groups of nodes potentially controlled by a single beneficiary.

For the past six months I have been conducting these reviews. My future goals include improving sourcing, moving away from the IC API, and maintaining a comprehensive and up-to-date overview of subnet health.

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.

5 Likes