Known Neuron Proposal: Cosmicrafts

Governance NNS proposal discussions
,
1

Proposal Title

Cosmicrafts - Register Known Neuron

Known Neuron ID

3099449518038519101

Known Neuron Name

Cosmicrafts

Known Neuron Description

Cosmicrafts is a gaming franchise built entirely on the Internet Computer, combining fun-first gameplay, functional NFTs, and deflationary tokenomics. At the core of our mission is advancing the adoption and utility of the Internet Computer through gaming.

Cosmicrafts aims to showcase the unique capabilities of the Internet Computer by creating a gaming franchise that integrates governance, ownership, and decentralized economics. By leveraging fully on-chain architecture, Cosmicrafts demonstrates the scalability, transparency, and cost-efficiency of ICP for large-scale applications.

As a known neuron, Cosmicrafts will continue to actively participate in NNS governance, focusing on topics that align with its mission, such as:

  • Subnet Management: Ensuring scalability for gaming applications.
  • Protocol Enhancements: Advocating for features that benefit user-centric applications.
  • Community Growth: Promoting engagement and education within the ICP ecosystem.

The Cosmicrafts team is committed to providing thoughtful feedback on proposals, engaging in constructive dialogue with the community, and voting independently based on our mission and vision.

Proposal Summary

This proposal requests that the NNS governing body approve a Register Known Neuron proposal to establish Cosmicrafts as a known neuron.

Cosmicrafts is a fully operational gaming franchise built entirely on the Internet Computer. Our goal is to empower stakeholders through the Cosmicrafts DAO, enabling decentralized governance and ownership of a franchise-scale gaming ecosystem. By becoming a known neuron, Cosmicrafts will actively contribute to the growth of the Internet Computer by participating in governance decisions that align with its vision of driving innovation, scalability, and adoption of ICP.

The Cosmicrafts DAO will leverage its position as a known neuron to:

  1. Support Growth-Oriented Proposals: Evaluate and support initiatives that drive adoption of the Internet Computer in gaming and user-centric applications.
  2. Engage with the Community: Actively promote the Internet Computer’s unique capabilities through education, collaboration, and partnerships.
  3. Showcase ICP’s Scalability: Demonstrate the feasibility of large-scale, fully on-chain applications through Cosmicrafts’ gaming ecosystem.

This proposal is submitted by Omar, founder of Cosmicrafts. Cosmicrafts has been operational for over 8 years, including its foundational years as a Web2 application before transitioning to the Internet Computer. We believe Cosmicrafts serves as a flagship example of what the Internet Computer can achieve and are excited to contribute to the decentralization and growth of ICP.

Proposer ID

3099449518038519101

3 Likes
2

Welcome to the known neuron club. I’m glad to see Cosmicrafts take this step. This is a well written summary of your proposal and your neuron goals. Thank you. You have my vote. I doubt you will have any trouble getting the support of Synapse and CodeGov as well.

2 Likes
3

Hi @ohsalmeron, this is a technical topic. Are you able to point to any good examples of this active participation?

Am I correct in observing that your proposed neuron has not rejected a proposal in recorded history? Instead this neuron has indiscriminately voted yes on every proposal. Perhaps this is just down to the limited history.

Could you explain the steps that you go through when actively participating in governance?

Could you point to some examples?

4

Thanks, happy to join the known neuron club!

I really appreciate the support, this means a lot.

1 Like
5

Hi @Lorimer, you have some valid concerns, let’s elaborate on that and provide some input.

You are correct to point out that Cosmicrafts neuron has predominantly voted “yes”, mostly because it follows DFINITY’s and the Internet Computer Association, while manually voting on critical updates or proposals that are clearly beneficial for the entire ecosystem or Cosmicrafts particularly.

Here’s the process we currently follow when evaluating proposals:

  1. Subnet Management and Critical Updates:
  • Proposals from DFINITY addressing patches, hotfixes, or protocol improvements are an automatic “yes.” For instance, I personally follow Wednesday’s R&D meetings to stay informed about updates, reports, and new initiatives.
  1. Community Proposals:
  • If a proposal comes from known contributors or projects with a proven track record of delivering value to the Internet Computer ecosystem, we support it.
  1. Cases for Rejection:
  • It’s a valid concern to point out that our neuron hasn’t rejected proposals in the past, I believe we should draw clear lines on proposals that:
    • Lack reasoning, credibility and or technical preparation (e.g., pushing personal agendas, unfeasible timelines for delivering complex projects).
    • Appear unserious or fail to align with the greater good of the ecosystem.

I acknowledge that voting yes on all proposals is a valid concern because it does not fully state what we stand for, and I really wasn’t really considering that when casting votes but its an area to improve.

Thanks for your insights

6

I’m not sure how sensible it is to advertise your neuron as one that votes independently on a technical topic, if that’s ultimately not what your neuron will be doing. It’s great that you follow the goings on in these technical topics though. Have you come across this thread, and the various subnet-specific threads that it links to? There are very detailed reviews posted by CodeGov, and myself (known neuron LORIMER). You may be interested in following D-QUORUM, which follows DFINITY, CodeGov and LORIMER on the subnet management topic. I think this could be more beneficial for the IC than your current automatic “yes” policy :slightly_smiling_face:

1 Like
7

Could you point to any examples of this? If not, would you be willing to clarify/adjust some of these statements to avoid misrepresentation?

8

Honestly, I wasn’t aware of all the work being done around subnet management until now, but it’s great timing for me to learn. With the known neuron and our upcoming SNS launch, it feels like the perfect moment to get this right.

I’m committed to learning and improving, and I appreciate insights like yours. For example, last year, we migrated to a faster subnet, but I didn’t realize we could actively contribute to its maintenance. That’s something I’m excited to explore further.

I’ll admit I’m not an expert on technical topics, so it makes sense to delegate those decisions to people who specialize in them and are putting in the effort. Following D-QUORUM seems like a great next step, I trust in CodeGov and DFINITY. Now that I’ve discovered your neuron (though I’ve seen you around for quite a while), delegating to D-QUORUM for these decisions feels like the way to go.

If you have any advice on how we can align better or things I should focus on, I’m all ears. Thanks again for sharing your insights and for being open to discuss this!

1 Like
9

Absolutely, I’m happy to clarify and ensure there’s no room for misinterpretation.

Here are some examples of how we’ve leveraged our position:

  • Driving ICP Adoption in Gaming: We’ve provided feedback on tools like ICP.NET (essential for Unity and .NET apps), engaged with the BOOM DAO ecosystem, and shared our base code publicly on GitHub. While these efforts aren’t always tied directly to NNS governance, they’ve contributed through forums, social media, and discussions with DFINITY and other developers.
  • Promoting ICP: We consistently tag ICP in everything we do. While it’s drawn some criticism in the past, we’re proud of our ecosystem and the people driving it forward. Even when exploring unconventional ideas, our intent has always been to drive adoption and reach those unfamiliar with or hesitant about blockchain.
  • Showcasing ICP Scalability: Last year, we migrated to a newer, faster subnet with a one-canister architecture. While our user base isn’t large enough to fully demonstrate it yet, the results in speed and responsiveness have been phenomenal.

I hope this helps clarify how we aim to align our actions with our stated mission and I’m open to further refining our messaging if needed.

10

Thanks for clarifying further @ohsalmeron, I’ll vote to adopt.