How-we-make-money

Initially, we do not have full-time staff, meaning we don’t operate like a traditional company. Instead, we function more like a decentralized DAO. We have no concept of salary costs or recurring expenses such as office rent or payroll. Our revenue comes from the sale of collections purchased by early participants, which is staked on various public blockchains to generate profits. The majority of this revenue is contributed to the prize pool, ensuring that our community participants can share in the product’s growth. The only fixed costs are server expenses and development maintenance.

How We Develop New Features

When a proposal is approved by the community and confirmed as a highly desired feature, we tap into our network of talented developers, who are also our loyal users. These developers can deliver the feature within an estimated timeline, following a high-quality and robust development process. This one-time development cost model ensures that we can sustain operations and updates in the long term, even during market fluctuations or transitions between bull and bear cycles.

Principles for Treating Users

The most important thing is to remain focused on building the best product.

• We don’t care about missing out on money-making opportunities If adhering to our principles means passing up certain opportunities, we will do so. We can afford to make this choice because we have strong trust with our users, and we must protect that trust.

• We don’t sign delivery contracts In particular, we avoid contracts that require delivering a product by a specific date. From a principled standpoint, if a single client forces us to develop something under a tight deadline, it could compromise the experience for the majority of our users. We aim for long-term sustainability.

• We will build features for specific customers, as long as we’re confident they won’t be the only users Slightly adjusting the roadmap can make sense, but adding features that only one user will use is not reasonable.

• Customers need to try Learnverse before expecting us to make changes We value customer feedback, but we don’t appreciate a list of demands from people who haven’t used our product.