You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pallet-revive and revive RPC binary are the replacement that Parity is working on instead of pallet-evm and Frontier.
revive-based smart contracts are what we intend to deploy on AssetHub, and are generally the technology that we intend to maintain more long term.
These are not fully ready yet.
I suppose your initial proposal explicitly called for the creation of pallet-evm templates. Back then (mid 2023) revive was not a thing yet :)
That all being said, your EVM template would be much more up to date and future-proof if it eventually becomes based on revive.
I suggest you to monitor the development of revive, and have a plan to migrate your template as soon as revive is stable to it. This can be incorporated in future governance funding as well.
Contribution Guidelines
I agree to follow this project's Contribution Guidelines
The text was updated successfully, but these errors were encountered:
templates
What is the feature you would like to see?
paritytech/polkadot-sdk#5308
pallet-revive
and revive RPC binary are the replacement that Parity is working on instead ofpallet-evm
and Frontier.revive-based smart contracts are what we intend to deploy on AssetHub, and are generally the technology that we intend to maintain more long term.
These are not fully ready yet.
I suppose your initial proposal explicitly called for the creation of pallet-evm templates. Back then (mid 2023) revive was not a thing yet :)
That all being said, your EVM template would be much more up to date and future-proof if it eventually becomes based on revive.
I suggest you to monitor the development of revive, and have a plan to migrate your template as soon as revive is stable to it. This can be incorporated in future governance funding as well.
Contribution Guidelines
The text was updated successfully, but these errors were encountered: