CO.DELTA △ - Protocol Canister Management
Voting Neuron Grant Application
-
Topic: Protocol Canister 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 Protocol Canister Management:
I have worked extensively with canister-based architectures on the Internet Computer, including governance systems and cross-canister integrations. My work on Toolkit involves interacting with protocol-level canisters such as the ledger and governance canister, ensuring compatibility with governance processes, and following changes in canister APIs and behavior.
I occasionally review relevant codebases to track changes that could impact Toolkit’s integrations and workflows, and I am familiar with assessing how such changes might affect both technical functionality and ecosystem compatibility. This background aligns closely with the review process for protocol canister proposals, where understanding their implications on core system canisters is critical.
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
- GitHub: https://github.com/remco-sprenkels
- 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 Protocol Canister Management:
I’ve been actively involved with the Internet Computer ecosystem since 2020, starting with pre-genesis testing and working with Motoko in its early stages. During this time, I created the first mini-big map example — a project specifically designed to showcase multi-canister architecture and how it can be applied to advanced canister design and interaction patterns. I also developed other small libraries to extend and refine these concepts.
My experience goes beyond just building application logic — I’ve experimented directly with the IC’s WASM modules and WASI interfaces, gaining insight into how the runtime executes canister code and interacts with the host environment. I’ve explored the System API that DFINITY uses for canister management, including inspecting and working with methods for inter-canister calls, stable memory, certified variables, and cycles accounting.
Over the years, I have tested new IC features, reported bugs directly to DFINITY, and, whilst helping others in the community, I’ve learned a great deal myself — deepening my understanding of both the technical and governance aspects of the network. My development work spans both Motoko and Rust, and I’ve been building in Rust for nearly four years on production projects like Dragginz and the Toko Marketplace, both of which rely heavily on multi-canister architecture for scalability and modularity. This combination of high-level design experience and low-level understanding of the IC’s execution model puts me in a strong position to review protocol canister proposals with a focus on security, maintainability, and real-world applicability.
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 Protocol Canister Management:
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).
I’m also closely working with frontend eng for Goldao and Origyn, and even if i’m not frontend specialist, i know how it work/can review for security purpose thoses topics.
I reviewed several protocol-level proposals with CodeGov and enjoyed contributing with a critical lens to the foundation of the Internet Computer. My experience in kernel development, backend infrastructure, and Dfinity ledger internals gives me the ability to audit protocol-level changes thoroughly.
Example 1
Example 2
etc…
Icrc7 nft
Icrc3 lib
Storage canister
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: https://forum.dfinity.org/u/gwojda/summary
-
GitHub https://github.com/Gwojda