Starting from zero is hard.
I forgot how hard it is to build a community from scratch.
But I am so stoked to build a new form of community, a Decentralized Autonomous Community!
With the soft launch at the EOS World Expo, I was able to have several meaningful conversations to create a concrete vision on how to approach the building of the project.
One thing that was clear from the inception of the project: a map of the EOS ecosystem is a staple of the EOS community and as such EOSmap should belong to the EOS community.
So I am back to what I love to do, building communities.
With Luke from eosDAC, we talked about the benefits of a Decentralized Autonomous Community (DAC) and how to build a DAC using their opensource DAC Factory software. It became clear that the first step of EOSmap is to build a community of contributors and supporters to collectively create and maintain the inventory of the ecosystem. Yet, it does not make sense to build a DAC when there is no one to take care of it, yet. Building a DAC also requires some development including issuing a token, work with lawyers to clear out any regulatory issues, and write a DAC convention with early community members. All this takes time, and as a strong believer of agility, the project needs first to prove it can grow a community rather than building the tools and after starting working as a community.
Another set of meaningful conversations was with Laurent, Mathieu and Josh from dfuse.io. dfuse offers access to all the blockchain data we need via their API. They will also support our developers when we will engage into developing the first product. The dfuse team helped us to understand what data we need to collect from contributors to have a relevant set of data about each dApp.
Last but not least, we are talking with Everipedia on how to leverage their network of editors to collect quickly the information we are missing about already identified dApps. Dave (Head of Partnerships), Navin (Editorial Director) and the whole leadership team at Everipedia are continuously showing support of the EOSmap project.
With all the support we are receiving, I believe it makes sense to shoot for the moon and provide a first visualization map of the current state of the EOS dApp ecosystem for EOS 1-year anniversary, ie May 31st. It is ambitious but achievable.
How can you help?
We have published a set of tools to work all together toward that ambitious goal:
- a submission form for contributors to submit information about the dApps they know;
- a Trello board for contributors to see how they can contribute in many other ways;
I also personally spend a lot of time reaching out to existing and new supporters so they help spread the world and get many contributions, as well to founders of dApps built on EOSIO.
I count on your help to spread the word on your own channels (Telegram, Twitter, Discord...) and get your audience to help building the inventory of all dApps built on EOSIO for the 1-year anniversary.