Early 2022 me and some of my team members were working on a safer alternative that would enable the creation of multisig addresses compatible with any cryptography for blockchain networks.
Most of them were using ECDSA at that time and still are, but others chose the newer and more efficient EdDSA. I won’t be getting into which one is better (EdDSA ), since this isn’t the purpose of this post.
After researching potential solutions, we stumbled across threshold signature scheme public repos on Github, which at the time was being maintained by Binance (binance-tss) and it seemed like the best solution, but the EdDSA implementation was still under development. We needed to deliver a solution, so we picked up and finished the TSS EdDSA implementation.
By the time it was done, we were already quite knowledgeable on this matter and decided to use this knowledge in practice. We’ve searched for several use-cases and started contacting communities to see if there was demand for a potential use-case. Zenon wasn’t among them, but luckily, one community member noticed us and reached out.
We’ve been skeptical at first, but we decided to give it a go (the Hyperspace program was ongoing) and see if we can build a prototype. What started as a prototype, became a long journey to develop a full-stack interoperability solution that we call “The Multiverse”, a multi-chain technology for NoM.
As a result, we enrolled into the Hyperspace Program with the purpose of developing a native, end-to-end interoperability solution for NoM.
After diving deep into the technical particularities of NoM and an initial research phase, we’ve started to develop and deliver milestones with the end goal of deploying a fully functional multi-chain solution.
After learning about the Protocol Level Liquidity and the liquidity embedded contract, we’ve decided to finish the implementation as it perfectly complements the decentralized bridge and it constitutes a pillar of long-term sustainability for the entire ecosystem.
Along this journey we’ve faced countless obstacles and challenges, but we’ve managed to overcome them and the merging of our codebase into the official Zenon repositories represents a culmination of months of hardcore development.
That being said, we want to continue our participation as full-time members of a Hypercore development team, dedicated to push forward this ecosystem and create solutions that are aligned with the founding principles of NoM.
Seeing the reluctance other contenders have received when they showcased their ideas, we took upon ourselves the risk of putting in the work upfront. And as you have noticed, we did our very best to deliver the highest quality work and state-of-the-art solutions.
As the team stated from the beginning, the Hyperspace fund has 120k ZNN and 1.2M QSR for the teams involved in developing and deploying interoperability solutions for NoM.
Our NoM team consists of several developers:
- 2 Go devs
- 1 Solidity dev
- 1 full-stack dev
- 1 tech lead
Beside the “raw” development, there were other parts such as:
- onboarding the team on this project
- getting familiar with the custom NoM cryptography (EdDSA, address derivation, etc.)
- getting familiar with the undocumented embedded contracts architecture (send-receive, account block model, etc)
- researching the architecture and go-zenon source code
- creating a project plan
- defining the infrastructure architecture
- prototyping an initial MVP
- creating the documentation
- countless code reviews
- regular internal security audits
- researching attack vectors
- brainstorming test-cases
- implementing unit-tests
- manual testing
- costs with VPSs for public testnet
- costs with dedicated server for internal testing and benchmarks
- costs with deployment of solidity contracts
- opportunity cost
What we ask for?
A total of 95k ZNN and 950k QSR out of the 120k ZNN and 1.2M QSR from the Hyperspace fund for the interop solutions that will enable us to:
- deploy at least 1 Pillar for on-chain voting rights and enabling us to be a bridge participant so we can actually debug things in realtime on the mainnet
- deploy Sentinel nodes
- stake ZNN to generate QSR
- cover past expenses by liquidating small amounts generated from the rewards of pillar/sentinels/staking without impacting the ZNN/QSR markets
However you’ll do the math, the 10+ months of intensive work on such a complex piece of software (over 20k lines of code) will end up costing more than that.
As we’ve already stated before, an important part of the funds that we will receive from A-Z will be used to establish a permanent presence in the community with the goal to become self-sustainable and even expand the team once the price rises enough to cover ongoing expenses.