As you may know, my old spq-sigs project has been transformed into a slower moving post-quantum project existing 100% at the library level.
The original plan was to create a post-quantum hash-based signatures setup tailored specifically at the HIVE eco-system. I created a DHF proposal that could have allowed me to allocate time to it, but I didn't get funding, so I changed the plans.
I dropped the HIVE tailoring and some of the HIVE programming languages, dropped the idea of diving into the core C++ code and making a concrete HIVE proposal. I ended up with a shallower but wider, and fundamentally more generic project: coinZdense
While I haven't been posting in this community much, I've been posting in HiveDevs, mainly because of the number of subscribers, I have been working on the project a few hours a week consistently. A few hours that I would really like to scale up. The last few days I've been doing some daily or almost daily posts, trying to push out some early, and thus still fluid documentation. Here is the index of my growing documentation series.
While I could really use funding in order to get some more velocity to the project, what I also really could use is a bit of community engagement into the quantum-resistance problem. Other than things like the pandemic, though, quantum-resistance isn't all that urgent a concern. We have years, a fair probability that we maybe might even have to the end of the decade, before utility chains like HIVE will get in trouble with their extensive key-reusage. No urgency, no funding, I get it. And my project isn't a crypto coin you could invest in and make 10x your money if you gamble right, it's a set of libraries that when finished, crypto projects can then use for free and make shitloads with. That won't pay my bills now will it pay the bills of early visionaries funding my time. I get it, this is a herd sell.
So I'm trying something else right now, and I know I'm not good at it, as I'm an infosec/data/software guy, not a finance guy. I've created a new token on hive-engine. The $COINZDENSE token.
I've minted 60,000 COINZDENSE, enough to fund me working on the project for 24 hours a week for about two years if the value of 1 COINZDENSE is at 1 HIVE. I'm currently offering the first 2000 $COINZDENSE for 0.9 HIVE. It is important to note that $COINZDENSE is meant as a project support token for the coinZdense project. It's like a project donation, but you get a token in return. A token that I'll say might show one day that you were a visionary with respect to quantum resistance. Not sure if that will get you something. Maybe it might. Maybe some cool project depending on coinZdense could end up airdropping to you because you own $COINZDENSE.
As I said, apart from funding, allowing me to spend more than the current 6 hours a week on the project, I could really do with some project engagement. People who:
- Join the Quantum Resistance HIVE community and actively post about the broader subject of the post-quantum future for crypto
- Blog on HIVE about coinZdense
- Give meaningful feedback to my technical deep-dive documentation
- Reach out to relevant crypto projects about aligning the specs for the project and the APIs.
- Help me get my project landing page to look less 1998.
- Help me figure out how to go about getting people to buy the support tokens, and how to make an airdrop work to the project's best advantage.
I'm not sure how to do it yet, but I was thinking that maybe I could reserve a few thousand COINZDENSE for an airdrop, and another few for the tasks I really need some help on from individuals.
So here are my questions to all of you guys:
- Should I do an airdrop?
- What can I do to make the airdrop help with QC awareness?
- What can I do to make the airdrop help with project engagement?
- What can I do to make the airdrop help towards increasing my hours with actual funding?
- What can I do with the token to get the right people to help me out with the landing page and the non-technical people stuff?
All input would be tremendously appreciated.