Distribute your tokens, get on-demand analytics and community growth.

Apply here to partner with MetricsDAO. We’ve got 3 spots left for June, apply until the end of April to activate the analytics machine!

Analytics, Exposure & User Acquisition for DAOs

By partnering with MetricsDAO, you’ll get access to top-tier analysts who will create the analytics and tools that your community is asking for. The fact that outputs are produced in near-real time means that they stay relevant and get widely shared on social & by media, which promotes your on-chain activity and drives awareness for your project.

At the same time analysts who’ve now spent hours digging into your data and earned your native token are more likely to HODL than if they received it via an airdrop, because they now see your project’s value and potential.

Existing Partners & Key Stats

102 analysts, created 491 dashboards and won a total of 9 grand prizes!

MetricsDAO has come up with compelling questions and created insights for:

• OlympusDAO — 12 submissions / 3 grand prize winners in the first program
• Harmony — 142 submissions / 6 grand prize winners
• Uniswap — 288 submissions / 5 grand prize candidates

View more stats: https://tinyurl.com/metricsdao-analytics

You can see what it takes to submit a winning submission in this article by community member @rplust here.

“MetricsDAO has been a pleasure to work with. We were already impressed with the team and the quality of output, so a further collaboration was a no-brainer. The Harmony community now has access to extremely valuable insights to understand critical metrics.” ~Giv Parvaneh, Senior Blockchain Engineer from Harmony.

Who should apply?

Good partners have these characteristics:

• Data is highly available, ideally from multiple providers (Dune, CovalentHQ, Flipside)
• The MetricsDAO community is excited about the protocol/ecosystem
• The grant size is at least five-digits when denominated in USD
• A huge plus is some form of synergy with existing partners

MetricsDAO is a community of curious, bright and fun people, who are always looking for the next challenge. If you are unsure whether to apply or if you could profit from us, join our Discord and talk to @raphbaph or @danner.eth. We’re happy to show you around.

We’ve got 3 spots left for June, apply until the end of April to partner with MetricsDAO.

Turn on the analytics machine — Partner with MetricsDAO was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our first workshop was by our esteemed member Hildobby, who gave us an introduction into using Dune Analytics to extract information on NFTs and present them in a snazzy dashboard.

If this peeks your interest you can watch the recorded workshop here: https://youtu.be/4aA5chHaSiU

We had a pre- and post-workshop survey. The pre-workshop survey focused on timing of the workshop and attracted significantly more participation than the one after the workshop, where only a single member took part.

Here are the results: Metrics DAO — Workshop 1 Survey (google.com)

We learned that a majority of the 11 survey participants had previous experience with blockchain technology and NFTs but few had previous Data Analysis experience and even fewer had used Dune Analytics before. This was expected since the workshop was introductory.

The workshop was well received overall with some time-zone issues reported. Finding a time that works for everyone becomes 3D chess with an audience that is spread out across the whole globe. Someone always gets the graveyard shift, and good practice demands rotating event times to escape time-zone-centrism. That being said, all the survey participants expressing a time preference picked evening on UTC.

The workshop hit the right tone, thanks Hildobby, and was characterised as Intermediate by 55% and as Beginner by 45%. An overwhelming majority (90%) wants to see additional workshops and deeper focus on NFTs in the future.

Only 30% felt ready to join the mentors circle and coach other members on their analytics journey.

The workshop’s recording also marked the beginning of the MetricsDAO YouTube channel, which you can subscribe to here:

MetricsDAO — YouTube

If you haven’t already please join our Discord and follow us on Twitter.

Workshop 1: Using Dune Analytics for NFTs with Hildobby was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

As a data-driven organization, MetricsDAO strives to learn from best practices that other DAOs are implementing. One of our MARCOM team, rplust, talks about his experiences over at Raid Guild (check them out!), with additional commentary in italics.

Overview

