CO.DELTA △ - Service Nervous System Management
Voting Neuron Grant Application
-
Topic: Service Nervous System 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:
Remco Sprenkels
Applied Topic(s):
Sns And Community Fund, Service Nervous System Management, Protocol Canister Management
Why Service Nervous System Management:
I have practical experience working with SNS deployments, from configuration and launch to post-decentralization governance. I occasionally review the SNS codebase as part of my work on Toolkit, which involves integrating SNS-related functionality such as proposal handling, parameter adjustments, and canister lifecycle operations. I also occasionally speak with people involved in improving the SNS to clarify technical details and better understand upcoming changes.
This work gives me familiarity with the SNS architecture, common change patterns, and potential areas of risk. While I have not yet performed formal SNS management proposal reviews, the overlap between my current work and the review process means I am already accustomed to reading through SNS changes, understanding their purpose, and considering their impact on governance and interoperability.
About me:
I am a developer with around 10 years of experience, starting in frontend development and later moving into fullstack work. I have followed the Internet Computer since 2018 and have been developing on it since genesis in May 2021. Over that time, I have worked on various projects within the IC ecosystem, covering areas like governance systems, canister architecture, and automated proposal execution.
I currently lead the development of a governance and project management platform on the IC that supports multiple governance models, secure canister lifecycle management, and integrations with other services. This work has involved reviewing upgrades, designing state migration strategies, and ensuring compatibility across different IC components. My experience gives me a practical understanding of both the technical and governance aspects of the Internet Computer.
-
DFINITY forum: Profile - rem.codes - Internet Computer Developer Forum
-
LinkedIn: https://www.linkedin.com/in/remco-sprenkels-49a44687/
Name:
Gabriel Nicola
Applied Topic(s):
SNS & Neurons’ Fund, Protocol Canister Management, Service Nervous System Management
Why Service Nervous System Management:
I have extensive hands-on experience with SNS governance and technical implementation, having been directly involved with one of the most complex SNS operations to date. As part of the Dragginz project, we were the first SNS to successfully execute a token dilution event — minting additional tokens, disbursing them proportionally to all existing SNS-1 holders, changing the token symbol, and adapting the SNS settings to align with Dragginz’s requirements.
This operation required deep understanding of SNS mechanics and careful coordination of multiple proposal types. To properly test everything, I had to set up a complete local SNS replica with the exact settings of SNS-1, including taking snapshots of all current token holders and recreating the entire governance state locally. This let me test the minting and distribution logic extensively before executing on mainnet — which was crucial since no previous project had attempted such a comprehensive transformation of an existing SNS.
Through this experience, I gained intimate knowledge of SNS proposal validation, canister upgrade processes, and the critical importance of verifying build hashes and API compatibility. I understand how proposal text must align precisely with actual code changes, and I’ve seen what happens when governance parameters need adjustment after deployment. Building the local testing environment also gave me deep insight into SNS initialization parameters, token economics, and how different SNS canisters interact.
My technical background in multi-canister architecture and System API exploration gives me the ability to conduct thorough code reviews.
This combination of pioneering SNS governance experience, technical knowledge, and practical understanding of how SNS changes affect live projects positions me well to review SNS management proposals with focus on technical accuracy, security implications, and operational feasibility.
About me:
I have over 11 years of coding experience, including work in banking solutions where precision, reliability, and strict compliance were essential. This background taught me to review code and systems with a strong focus on security, which is important for protocol-level canister management.
Since joining the IC community in 2020, I’ve been active in both development and governance, building canisters, contributing libraries, reporting bugs, and assisting the community. My work includes early Motoko projects, multi-canister system designs, and large-scale Rust applications like Dragginz and the Toko Marketplace. I’m passionate about building secure, scalable, and maintainable canister-based systems and sharing that knowledge with the community.
-
DFINITY forum: Profile - Gabriel - Internet Computer Developer Forum
-
Github: gabrielnic · GitHub
Name:
Gautier Wojda
Applied Topic(s):
IC OS Elections, Application Canister Management, Service Nervous System Management, Protocol Canister Management
Why Service Nervous System Management:
I am involve in Origyn and goldao SNS, 2 of the biggest sns done on ic.
I was strongly involve in the Origyn sns migration (Origyn had his own implementation, and was migrate to SNS last year)
I have strong knowledge in SNS in general, and want to participe and follow more this topics, to follow development and new features, to make sure when we update canisters, nothing on Goldao or Origyn will broke due to a breaking change.
What i can bring is my web3 dev knowledge. I’ve built and audited numerous backend canisters, including complex services that use stable memory, chunked data, token standards, and indexing. I’ve reviewed some DFINITY projects and community libraries (like asset canisters, ICRC interfaces, 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)
-
DFINITY forum: Profile - Gwojda - Internet Computer Developer Forum
-
GitHub Gwojda · GitHub
-
LinkedIn Gautier Wojda - Bity | LinkedIn