@borovan Strange, would be curios to know who those 3 people are whome you suspect to control 70% of nodes ?
Why would you just give it to co.delta, are you biased for them? I think it should be given to new comers not to existing ones.
I just figured out why youre angry, zack.
I had nothing to do with this though.
Hey @ritvick, everyone whoās interested should apply. Competition in this space is good for the IC 
All thatās needed is for DFINITY to indicate their approval following the broad NNS support that @borovanās proposal has so far gained. Heās asking for an opportunity for anyone and everyone to put themselves forward and let the NNS refresh the electee decisions.
As a side note, CO.DELTA is an entirely decentralised collective, where grant funds are fully managed by smart contract and threshold consensus among team members. To our knowledge weāre the only existing grant recipient like this (in fact DFINITY is now making changes to the grants application process in order to accommodate decentralised canister-controlled recipients like CO.DELTA).
Currently the CO.DELTA team formally covers the Subnet Management and API Boundary Node topics, but as a team we already have broad experience involving the other topics (node provider experience, contributions to notable IC projects, bug bounties, prior experience reviewing IC OS Election prososals etc.). Weāve also been in discussion with numerous talented individuals in recent weeks in order to grow our team.
If DFINITY announce more elections, weāll announce some new additions to the team 
3 Likes
Even if the DFINITY Foundation decides to hold elections in the NNS, with 8 open seats across 4 proposal topics like last time, Synapse & CodeGov will win them again simply by leveraging their full voting power to support their own candidature. We need to form teams, because individuals stand no chance against this kind of oligarchy. This system doesnāt seem to change anything - we need a long-term solution.
1 Like
Would it not be fair if the people who are applying for grants are not permitted to cast votes on who gets the grants?
Come and join CO.Delta then. I think we can outvote Synapse anyway, well, nearly.
1 Like
Following the firm adoption of motion 136448 (see forum announcement), the CO.DELTA team would like to announce that weāre growing to form a team of 7, and weāre ready to cover all 4 grant allocations (should the NNS see fit to elect us).
As mentioned, CO.DELTA is fully decentralised and managed by smart contract, which enforces consensus among team members (including everything from fund management to neuron control). This means the Nakamoto coefficient for the CO.DELTA known neuron will be doubling from 2 to 4 (twice that of the DFINITY Foundation known neuron). Thank you to everyone who reached out to us to demonstrate your interest in joining CO.DELTA, there was some stiff competition. We plan to grow more in the future.
As a team of 7, weāll aim to finish putting our āGrants for Voting Neuronsā applications together for each topic before the end of this week (within the 14 day application window specified by the motion proposal). We encourage existing electees to re-apply for their topics if theyāre still interested in covering them, and/or any other topics theyāre interested in covering. This is a good opportunity to showcase the proposal reviews that youāve been most proud of over the last 6 months or so, and demonstrate to the community why youāre worthy of your spot. We also encourage new faces to apply (even if you donāt receive a position in these elecitons, CO.DELTA is always on the lookout for new talent).
6 Likes
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! 
8 Likes
Congratulations @rem.codes @Gabriel @MalithHatananchchige @Zane @Lorimer @aligatorr89 @Thyassa. You all make a strong team and I look forward to your contributions to the technical proposal reviews the interests each of you. You will surely help advance decentralization of the internet computer. Iām particularly proud of the fact that two of your team members, Alex Lorimer and Zane, were first motivated and incentivized to participate in these technical proposal reviews through CodeGov and are currently still members of the Synapse known neuron. Regardless of the politics that exists around ICP governance, weāve been doing something right to get the right people in place to take an active role. Iām really happy to see that a new larger organization has formed that has attracted so much additional talent to perform the work of reviewing technical changes that are routinely proposed to the internet computer.
Of course, CodeGov will be applying for all grants again when a revised program is rolled out by DFINITY. We will wait to make our announcements until after we learn the details of the revised grant program that DFINITY proposes. My hope is that they will be expanding the number of teams that are funded as well as adding additional technical topics (e.g. Application Canister Management and Service Nervous System Management). Ideally, CodeGov and co.delta will not be the only organizations that seek grant funding for technical proposal reviews and that DFINITY can find a way to support all interested and qualified organizations (as I have advocated previously).
7 Likes
Hello everyone,
We have voted to adopt Proposal 136448, which calls for a re-run of the voting neuron grant recipient election. When we launched this program, we committed to a six-month timeline; that period has elapsed, and it makes sense to hold a fresh vote.
Our plan is to tentatively run the re-election in July. Until then, existing grants and responsibilities will continue uninterrupted.
The precise details of how the vote will be conductedātimeline, voting mechanics, and candidate requirementsāare still being finalized. We expect to share a full schedule and instructions in the coming weeks.
Thank you for your patience and continued engagement.
12 Likes