Raid Guild (RG) is a Service DAO akin to a project management and dev shop for web3 projects. Their services span from project consultation and one-off product feature developments, to full-on project life cycle management.

The Cohort Approach

I was able to join Raid Guild’s season 3 cohort back in November 2021 by way of an online application and went through season 3 until its “soft close” back in December 2021. I mention soft close because it really depends on the project you will be working on and when it will finish.

Progression

Being part of a Raid Guild cohort allows one to (1) contribute and work on RG’s projects, (2) help out with the DAO’s operations, and (3) become a full member at the end since everyone starts as an “apprentice.” At the end of a season, an apprentice might become a member, a non-member that continuously contributes to Raid Guild, or just hang out in Discord and take part in projects later on.

There are certain milestones per season broken down into “episodes”. Here are a few examples:

1. Start

• Email acceptance and being granted access to the cohort channels on the Raid Guild Discord

2. Episode 0

• A call with the whole cohort and a Raid Guild member who will serve as the cohorts onboarding guide throughout the season.
• This is mostly an intro to RG, DAOs in general, and an overview on how the season is planned out.
• Everyone does a quick intro of themselves.

3. Episode 1

• Raid Guild “work roles” are introduced here and you will be able to choose your role/s. I picked Angry Dwarf (Treasury), Druid (Data Analyst/Scientist), and Hunter (BizDev) — very in theme.
• The concept of “Raids” are discussed which is basically what RG calls its projects, specifically client-facing projects.
• Here everyone gets to pick what task/s and/or project/s they want to take part in for the season.
• Most projects are compensated especially if they are client projects. Apprentices are also encouraged to submit compensation proposals on projects that did not have planned compensations at the start if they deem it deserving based on complexity and significance.

4. Episode 2

• Mostly updates on what you’ve been working on since the previous episode.
• In this episode, a DAO specific to the cohort is built and everyone learns how to pledge wxDAI (sponsored by RG) and become a member. It’s a good way for people to really get hands-on experience.

5. Episode 3

• Again, updates from the last episode.
• An in-depth overview of the DAOhaus platform, a DAO operations tool.

6. Project Demo Day

• Concluded projects demo what they did through a presentation or pitch.
• On-going projects are encouraged to present their progress and give timelines on when they aim to finish. Asking for help and resources is encouraged.

7. Finish

• At this point, the season “concludes” but is really dependent on the project/s being worked on.
• Cohort members are encouraged to keep going on raids and contribute to Raid Guild.
• A lot of proposals to become full members happen here as well.

Episodes happen every week or week and a half. Schedules are released ahead of time.

All throughout, other Raid Guild members try to involve themselves in the season by way of guidance, membership, and even recruitment into the live projects. There are also plenty of opportunities for cohort apprentices that stand out to be championed by members of the guild to become a full member.

In-Between Times

In between the episodes, there are different workshops conducted by various functions in Raid Guild (marketing workshops, product development guides, smart contract code review/contribution calls, etc).

I myself just recently finished up my main project with Raid Guild back in early February 2022. I was able to work with fellow cohort apprentices, a couple of which are now full RG members. I also worked with RG members and an external client for the project.

Improvements

The cohort season system provides the guild with a steady stream of project contributors and potential members. They gain a significant skills and knowledge base per cohort they onboard who can help further develop the DAO and even come up with new projects and products. Raid Guild continuously strives to improve this system and make it even better for future seasons.

Summary

Several aspects of the Raid Guild Seasonal model are broadly applicable to other organizations, including MetricsDAO:

1. Seasons are based on the length of projects, rather than on hard deadlines
2. Members start off in an “apprentice” role and progress to full contributor status by the end of the season, based on their accomplishments. Alternatively, members can gracefully off-ramp or dial down their contributions at season’s end if they prefer
3. Seasonal milestones help keep the entire DAO focused and enable celebrating wins
4. In-between times (“pre-season”, “off-season”) are useful to get a breather, review learnings from prior seasons, and recalibrate prior to the next season’s launch

