[Tip Request] Hydradx EVM support on subsquare

Content

AI Summary

To support HydraDX EVM related features on subsquare, OpenSquare team did some customization development, including:

Research and learn code of HydraDX app to check how EVM works on HydraDX.
Deploy statescan and subsquare instances for parsing history EVM related extrinsics and testing.
Support metamask connect, singing and commenting. This request lots of code refactor to support both substrate and EVM addresses on a single network.
Support web2 user binding an EVM address.
Do address convertion between EVM address and substrate address to show them on UI and submit extrinsics.
In scan scripts, extract substrate calls from ethereum#transact extrinsic, so we can update referendum status in time when related calls detected.

Cost

Roughly these features cost us 2 FTE 10 days work, 160 hours. Taking $80 per hour as the rate, it's $12,800. Considering these features can be used by other projects, we will request part of it. Our final request is 500k HDX.

Edited

SubSquare is a platform that has added new features to support HydraDX EVM. Here are the changes they made:

They learned how EVM works on HydraDX by studying its code.
They created instances for testing and parsing EVM related extrinsics.
They made changes to support both substrate and EVM addresses on a single network, which required a lot of code refactoring.
They allowed web2 users to bind an EVM address.
They converted EVM addresses to substrate addresses to show them on the user interface and submit extrinsics.
They updated referendum status in time when related calls were detected.

These features cost 2 full-time employees 10 days of work, which is roughly 160 hours. They requested 500k HDX as payment for their work.

Up 2