neo
neo copied to clipboard
neo-project
Request for Ethereum to Solidity conversion tools
Over the last 6 weeks I have converted several thousand lines of Solidity code from the Ethereum version of my dApp to C# code that runs on NEO N3. Very soon in the process, it became painfully apparent that a lot of the process involved tedious, repetitive operations that could be automated. For example:
- Variable type substitutions
- Solidity function to C# method reformulations involving basic transpositions of function attributes and parameters
- Converting Solidity
requirestatements to C# IF statements - etc.
Arguably there could be no greater boost to the NEO N3 ecosystem than a wave of experienced blockchain developers converting their popular dApps to NEO N3. Thus bringing with them their thousands or tens of thousands of users to NEO N3, a blockchain with a significantly superior development environment, far better performance, reasonable transaction fees, and a better end-user experience.
I suggest, strongly, that a set of tools be created that would eliminate the basic conversion tasks that as of now, injure badly any attempts to bring those Ethereum developers over to NEO N3. Personally I am committed to bringing my dApp over to NEO N3 and nothing will prevent that from happening. But why not create some basic tools to make that same decision much easier for other Ethereum developers to make? These developers have to weigh their decision to migrate against the time and effort it will take to make that leap. Shouldn't we make that decision as effortless as possible?
You can see in my latest video in the series I publish on converting Solidity smart contracts to C#/N3, exactly the kind of simple, yet time consuming and error prone translation steps that are necessary to do this code conversion, here:
https://youtu.be/MqWpjpHKHlo?t=562
We have discussed building a solidity-like language since antshares days. This would probably be the best solution(but would be the most involved) since it would natively support the syntax. It wouldn't have complete coverage because there are native operations that don't map, but would get people pretty far in migrating. If that would meet the need, we should be able to find some resources to work on it.
@lock9 @devhawk @ixje
I think it is a “nice to have” feature, not a must. Our vision is to attract the millions of no blockchain developer to build real life application for mass adoption.
Our path requires more time and patience initially, but I think the goal is more ambitious than having only cryptokittens on our chain.
We also covered all the other EVM functionalities, so what is the real value proposition to be another BSC? If this converting tool requires too resources, effort and time, I would remain strictly related to our primary focus. That’s my idea.
Everything that helps NEO to get new developers onboarded is a must in my opinion. NEO needs a quick network build up and huge dapp universe that makes it attractive to new developer groups. There are plenty of projects on Ethereum that migrated over to other chains (e.g. Avalanche) because it was easy for them. A converter would be an additional feature and wouldn’t limit more complex projects.
Good initiative. I think NGD and team should invest resources to make it happen.