Stay tuned for additional pieces on how MetricsDAO intends to design and implement our own Seasonal model! Join our Discord and/or follow us on Twitter.

Credits to GJ Flannery for helping structure this article and for writing the introduction and the summary sections.

Seasoning MetricsDAO, Part 1 was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

Firstly, some bounty questions around the protocol or blockchain involved are left unanswered given the time constraints and the difficulty level. Another is that analysts are not able to first familiarize themselves with the topic of concern and strategically dive deeper into the bounties which leads to submissions that can be much improved. Lastly, due again to not having enough time, analysts are not able to complete several bounty questions which decreases their potential earnings from bounty programs.

Our hypothesis is that

1. If bounty questions are released based on difficulty level with easier ones going out first, more questions around the protocol or blockchain can be answered. This is because analysts can have a chance to first familiarize themselves with the protocol and tackle complex questions later on.
2. If the volume of questions are controlled with a staggered release, analysts will have enough time to think through their solutions and generate higher quality submissions.
3. If analysts are given enough time, they will be able to tackle more bounty questions and maximize their potential earnings.

The solution we have come up with to test out our hypotheses is to do tiered challenges for bounties. This is wherein bounty questions are released in a series of weeks at an increasing difficulty level. The first tier of questions is for analysts to familiarize themselves with the basics of the particular topic, where that might be about a particular protocol or blockchain. The next tier is for diving deeper into more nuanced aspects of the topic. Finally, the last tier is for solving harder, more complex questions not only regarding the protocol or related blockchain but possibly the surrounding ecosystem as well.

We are currently implementing this as an experiment with our Convex Bounty Program, although due to time constraints, we were not able to explicitly classify the questions according to difficulty level.

We started with the release of the first tier last February 7, 2022, giving participants until the Friday of that week (February 11, 2022) to submit their analyses. Since then, we have finished releasing the subsequent tiers on a weekly basis at a rate of five questions per week. Currently, our team of graders are in the middle of assessing submissions for each tier and we will soon announce the complete results.

The results of this experiment are not yet complete but so far:

• We received 48 submissions which is 4x times more than our last bounty program.
• Comparing averages, this program generated three submissions per bounty question compared to our last wherein the average was one submission per bounty.
• 14 out of the 15 bounty questions had a submission which is another improvement over our last program that only had 70% of the questions answered.
• Two questions were able to get seven submissions each.

Stay tuned for the complete results of his experiment after we conclude the Convex Bounty program by joining our Discord and following us on Twitter. We would love to hear your feedback on our bounty programs as well.

Experiment #6: Tiered Challenges for Convex Bounties was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

On a sunny February morning in Vienna, Austria, I hopped on a Discord voice call with Chuxin, located 10 timezones away, to talk about data curation, what makes NEAR special and her journey to become a pod leader and data curator for MetricsDAO.

Q: Hi Chuxin, thanks for taking the time to talk with me. Let me ask you a couple of questions regarding the ongoing curation of NEAR protocol blockchain data. What makes NEAR different from say Ethereum, or from Harmony, where you also led the curation efforts for MetricsDAO?

Chuxin: NEAR is another Layer 1 blockchain protocol that has been growing fast, so that was exciting. It uses a Proof-of-Stake consensus mechanism and sharding design to improve scalability. In terms of data curation, because of this design, data such as chunks, actions etc. are what we didn’t see in that way in Harmony or Ethereum.

Q: Do you now have to parse multiple shards? Or is there a canonical chain that’s a single source of truth in the end?

C: At the end the fundamental structure is a single chain of blocks. However, because of the sharding design, consensus nodes only need to validate parts of the history, in comparison to the non-sharded chains where all consensus nodes need to agree on the state of the entire chain. So for NEAR, all transactions are aggregated and split into chunks to be validated. That’s different from what we saw with Harmony.

Q: How many people are working on data curation for NEAR at the moment?

