The Enterprise Ethereum Alliance Mainnet Working Group created a survey to solicit the opinions of enterprise developers working on Ethereum applications. The survey was emailed to the EEA mailing list and promoted on Twitter from November 2020 to January 2021. The following is a summary of the results and answers to key questions.

  • There are 42 respondents.
  • 73% of respondents believe that they are enterprise software developers or architects working on Ethereum applications. Probably the others are developers who are not related to the term “enterprise.”
  • 72% of respondents are using the Ethereum mainnet; 74% are working with private chain stores; 51% are working with them.

Significant response to “Which of them do you think needs improvement and how to improve”

  • Solidity should have ready-made examples of supply chain, DeFi and other applications
  • Reliability: Brings on-chain identity, ZKP and homomorphic encryption, which can be used for safe assets in compliance with regulations
  • Stability: We should have a network process like software
  • Transaction trace and Solidity debugger
  • [Bring] Web3js has the latest features
  • Similar to webflow
  • stable [of] Truffle Ganache
  • Truffle, to compile each file with a different compiler version, VSCode has a better debugger plugin.
  • Network settings, for example, N nodes starting from the basic settings for privacy, permission – Besu is working on it, but it needs to be improved to make it great for businesses
  • Mixing, versatile, but few resources
  • Children’s smart contract coding (similar to Scratch Studio)
  • Web3j, poor maintenance
  • My current pain point is full abi2 support for Web3j
  • [Support for] rust
  • #Tx/sec
  • No, but an optimistic summary of L2 execution contracts is essential
  • Support for Node.js wrapper for arbitration-based evms
  • Documentation tools need to be improved.It would be nice to integrate in one of the main document generation tools
  • IPFS browser integration
  • IPFS or any other enterprise-level production-ready storage solution
  • IPFS: Protected access; everything else is REST…
  • Interoperability between different blockchains
  • Thousand Island Hall

The obvious answer to “what tools or libraries or services do you think are missing and should exist”.

  • Easy/automatically build APIs on top of smart contracts
  • Generic REST-API “producer” for smart contracts
  • [Tools for] Regression testing, analysis, formal verification
  • Good debugging tools across Java applications and stability will be very useful
  • A good visual debugger
  • Key store, signer storehouse of key store such as KMS and HSM
  • Webflow, the second-tier development tool
  • web3j or any web3 should have separate APIs to manage a) create transactions, b) sign transactions via web3 or independently, and c) submit transactions to the desired network.
  • Deploy libraries and mixed development (public testnet/local-agents that can be retained after recompilation).
  • MetaMask… very useful, but can provide more support for developers, such as local RPC network
  • JS library of evm’s quos
  • UI components
  • Interoperability library to perform connection to another blockchain network
  • Central open smart contract library and its detailed documentation.
  • Organizations dealing with decentralization
  • Rust-based client
  • Token script

Significant response to “What standards do you think are missing or should be improved?”

  • Blocking/confidential tokens such as Aztec and Anonymous Zether.
  • Interoperability between off-chain resources
  • Best practice: non-pegged stablecoin and utility token economics, dealing with real software products based on Ethereum (business and development aspects)
  • privacy
  • safety standard
  • On-chain encryption
  • IPF alternatives, interoperability
  • Written commitment of cash rewards for safe disclosure
  • REST-API first
  • Message delivery
  • key
  • DID/SSI support as a base layer for application integration for human, company and machine identities
  • Better NatSpec standard: https://github.com/ethereum/solidity/issues/10825

A notable response to “As a developer, what other Ethereum-related challenges do you face?”

  • High gas bills
  • Gasoline prices
  • Gasoline prices
  • Change – the cost of natural gas on public blockchains is high
  • Ethereum 1 scalability
  • Scalability
  • privacy
  • Safety test
  • key
  • CI / CD-Automation-not restricted by the platform (for example, Infura, etc.)
  • Nonce management with flexible architecture
  • Entity version changes
  • Solidity will provide many improvements for date and structure management in the future
  • Slow testnet deployment/debugging standards
  • The document is bad, the product does not work
  • Learn the latest resources
  • Java tools are not yet mature.Once you perform non-simple operations, there is still a lot of copy and paste to deploy the contract, for example, deploy a physical contract in a Genesis file with storage
  • Reliability: From an enterprise perspective, RPC is not that reliable.Need more features to enhance RPC or use open source MQ for messaging
  • Communication with other developers. Need a network.
  • BFT, private transaction
  • Interaction issues in open Ethereum
  • Build an economic system around decentralized applications to maximize network effects to prevent someone from forking the project and reduce protocol revenue or the need to develop closed source projects

in conclusion

Put forward some suggestions to improve the development tool ecosystem. Due to the relatively small sample size, no major clusters or trends were found (except for natural gas prices/scalability). It may be useful to repeat the survey a few months later.

Some interviewees mentioned high transaction fees and scalability as challenges. This shows that developers need to be educated about layer 2 technologies designed to solve these problems.