chore: upgrade to stable2409

[chungquantin]

Uplift asset-parachain template to stable2409 - Release Changelog. Configure pallet-revive for the runtime. By default, ETH RPC is not configured.

• Reference Upgrade polkadot-sdk-parachain-template to stable2409
  • Commit history: https://github.com/paritytech/polkadot-sdk/commits/polkadot-stable2409/templates/parachain
• Reference Upgrade pop-node to stable2409
• Reference Upgrade base-parachain to stable2409

Status

• ✅ Builds node & runtime successfully.
• ✅ Parachain node produce blocks with PASEO local.
• ✅ Deploy a new contract successfully with pop-cli

┌   Pop CLI : Deploy a smart contract
│
▲  NOTE: contract has not yet been built.
│
◇  Your contract artifacts are ready. You can find them in: /Users/chungquantin/Developer/pop-network/contracts-parachain/target/ink/my_contract
│
◇  Gas limit estimate: Weight { ref_time: 179608473, proof_size: 26643 }
│
◇  Contract deployed and instantiated: The Contract Address is "5E4z7LvRkgpAftqFuYSDRYW9q3TVnY8ybF5Mjnqhbr6qYhD4"
│
└  🚀 Deployment complete

[al3mart]

Changes look alright! Thanks!

If anything, given that we are introducing revive, it might make sense pointing in the README that users need to deploy this proxy server:

• https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/revive/rpc

Which emulates the Ethereum Json RPC. So that's the server eth dapps and wallets want to connect to instead of the node directly.

Also this is the REMIX version that should be used:

• https://github.com/paritytech/revive-remix

[AlexD10S]

Nice work! One thing before merging: please remove the network.toml file, as pop-cli generates it automatically. For future reference, it might be a good idea to add a line to .gitignore to prevent this in the future.

I was able to manually deploy a contract using pallet_revive. However, until pop-cli is fully compatible, it might not be worth adding too much detail about revive in the README. Perhaps just include a note for developers mentioning that the template includes pallet_revive and pallet_contracts for those who want to start exploring.

Maybe @al3mart's suggestion here is worth adding, especially if we plan to deprecate the EVM template in favor of this one: #12 (review).
However, I’m not sure if it falls out of scope without a proper update to the documentation.

[chungquantin]

Nice work! One thing before merging: please remove the network.toml file, as pop-cli generates it automatically. For future reference, it might be a good idea to add a line to .gitignore to prevent this in the future.

I was able to manually deploy a contract using pallet_revive. However, until pop-cli is fully compatible, it might not be worth adding too much detail about revive in the README. Perhaps just include a note for developers mentioning that the template includes pallet_revive and pallet_contracts for those who want to start exploring.

Maybe @al3mart's suggestion here is worth adding, especially if we plan to deprecate the EVM template in favor of this one: #12 (review). However, I’m not sure if it falls out of scope without a proper update to the documentation.

Apologies, I remember excluding network.toml already. Resolve by updating the README and removing network.toml.