C: We have four to five active contributors at this stage. We’re getting started with the main effort now. Before we were researching in order to come to a mutual understanding of what makes up the NEAR blockchain, and how we wanted to design the table schema to be useful for end users. Currently we have tables for NEAR blocks, actions and a staging table for NEAR transactions. You can see where we are here in our GitHub repo:

GitHub — MetricsDAO/near_dbt

Q: As far as I know Ethereum smart contracts can also emit events, how is that different in NEAR?

C: Yeah, that’s kind of similar, but transactions in NEAR are a list of actions to be performed on the receiver side with some additional information such as block hash, signer and receiver ids.

Q: Which database are you using?

C: We pull data from the NEAR blockchain using chainwalker, which ingests all the data in the raw, JSON format. As curators we model the data into blocks, transactions and actions and put them into Snowflake tables.

Q: So this brings us to the heart of the process. What does data curation actually entail here?

C: First of all we come up with the core tables we need to curate into, which is usually quite similar to other chains. But in the raw data there’s going to be duplicates, which we need to clean up.

Then we expand and decode the JSON keys into columns, or into separate tables if it is merited. That was the case for actions in NEAR.

Q: A bit about yourself, do you have a blockchain background? Or are you a data scientist by profession?

C: I’m from the analytics space and work for a Web2 tech co, and have been doing data analysis and data science for the last three and a half years. I got started in the crypto space in the middle of 2021 with a program by Andrew Hong called OurNetwork Learn, and that is how I got started.

I became involved in MetricsDAO via Drake and actually was one of the first members there. I got to understand blockchain data better, and am familiar with Ethereum now. There’s so many different chains, and I was really interested in going deeper.

When the Harmony curation project started I raised my hand and thought to myself: I have experience with Snowflake, and with DBT, and these other tools, but no Harmony experience. MetricsDAO allowed me to really get my hands dirty with the multichain data.

This project progressed very well, with five to six people contributing actively. The bounties are almost up, and we’re happy with the output. We will also be able to use the curated data going forward. And from there on I naturally progressed into NEAR curation.

Q: Was it easy to find enough contributors on MetricsDAO?

C: Some people are interested in contributing to the curation itself, others are tangentially interested but have different aims, which is fine too.

We would love to bring in more curators to speed the process up and improve data quality. I’m going to give a workshop on data curation on March 11th, 2022, for anyone interested in getting into blockchain data curation.

https://discord.com/events/902943676685230100/940419232074694656

And I hope we can make people more comfortable with the tech stack we use and onboard more curators.

Q: Tell me about the tech stack you use, please.

C: We use Snowflake as a database, and DBT (DataBuildTool) for orchestration, and collaborate over GitHub, and we use Docker for the environment. And that’s pretty much it.

Q: Any other links you would like to share?

C: There’s a Gitbook section for data curators, quite short but would be informative
Data Curator Onboarding — MetricsDAO (gitbook.io)

Then anyone using Flipside can build queries on the curated Harmony data, which is exciting.

Q: Thanks for the fascinating insights, highly recommend anyone interested into data curation to join the workshop. And of course join MetricsDAO on the Discord. Thanks Chuxin, have a great evening.

MetricsDAO provides a 6 step process for ​​Organized, On-Demand Analytics Delivery, or as we like to call it, OODAD.

Follow us on Twitter
Join our Discord

Insights from curating NEAR data — Chuxin.eth was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

Submissions that get decent scores in these criteria are qualified to receive bounty payouts. Those that get a perfect score are then entitled to the grand prize. Let’s get started on a breakdown of these criteria.

Accuracy & Completeness

Given that bounties aim to firstly answer questions, it is important that a submission answers all the questions related to the bounty. The methodology also needs to be clear and logical in order to explain the concepts involved.

Insights

A good analysis should have a narrative weaving everything together and this needs to be clear in the submission. Readers should be able to gain key insights and new information which could inform their decision-making later on related to the subject matter.

