Can you tell what are the pain points for the Blockchain developers while developing DApp/ managing consortium networks.

closed as primarily opinion-based by mirg, Achala Dissanayake, Ismael, Richard Horrocks, TC8 Jun 20 '18 at 9:40

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.


I don't think DApp is a challenge because in the end it is just an application and you can face general problems that you face writing any application.

Most of the complex part is handled by the Web3.js library (given you are using JS/NodeJS to write your code) and similarly other libraries to handle the JSON-RPC communication. The documentation and support for web3 is tremendous compared to other libraries.

When you start out you can face few challenges in communicating with your smart contract because the documentation can be confusing sometimes. The only place I faced challenges were listening to events on Ethereum and had to play around with various filters on those events to get the right fit ( I am still in the process of learning that, pretty ambiguous)

If you are writing the chaincode (smart contracts) then getting along with Solidity might take sometime because there are many challenges you face when you deal with structures and it keeps on getting more and more complex. Main reason for that is many things that you do in your traditional programming languages, do not work here. E.g working with literals or assigning some runtime variables.

If you understand these things properly I don't think there should be a problem. Don't be afraid to play around.

Not the answer you're looking for? Browse other questions tagged or ask your own question.