State of Developments and Plan for Future Deliveries
In earlier days, FireProtocol announced its integration with Acala for its migration to Polkadot. The integration however was not openly deployed due to the status quo of Acala test-net.
At the current stage, FireProtocol is a DApp built under HECO with Solidity as the original coding language. And, it relies on EVM to be functional.
To enable better migration to Polkadot, FireProtocol decided to integrate with Acala for the pre-stage development, deployment and testing of the DApp.
Now, EVM.Acala has some built-in testing assets already. In the meantime, networks such as Plasm and Edgeware of the Polkadot ecology also support EVM.
However, Acala’s EVM (https://evm.acala.network) is still under internal development and testing, and not opened for deployment yet. As a result, FireProtocol team is pulling all resources in finding the networks which will register as Polkadot parachains and support EVM. Based on the structure and protocol of these networks, FireProtocol will be further improved, making it more integrated into Polkadot.
For sure, FireProtocol team will keep eyes on Acala. Once Acala openly supports EVM, team will kickstart the deployment in the first time.
In regards to future deliveries, the team is working on future deliveries such as Launchpad, Cross-chain Loan etc. Announcements will be made when official.
Thanks for the support, as always.