Visualizations

Perhaps the centerpiece of any bounty submissions is the visualizations. It is through these visualizations that one can best surface the insights that were generated from the analysis. However, it is not enough to just have visualizations. The best submissions are able to discern which types of charts to use that help fully explain the analysis and provide definitive insights.

Definitions

Lastly, data sources, terminologies, and metrics used should be clear in the submission. Always give credit to the sources you used. It is easy to fall into the trap of assuming that the reader knows what you know. However, more often than not, this is not the case, especially given that most bounties try to answer questions about new protocols and datasets that were previously undiscovered. Defining these terms in the submission adds to the overall insight generated by the submission.

Best Practices

Going Above and Beyond

Some bounty questions are indeed simple enough to be answered by just one graph or table. Technically that would be a complete submission. However, nothing is stopping you from exploring other related questions to enrich the overall insights that readers can get from the submission. This significantly increases the chances of winning the grand prize.

Guide the Reader

It is important that the readers know the message a bounty submission is trying to convey. Having a good dashboard title is a good way to achieve this. Perhaps even better is to have your key takeaways be mentioned up front so the reader knows what to expect.

Context is Key

Related to the previous point is providing context in your submission. While having a long narrative is unnecessary, sometimes having a short description of the project, protocol or subject matter related to the bounty can go a long way. This additional context helps readers glean more insights from the submission.

Grand Prize Bounty Winner Examples

Kakamora offers a comprehensive look at the staking user growth in Olympus

shreyash goes into Anchor repayments and borrower behavior

Review Timeline

Bounty programs are launched on a weekly basis wherein submissions are open for a week. After this, another week is given for a comprehensive review of the submissions. The announcement of winners and payouts are done shortly after.

For example, if a bounty program is launched on a Friday (T), submissions will be open until the following Friday (T+7). MetricsDAO aims to complete the review process by the following Friday (T+14) and announce winners on the following Monday (T+17).

—

If you’re interested in learning more about what makes great bounties or you’re ready to participate and submit your own, check out the MetricsDAO Discord and/or follow us on Twitter for the latest bounty news and programs.

Bounty Review Process Overview was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

MetricsDAO launched in 2021 to operationalize, automate and scale the creation of on-chain analytics for crypto projects. In the past three months we’ve seen an unaffiliated group of people from all over the world start to organize around this mission, and grow to nearly 1,500 contributors. Projects such as Harmony, OlympusDAO, and Uniswap have already approved grants to tap into the DAO’s community for the analytics they need.

Getting here this quickly took more than a vision and a Discord. Actually growing, organizing, and enabling the MetricsDAO community to drive outcomes could not have happened this quickly without Flipside Crypto’s support, via a process we call “excubation”.

In this article we aim to shed light on what the bootstrapping, or “excubating” process has looked like so far, how it’s working, and how specific challenges could cause it to fail. We don’t claim to have all of the answers — in fact we’re still experimenting with the right structures and incentives to move MetricsDAO towards further decentralization and automation.

If you have questions, comments, or ideas after reading this, please message us in Discord! We’d love to discuss.

Excubation

When the parts are worth more than the sum.

Flipside Crypto’s mission is to help blockchain projects reach their full potential. At the core of every product is a robust data analytics platform that labels and curates blockchain data. Around it are many other moving pieces focused on bounties, governance, marketing, education, international growth, and scaling and automation. Together, these parts allow Flipside to run community enabled analytics that drive user growth and retention for partner projects.

Flipside already produces outputs by working directly with its community of analysts. This creates a “porous” organization, in which community talent and internal resources blend together to drive analytical outcomes.

But what if we made the organization even more “porous”? By open sourcing more than just code bases, spaces are created that empower more diverse lines of thinking. Individuals become more than participants in the system — they are given the power to become contributors who shape the system and its partnerships for themselves and others.

