Smart contract developers that come from other protocols in the ecosystem need a guide that helps them understand the similarities and differences they will have in their experience building smart contracts on Hedera compared to where they are coming from
Even though Hedera is evm compatible there are differences the developer would need to understand interacting with out network, our entities, the way gas is paid, etc
This differences need to be highlighted so that we can educate our web3 smart contract developers coming to Hedera and ensuring a smooth experience
Using a contract that is deployed on another network and porting it to Hedera would be a good starting point to capture what the differences might be along that process
Do we have different smart contract developer personas that build different kinds of applications using smart contracts?
The goal is to learn about the smart contract developer learning path and propose an outline for what kind of content needs to be covered
Some things that come to mind are explaining the different kinds of addresses Hedera has for the smart contract entity. Ones that are evm compatible and ones that are only Hedera network compatible.
How to setup TheGraph with Hedera ( in context of an application)
Testing of the application
How does the user interact with the smart contract application (reference application)
Incorporate differences for Hedera [testnets, wallets, etc]
Tasks