Decentralized Voice Program Cohort 3 - Tiny/Mimir

Governance
1

Hello everyone, I am Tiny, the product manager from the Mimir team. I would like to join the Decentralized Voice Program to participate in the governance and development of the Polkadot ecosystem. Decentralized Voices Program. Web3 Foundation has created the… | by Web3 Foundation Team | Web3 Foundation | Medium

Currently, I am the product manager of Mimir, an asset management product. Our team aims to provide more diverse account structures and more convenient transaction features by making many of Substrate’s Pallets more user-friendly. I have more than 5 years experience in Polkadot ecosystem.

Polkadot Address: 14pa3BAYZLPvZfRDjWEfZXZWBVU45E67HUQEUxNCrdXGoata

Kusama Address: GPtZAFMKv9NsnE9YZziKL6MUTkeBbM9fMWViKeonLiFNJN7

The Mimir team was established during the 2023 Asia Summer Hackathon, where we won first prize, and we also won second prize in the Winter Hackathon. As we began planning to submit proposals to the treasury, we gained a deeper understanding of OpenGov. We were very pleased that the treasury recognized our previous work and approved our proposal; therefore, I also hope to join the governance process to help more promising projects that can benefit the ecosystem.

Here is my voting logic, and you can view my past voting history at: Subsquare | Polkadot governance platform

I will vote according to the following logic:

“Aye” Proposal: From a product manager’s perspective, Polkadot prefers to build a robust underlying technical architecture, while productization is left to the community through the treasury. Therefore, I will support projects that meet the following criteria:

  1. Projects that actively follow Polkadot’s latest features, such as Coretime and the upcoming JAM. The ecosystem needs these projects to be available to users as soon as the underlying technology is developed.

  2. Projects that fill gaps in the ecosystem. Many project types that are mature in other ecosystems are still lacking in Polkadot. These projects can help us broaden the market.

  3. Projects that leverage Polkadot’s strengths, such as cross-chain capabilities and governance, to enhance user experience.

To prevent supporting ineffective teams, these projects need to meet the following basic conditions:

  1. Verifiable work, at least a basic design demo or an existing online product, with retroactive funding being the best-case scenario. From my experience, taking a project from concept to implementation is challenging, and there is a significant gap between an idea and its realization. Therefore, to ensure effective use of funds, some part of the workload needs to be verifiable.

  2. If there is not enough verifiable workload, the team should have a proven track record, such as successful cases within the Polkadot ecosystem or related fields, including past work experience and hackathon achievements.

  3. Reasonable funding needs with a clear and reliable budget.

Since marketing is not my expertise. Therefore, I will be more cautious with marketing-related proposals. I will vote for the following marketing activities:

  1. Official or semi-official developer events, such as Decoded, hackathons, and PBA, both global and regional. From my own participation experience, these events are crucial for ecosystem development, and we look forward to more projects showcasing themselves through these channels.

“Nay” Proposal: The opposite of the “Aye” Proposal. I will reject proposals based on the following priorities:

  1. Reasonable amount: Requests for funding that are excessively high and significantly exceed the expected cost of the project.

  2. Reasonable proposition: Projects with unfeasible or low-demand propositions within the ecosystem, such as another Polkadot cross-chain bridge.

  3. Reasonable developers: In cases where there is no verifiable product, if developers disclose too little information and their credibility cannot be verified.

Additionally, I will help submit negative votes for incorrect proposals to avoid any adverse events.

“Abstain” Proposal: Conflicts of Interest:

  1. Since Mimir is a multisig product, to avoid conflicts of interest, I will abstain from voting on proposals related to multisig products, such as Polkasafe, Multix, and Signet.

Welcome everyone’s feedback.

2 Likes