This free-flowing model is what MetricsDAO is all about.

Instead of incubating a team to start building a project, Flipside excubated a prototype that needed a team. Part of this process involved intellectual property: a 6 step process that would turn community-sourced questions into actionable challenges that DAO participants could subsequently solve. The framework came in part from Flipside’s experience with launching bounties, but is by no means in its final form. It is meant to provide enough incentive and structure to stimulate learning and innovation from a decentralized group of people.

Excubating MetricsDAO also meant providing talent. Five Flipside team members are devoting significant time to MetricsDAO, enabling them to provide energy and operational support while community members on-ramp to become valued contributors and Core team members.

Last but not least, Flipside provided capital. The startup contributed 100,000 USDC to the MetricsDAO treasury to go towards more self-funded experiments and to align incentives as needed.

Where Excubation Works

Excubating a DAO means providing some leadership, capital and structure that together can organize a larger decentralized network of people around a common goal.

The MetricsDAO community has already self-organized into working groups, or “pods”, each with a leader and a specific goal. It’s fascinating to see some of these pods form entirely without the leadership of Flipside, bringing in new ideas and people to drive better outcomes. Excubation works by allowing decentralization to happen from the bottom-up. It provides sufficient structure and resources for the organization to grow while still having some missing pieces at launch.

As experiments validate hypotheses, processes can be automated which means there’s less need for human touch, and less vulnerability to human error. A more resilient system starts to form, which allows for further decentralization.

This reinforcing loop creates space for more equity holders to come in and impact direction, provide diverse thoughts and drive innovation all while building a more trustless system.

How Excubation Can Fail

There are clear risks with excubating a process. For one, you may struggle to source the proper contributors. DAO contributors are usually drawn to a mission which makes them passionate and driven, but they’re also not yet being compensated for their work. As a result, it may be slower to attract talent and/or contributors may not be as available as you’d expect a traditional employee to be.

Additionally, while excubation gives full-time employees wide latitude to invest their time and energy in a project, some employees are expected to wear two hats. The biggest risk with excubating a DAO, then, is realizing that you’ve pushed people and capital to their limits and growth is stagnating.

—

MetricsDAO has a long way to go before we can truly call it decentralized and autonomous, but the way Flipside has been bootstrapping the DAO — by providing structure that allows it to grow but not being restrictive or controlling in that growth — is clearly resonating with people. The fact that MetricsDAO is open-sourcing more than just repositories and actually giving the community a say in how its operating process should be structured, means that anyone can come in and really have an impact.

We believe that on its own MetricsDAO can grow to become something more special than what the analytics process would look like in house at a traditional org.

We believe that a community-owned and run organization can blossom into something spectacular.

Join our community and help make this excubation process a success!

What Bootstrapping a DAO Looks Like was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

