When TokenJenny was started, I had no intention of turning it into a DAO. It was my work, wrote by myself (for the most part), hosted by my VPS, being paid by my credit card. However, simply put: the communities involvement is important. Not just to keep the life of a project stirring with activity, but to steer that project in the right direction, by unbiased opinions and with a far higher combined IQ than a sole owner.
So, we're as of this point a DAO. I write that with excitement and anxiety. I've put a LOT of time, sleepless nights, energy drinks and 4AM handfuls of Doritos (I bet that gives off quite the mental image) towards creating TokenJenny - and I'm proud of it. But, I'm also certain the community would be more apt to see the bigger picture in steering the ship, as I hardly see past the bags under my eyes.
With that being said, there are a few stipulations to this change.
Our code will remain closed source. Not forever, but until we can afford to have it audited. I do not want to run the risk of having our contracts exploited because "open source is the in thing." It is. But, while no one can guarantee it'll ever be 100% tamper-proof, we can have some peace of mind prior to publicizing the code.
We will complete the milestones of Harmony's Grant/Bounty, prior to moving on to other features. They were beyond kind enough to have faith in us, I have no intentions of not holding up my end of the bargain. With that, we're not far off. With the governance portion of TokenJenny complete, all that remains are premium tokens.
Decisions made prior to converting to a DAO will remain in place, unless the original team (myself, SR, aerias & coach) decides otherwise. We're not that stubborn, if a case can be made that they are not in the best interest of the project or necessary at this time or whatever, we're happy to pivot.
The treasury will remain private. Once we've built a repertoire of trust, we can consider moving it over to a multi-sig mechanism. However, until then, I'll continue what I've been doing and only using it when necessary (competitions, CM/Dev pay, etc...).
Similar to the treasury, TokenJenny runs on a permissions contract where a wallet from each seat is added. Until we've built that foundation where we can trust that things won't be mis-used, the wallets for these seats won't be added. Once that foundation is there, we can add it no problem.
With that, let's see where this takes us. Thanks for reading and I look forward to everyone's involvement.
