2020-03-04-2020-Blockchain-Developer-Survey.md
This commit is contained in:
Graham McBain
parent
19b96216a8
commit
d59999f552
|
|
@ -0,0 +1,110 @@
|
|||
|
||||
## Abstract
|
||||
The blockchain developer mindset is not well understood. This survey initiative was created in an effort to shed light on the current sentiment in the blockchain developer community. The echo chamber of crypto Twitter doesn’t allow for thoughtful discussion, and we felt there was a need for a survey of the community outside of that forum. Though our sample size is small we are happy with the input we received from developers around the world.
|
||||
|
||||
In addition to the survey form we conducted interviews on Zoom to ask more detailed questions. This community is truly global in scope. What is most apparent from this survey is that the world of blockchain development is just getting started, and there is more we can do to make it accessible to those looking to invest their time in learning about this exciting technology.
|
||||
|
||||
The main takeaways of this study are:
|
||||
Popular sentiment on Crypto Twitter does not represent blockchain developer attitudes
|
||||
There is general interest in developing across chains, and across public/enterprise blockchain platforms
|
||||
Developers care about decentralization, but don’t believe it is something the general public cares about at all
|
||||
|
||||
## Methodology
|
||||
For this inaugural survey we focused on the sentiments of developers in the Ethereum community to access the significant volume of work that occurs in Ethereum. Next year we will expand the sample to a much broader swath of the blockchain community.
|
||||
|
||||
We focused on three key areas of questioning in this survey:
|
||||
- Technology
|
||||
- Sentiment
|
||||
- Motivation
|
||||
|
||||
Within these sections we hoped to understand better how developers are spending their time and what drives them to be a part of this industry. We used a qualitative, open-ended question method in order to generate a broad range of ideas. In future studies we will use this data to develop more precise attitude and behavior measures.
|
||||
|
||||
## Chains
|
||||
Of all respondents surveyed, a little under fifty five percent identified as exclusively developing on Ethereum. While many responded that they develop on many platforms including Ethereum, only six percent of respondents said they do no development work on Ethereum, excluding EVM compatible chains, that number drops to two percent.
|
||||
|
||||
|
||||
|
||||
|
||||
What was surprising was the number of people who are working on EVM compatible chains (cue RUN EVM T-Shirts.) The most popular of these were EOS and and Cosmos in that order. What was perhaps most surprising was the fact that Lightning Network was more popular than any EVM compatible platform. This is most surprising because very little effort was made to get this survey in the hands of Lightning developers. This means either Lightning devs participated at a higher per capita rate than Ethereum devs, or that many Ethereum devs are self selecting to learn about Lightning.
|
||||
|
||||
Responses to this question show that Ethereum still dominates mindshare in the Ethereum community, but there is a diversity of effort happening. It will be interesting to see how these results develop over time, especially considering the concern around ETH2 expressed later in the survey.
|
||||
|
||||
## Tools
|
||||
The developer tools section was dominated by Truffle Suite with 68% of respondents saying they use it predominantly. As an early Ethereum project, this project deserves a lot of credit for making it easier to get into Ethereum development than other chains. On the framework side of things Embark came in close second with 34% of developers reporting using the toolsets.
|
||||
|
||||
|
||||
|
||||
That little green sliver is one of the more interesting findings. We anticipated that there would be some who were experimenting with Lightning development but were surprised to find that number reaching close to 10% of respondents. With the recent announcement from Lightning Labs that they are rolling out Loop, a non-custodial Bitcoin to Lighting on-ramp/off-ramp, we’re excited to see where this community goes over the next few months. It will also be useful to see how Lightning developers differ from Ethereum-only, or other EVM developers in future studies.
|
||||
|
||||
## Motivation
|
||||
|
||||
|
||||
|
||||
There were a small number of participants who answered that their reason for being interested in blockchain development is to “make number go up”. Beyond the financial motivation, most people gave more than one answer to these questions. Among the most popular were smart contracts and their composable business logic.
|
||||
|
||||
What was surprising was that philosophical reasoning wasn’t given more broadly. We had expected almost everyone to select censorship resistance and sound money for their reasoning to join crypto. As it stands only 28% gave these answers. DeFi, DAOs, and NFTs made a strong showing with close to half of responded saying they were a motivation. There seems to be a healthy mix of motivations for getting into the blockchain developer ecosystem.
|
||||
|
||||
|
||||
## Public/Private Chains
|
||||
Popular sentiment among the crypto community is that private chains are not really a serious endeavor. Enterprise chains have gotten off to a slow start ever since the “blockchain not Bitcoin” movement of the 2015 era. Given this, we were surprised to see a strong interest in developing for these projects.
|
||||
|
||||
|
||||
|
||||
Over half of respondents indicated their interest in building on private chains, when you include those willing to do it, “for a price” that number jumps to over three quarters. The remaining quarter have varying degrees of opposition to building on private chains. We can see the arguments on Twitter forming, “what do you consider a private chain?” Though we could have done a better job clarifying, this question was intended to mean an enterprise chain. It was refreshing to see the willingness of people to work on things that are outside the overton window that crypto Twitter advocates for.
|
||||
|
||||
|
||||
## Perception of public sentiment
|
||||
Back in the wild days of 2017 it was believed you could take any business model, throw the word Decentralized in front of it and people would flock to you. While this may have been true in the sense that people would throw money at your ICO, it hasn’t yet proven true in the race for acquiring real users.
|
||||
|
||||
|
||||
|
||||
In our survey we saw that a majority of developers agreed that they don’t believe users care about decentralization. This has been adopted by companies like Brave and Dharma which have adopted marketing that either doesn’t mention crypto at all or mentions it as a side note. That being said, decentralization was in fact important to developers with a majority of respondents saying that while users may not care, the developers still do.
|
||||
|
||||
|
||||
## ETH2 perception
|
||||
|
||||
|
||||
|
||||
As should be clear from the chart, an overwhelming majority of developers in this survey are concerned about ETH2 and its implications. The people working on ETH2 are heads down solving really hard problems. However, this response speaks to the need for better communication of the work that is happening, the problems and solutions involved, timelines, and what it will mean for developers in Ethereum in time.
|
||||
|
||||
One interesting finding is the small minority of users who are not at all concerned about ETH2. When digging deeper on calls some engineers mentioned that they have done research and understand the complexity involved in bringing it online. Perhaps the answer is DYOR and not believing the naysayers on Twitter, or perhaps outreach and better communication to combat ETH2 critics could ease concerns.
|
||||
|
||||
## Who are you building for?
|
||||
|
||||
|
||||
|
||||
We wanted to see what type of reach people are getting with their dapps. We were excited to see that more than a few people had over five thousand users on their platform. Over six percent of developers said they have over a thousand users. On the other side of this however over ninety percent said that they have less than a thousand daily active users on their dapps.
|
||||
|
||||
We’re excited to see these numbers change over the next year. There are some outlier applications like Brave with twelve million active users, but we hope to see even more breakout successes such as the recent launch of Dharma’s mainstream focused application.
|
||||
|
||||
Impediments to blockchain development
|
||||
We asked people what their biggest impediments are to building blockchain tools. In our Zoom interviews we had a lot of input on this question. The general feedback was that the learning required is vast. One interviewee said that learning web3 development was as difficult as learning to become a developer at all. The other interesting anecdote was the ‘analysis paralysis’ that comes from choosing which ecosystem/chain to work on.
|
||||
|
||||
|
||||
This question gave the most diverse set of opinions, and many developers chose more than one response. Unsurprisingly, ‘private key management/education” eked out a win as the most popular response. We hadn’t expected regulatory clarity to be such a large issue, but it was also substantial. Though not the most popular answer, we would postulate that this is actually the part of the reason we don’t see more founders getting into crypto. It’s hard enough to build a company, let alone one that has a threat of prosecution hanging over it.
|
||||
|
||||
|
||||
## Conclusion
|
||||
|
||||
## Several key findings stand out from this report:
|
||||
- Gitcoin respondents overwhelmingly selected Ethereum as the chain to work on, but also worked on other platforms including Bitcoin
|
||||
- Truffle remains the dominant developer toolkit for Ethereum, with Embark taking a smaller share of the use
|
||||
- The technical properties of blockchain are the main drivers for a developer choosing to get into the space
|
||||
- Private chains are an appealing option for developers interested in working full time in blockchain space
|
||||
- Developers are under no illusions that the public cares about decentralization, but they themselves do hold that ideal as important
|
||||
- The majority of developers surveyed are concerned about ETH2 and its implications for the future of Ethereum
|
||||
- Most dApps still have under a thousand daily active users
|
||||
- Regulatory clarity and private key management are still major impediments to the creation of dApps
|
||||
|
||||
What was most interesting however was the 1:1 interviews we conducted. We spoke to devs in Russia, Japan, the US and Egypt. These less formal interviews helped put a face on the developers. What was apparent among these people was the deep passion for the potential of this technology. People all over the world are coming into crypto with open minds and open hearts.
|
||||
|
||||
We can often feel like getting into crypto now is getting in “late”, but nothing could be further from the truth. The developer experience is still clunky. The learning curve is still steep. The regulation is still ambiguous. There is almost no aspect of being a developer in blockchain that could be considered “mature.”
|
||||
|
||||
Getting to peer into the mind of blockchain developers is something that needs to be done more often to ensure that we’re building the right tools to help foster growth in decentralized public development. We’re hoping to make this an annual report and welcome more input on distribution, categorization and methodology.
|
||||
|
||||
As the current crypto winter thaws we’re starting to see shoots of new growth. It’s an exciting time to be in cryptocurrency, even more so as a developer. Thank you to all the people who participated in this survey, and especially the team at Gitcoin for making it possible. We’re proud to be part of this ecosystem and look forward to supporting more developers as they come into the space.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue