The repository was created specifically for open-source purposes, with the code sorted, formatted, and thoroughly commented. The version is fully up-to-date, reflecting the production environment as a guarantee.
This reflects our approach to repository management. So no repo is discarded. Meanwhile, ongoing development during the SNS period continues based on our dev repository. Having the repos separated for different uses would be ideal.
Hey @Trils, we also believe this could be a great DAO! Thank you.
Your previous concerns regarding liquidity/DEX/CEX roadmaps were taken very seriously. It’s very much in-line with what we would like to provide the community. Great dApps and an easy-to-use token with loads of utility. After answering your questions I mentioned that the final information regarding liquidity would be out pre-SNS launch. I am still doing so and have decided to create a video where we discuss the CANI roadmap. As you may have seen from our X timeline we have been filming a lot. There is just not enough marketing in this eco. Today we are releasing discussions with musicians and their thoughts on Web3.
We have been prepared, we was not aware of a few things and are now rushing to get them done. This would be due to the fact that the holidays are approaching.
Thank you for the massive support so far! we have had many votes supporting the CANI DAO proposal.
We’ve received feedback from Dfinity regarding our SNS proposal. Unfortunately, the proposal will be rejected due to one key issue: our code was not made 100% open source for the full two weeks, as outlined in the SNS guidelines.
While this was an oversight on our part, we’re pleased to share that everything else in the proposal has successfully passed their review. The only remaining step is to meet the required timeframe to allow the community adequate time to analyze our code.
We are already working to resubmit the proposal shortly, ensuring full compliance with the guidelines this time. We appreciate your patience and continued support as we move closer to bringing the CANI DAO to life.
An additional diagram of CaniSafe simplifies overview, illustrating its four core components:
identity, wallet, computation, and storage -all unified into one service.
It also demonstrates how CaniSafe integrates with Internet Identity, CaniPlay, and CaniStore dApps, while being deployed on the EU subnet.
All details remain the same except we’ve lowered the resolution of our logo (due to recent events) and added capital letters to name (from Cani DAO to CANI DAO) to match the branding. Input spaces in the description to improve readability and the link to the new launch video.
Let’s go! As always any questions feel free to ask here.
I suspect that you’re following a neuron on this topic, and they’ve already rejected (so your neuron rejected in turn). I would check for you, but I can see that your neuron is currently set to private.
I love the concept. I really dislike the name. There are two issue that I have with it: How it’s pronounced makes it feel clunky to say especially for a subject word with more than one syllable that ends with a long “I” sound, it feels unatural to say mid sentence. The other aspect that makes the name awkward to say is that it comes from a more than commonly used colloquial phrase which undermines it’s brand identity.
What I think does stick is the CAN itself. It could stand for Creator Aligned Networking and the overarching network of dApps can be referred to as UniCAN - United Creator Aligned Network with the coin being branded as UCan, instead of asking a question and being unsure, UCan answers the quesiton while still focusing on the individual. UCanSecure, UCanSell, UCanPlay.
Despite having a great concept, it’s important to note when branding makes or breaks a project. There’s a reason why iPhone looks and sounds good while Phonei looks and sounds phoney. Branding is a project’s first impression. It has to be smooth in its delivery, yet deliver it remarkably. Branding is a determinant of success and I hope you can succeed.
Thanks for sharing your thoughts, and I really appreciate the kind words about CANI being a great concept!
The name CANI comes from ICP’s Canisters, which we use to store data in the ecosystem. It’s a key part of the project’s uniqueness and ties directly to the technology we’re building on.
While the CANI name already has some traction within our community, I do agree branding plays a huge role, and I’ll definitely take your feedback on board as we move forward.