MetricsDAO member Kakamora (Discord: kakamora#2549) created a beautiful dashboard to illustrate staking user growth. We talked about his process and how it all came together.

Q: How long did it take for you to create your dashboard?

Kakamora (K): 8 hours or so starting from analysis to completing the bounty.

Q: What tools from Flipside, Dune and MetricsDAO did you use?

K: I used Velocity from Flipside and Zoho Analytics for the charts.

Q: Were you part of the data curation team?

K: No, I was not part of that process.

Q: Are you a member of Olympus?

K:No, I’m not.

Q: Thanks for giving us a peek behind the blinders!

Other submissions to MetricDAO’s first OlympusDAO pod: https://app.flipsidecrypto.com/dashboard/olympus-pro-alchemix-dI4zTD
https://app.flipsidecrypto.com/dashboard/olympus-staking-users-growth-d2yNUU

CLOSE FOLLOWERS ($175 prize) — — these were all very close in score to #3 and to each other MetricsDAO awarded them an additional $75 apiece

https://dune.xyz/KARTOD/Olympus-in-the-second-half-of-2021
https://app.flipsidecrypto.com/dashboard/1-olympus-pool-together-6TvJFH
https://app.flipsidecrypto.com/dashboard/ohm-cyclicality-SPXLAP

Thanks to the quality of submissions, the next OlympusDAO pod will be financed by a grant. MetricsDAO is happy to showcase the power of community enabled analytics.

MetricsDAO provides a 6 step process for ​​Organized, On-Demand Analytics Delivery, or as we like to call it, OODAD.

Follow us on Twitter
Join our Discord

OlympusDAO winners roundup — Kakamora was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

Here’s a link to his amazing dashboard: Defi Kingdoms Report Generator — Anton Yip (dfk-report.vercel.app). And link to the bounty: Defi Kingdoms (harmony.one)

Q: Hi Anton! Thanks for taking the time to chat and congrats to your price. You chose Node.js to build the dashboard and a backend to query the Snowflake DB. Wow! Why Node?

Ant: I wasn’t very familiar with Node before this project, but it seemed the choice that would give me the quickest results. I don’t know Python or R well enough and the learning curve seemed steeper.

Q: Amazing! Did you do all the work yourself? Or did other MetricsDAO members pitch in?

Ant: I did it all by myself, within three weeks. I have a regular job, so this was a side project. I was also involved in the data curation of Harmony One for MetricsDAO. So I already knew the database layout.

Q: What’s your skill set? I see you developed a backend. Was that something that Snowflake offered?
Ant: I’m a software engineer, so I’m familiar with many languages and can easily learn new ones. Snowflake didn’t offer the backend I wanted, but Node made it really easy to develop the APIs I needed.

Q: The dashboard is using Vercel, can you tell why you chose them?

Ant: Vercel makes spinning up applications like my dashboard a lot faster and easier. I’m very happy with them. I used them before and they are really good for rapid prototyping.

Q: Do you think DeFiKingdom choosing Harmony was a good choice?

Ant: I think Polygon would probably have been a better choice, but they chose Harmony, and in the end the problems there caught up with the game. Like blockchain spamming, for instance.

Q: So how much did you win?

Ant: The price is 600 JEWEL, which got paid out Feb 1st. I’m also working on another DFK dashboard for MetricsDAO at the moment. Due to the Chinese new year, I won’t have as much time, so I will submit what I can get to by the deadline.

Q: Thanks a lot for your time and looking forward to seeing you on MetricsDAO! If people want to follow you, where can they find you?

Ant: All the best! People can find me in the MetricsDAO Discord. My Discord username is Ant#8260.

Anton Yip makes 5th place on DeFi Kingdom Transaction Tracker Bounty was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.

Set Up

MetricsDAO provides a 6 step process for ​​Organized, On-Demand Analytics Delivery, or as we like to call it, OODAD.

We ran a workshop that we announced on Twitter and the MetricsDAO Discord server and chose a moderator to facilitate the session.

The session itself had a twenty-minute brainstorming session. Participants could submit as many questions as possible. They could come with questions prepared or make them up on the spot.

After the brainstorming session, there was a short period for grouping questions and seeing if some themes emerged.

Why did we do it that way?

1. We didn’t generate enough questions with the question collection tool and wanted to try something different.
2. Participants could just show up without any prerequisites, and we wanted to see what themes were emerging.

Outcome

We generated more than 50 questions. While there was some similarity, more than enough for the program emerged.

We were happy with the results, and it was a lot of fun!

What will we do better next time?

We want to allocate more time to share and discuss at the end of the session.

Our workshop template was a completely blank slate. We want to insert some seed topics or themes in the future. For Convex, it could have been Curve wars or tokenomics.

About MetricsDAO

MetricsDAO is uniting the best analytical minds in the space to build the future of crypto analytics.

Follow us on Twitter
Join our Discord

Experiment #5: Generating copious questions for the Convex Pod was originally published in MetricsDAO on Medium, where people are continuing the conversation by highlighting and responding to this story.