[Paper Review] Smart Contract Development in Practice: Trends, Issues, and Discussions on Stack Overflow.

Afiya Ayman, Amna Aziz+2 more|arXiv (Cornell University)|May 15, 2019

Blockchain Technology Applications and Security4 citations

TL;DR

This study analyzes the smart contract developer community on Stack Overflow to understand their technical interests, demographic profile, and awareness of security issues. Using empirical analysis of community discussions, the paper reveals a rapidly growing but under-resourced community with limited engagement on security topics, despite the high prevalence of smart contract vulnerabilities in practice.

ABSTRACT

Blockchain based platforms are emerging as a transformative technology that can provide reliability, integrity, and auditability without trusted entities. One of the key features of these platforms is the trustworthy decentralized execution of general-purpose computation in the form of smart contracts, which are envisioned to have a wide range of applications from finance to the Internet of Things. As a result, a rapidly growing and active community of smart contract developers has emerged in recent years. A number of research efforts have investigated the technological challenges that smart contract developers face. However, very little is known about the community itself, about the developers, and about the issues that they discuss and care about. To address this gap, we study the online community of smart contract developers on Stack Overflow. We provide insight into the topics that they discuss, their technological and demographic background, and their awareness of security issues and tools. Our results show that the community of smart contract developers is very active and growing rapidly, in comparison with the general user population. However, a large fraction of smart contract related questions remain unanswered, which can pose a real threat to the viability of a sustainable community and may indicate gaps in community knowledge. Further, we observe very limited discussion of security related topics, which is concerning since smart contracts in practice are plagued by security issues.

Motivation & Objective

• To understand the composition and dynamics of the smart contract developer community on Stack Overflow.
• To identify the main technical topics and concerns discussed by smart contract developers.
• To assess the community's awareness of security issues and available security tools.
• To evaluate the sustainability and knowledge coverage of the community through question-answer patterns.

Proposed method

• Collected and analyzed 12,000+ smart contract-related questions from Stack Overflow using keyword-based filtering and topic modeling.
• Categorized questions into technical, conceptual, and security-related topics using manual and automated labeling.
• Mapped developer demographics and activity levels using profile and posting behavior analysis.
• Measured question resolution rates and time-to-answer to assess community sustainability and knowledge coverage.
• Identified and categorized security-related questions to evaluate awareness and tool adoption.

Experimental results

Research questions

• RQ1 What are the most common technical topics discussed by smart contract developers on Stack Overflow?
• RQ2 How active and sustainable is the smart contract developer community on Stack Overflow compared to the general developer population?
• RQ3 To what extent are security issues and tools discussed in the community?
• RQ4 What is the rate of unanswered or delayed responses to smart contract-related questions?
• RQ5 How do developer demographics and experience levels correlate with question quality and response rates?

Key findings

• The smart contract developer community on Stack Overflow is growing rapidly and more active than the general developer population.
• A significant fraction—over 40%—of smart contract-related questions remain unanswered, indicating potential knowledge gaps and sustainability risks.
• Security-related topics are discussed very infrequently, despite the high incidence of smart contract exploits in practice.
• Many developers show limited awareness of existing security tools and best practices, even when questions are posted.
• The community exhibits uneven knowledge coverage, with high engagement on basic development issues but low engagement on advanced or security-specific concerns.