Hi NNS participants,
We are CO.DELTA, a verifiably decentralised team of 7 experienced members of the community. We have recently grown from a team of 3, onboarding new talent and expertise in order to expand the number of topics that CO.DELTA is able to specialise in, thereby helping to decentralise the IC. CO.DELTA offers high quality, publicly shared proof of due diligence, provided by experienced members of the community, for the community. The CO.DELTA canister and neuron are operated by consensus, and cannot be controlled by any one individual. Our newest members will soon be granted voting rights within the team, doubling the CO.DELTA Nakamoto coefficient from 2 to 4 (twice the size of the DFINITY Foundation’s known neuron).
We are applying for all 4 grants under the ‘Grants for Voting Neurons’ initiative, encompassing the following topics. In each case we have a dedicated team of 3:
Protocol Canister Management
IC OS Version Election
Participant Management & Node Admin
Subnet management & API BN Management
Meet the Team!
Gabriel
Hi, I’m Gabriel—a dedicated Dfinity ecosystem contributor since 2020, where I’ve been helping build and support the Internet Computer community through both technical development and community leadership.
I’ve been coding in Rust and Motoko since pre-genesis, Go, and JavaScript. My projects include the Mini Big Map tool, React boilerplate, and other community-focused resources that help fellow IC developers.
As a Discord admin from the very first day of the community (both unofficial and official servers), I’ve fostered connections and provided support throughout the ecosystem’s growth. I’m also an active forum contributor and maintain regular communication with the Dfinity team, offering assistance and insights whenever possible.
My focus remains on creating tools and resources that empower the IC community while bridging technical innovation with collaborative community building.
Donna
Hi, I’m Donna. I have been active in the Internet Computer (IC) ecosystem since genesis and was part of the seed investor round. I am also building on the IC, being one of the creators of Dragginz and the Toko Marketplace/NFT maker. Whilst not a developer, I feel I could use my analytical skills and experience to help make a difference.
Towards the end of 2024, I began to notice several warning signs related to Node Provider independence, which led me to conduct deep dives into the entire system. I have since been a driving force behind the improved KYC initiative that is currently being piloted.
My company, Dragginz SARL, has been approved to serve as a node provider, should there be demand for additional nodes. Completing this process has given me valuable insights into how node provider documentation and the onboarding experience could be significantly improved.
I am eager to apply everything I’ve learned over the past several months to help ensure our node providers are well supported and, most importantly, truly reflect the decentralized and sovereign nature the network is meant to embody.
If CO.DELTA is selected to receive one of the node provider grant allocations, I intend to donate any rewards I might receive to support the development of tooling for the Internet Computer ecosystem.
Lorimer
I’m Alex Lorimer, 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. I regularly review IC code and have received numerous bug bounties in the IC ecosystem. As a member of CO.DELTA, my focus is Subnet Management and API Boundary Node Management, as well as IC OS Version Elections.
I have been iteratively improving tooling for performing Subnet Management reviews over the last few months, 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:
- 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.
I have also conducted many IC OS Version Election reviews, and have published related writeups, including Do U C What IC, and have also been involved in numerous discussions around improving IC OS Election/Deployment workflows, including HostOS release cadence (which I’m glad to see has recently become a weekly occurence). As a CO.DELTA reviewer, if elected I intend to dive deep into this topic, which will become my major focus. Among other areas of improvement I’d like to see IC OS releases regularly run by reviewers locally as part of the review process (in addition to the normal build verification and code review). There is also overlap between Subnet Management and IC OS version deployments, and I’m keen to build tooling to help visualise deployment patterns, and reflect on outcomes of IC OS modification.
All in all, I’m excited about levelling up my knowledge and experience in this area, while also continuing to build and refine tooling that will make it easier for anyone and everyone to keep track of IC OS and Subnet Management changes. This is one of my long-term goals on the IC.
Remco
Hello, I’m Remco.
I’ve been following the Internet Computer since 2018 and started building on it right from genesis. Before that, I was a frontend developer who quickly moved into fullstack work. These days, I’m mostly focused on the IC, where I’ve helped a number of projects and founded Toolkit, a platform for canister management, decentralized governance, and asset operations.
Having been around the IC community for so long, it’s been amazing to see the network grow and evolve. Through developing Toolkit, I touch a lot of core IC logic daily, so it felt natural to dig even deeper and start contributing to Protocol Canister Management discussions.
I’m excited to bring a builder’s perspective to the table, with a focus on making things more robust, practical, and developer-friendly as the IC keeps moving forward.
Rok
Hi, my name is Rok. I have 9y+ of proven professional experience as a software developer - mostly backend. I discovered the IC in 2017, being in an ICO list. I received an airdrop of 100 tokens in 2021 and started following the project. I discovered many interesting novelties, like passkeys in 2022 - remember the days you had to enable WebAuth manually in Safari, first chain key integrations in 2023 and an interesting dapp called Taggr which brought me closer to the governance, code and IC environment. I started doing code reviews, got a few bug bounties, and developed some features for the community - which I’m still doing on a best-effort basis.
This year I joined CO.DELTA after a well known member Alex (which I met on Taggr) asked me
if I want to join to do Subnet Management reviews. Up 3 months from then we became a proficient team, and even added another topic (API Boundary Node management) to our list. We understand improvement and learning is necessary to stay afloat. One thing that we are working on is replacing a closed source ic-api. We will switch to retrieving certified data from protocol canisters.
And here we are, looking to expand in all areas of community driven IC reviews. I am most excited about IC OS version election reviews. I am an experienced reviewer, I’ve done it for many years as a backend developer. In the IC world I’ve been reviewing Taggr since the beginning of 2024. IC protocol reviews require broader domain knowledge but I have no doubt in my abilities.
Malith
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 last two years—both personally and through my company, Geodd, which is also a node provider for the network.
Some of the tools we’ve built for the community include:
- IC Node Dashboard for Grafana
- iOS XDR Rewards Widget
- IC Netprobe (ping monitor for NPs)
Over time, I have a solid understanding of how the IC functions internally. I’m eager to make more contributions, assisting in enhancing technical dependability, transparency, and ecosystem support as it expands.
Zane
Hi, I’m Zane
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 ranging from traditional web2 companies to leading a small team tasked with scaling infrastructure for one of Italy’s largest gaming communities.
For the past three years I’ve mostly focused 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.
In parallel, I’ve been performing code reviews for IC-OS version elections, 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.
Together we can make the IC bigger, better, and stronger! 