After #855 passing I would like take the time to lay out what Parity is planning to deliver and when it will be delivered approximately. I also try to elaborate on how the community can contribute. Deliverables pallet_revive : A heavily stripped down and simplified fork of pallet_contracts. The obv…

[image] sourabhniyogi: Wonderful! For a Etherscan block explorer integration with contract verification, we require the equivalent of this Contract verification is just a matter of supporting deterministic compilation. This essentially requires agreeing on a “canonical build” of the compiler.…

Awesome!! I have a bunch of questions, I hope this is not off topic :sweat_smile: can a smart contract on asset-hub do cross-chain extrinsic calls to relay chain or system’s parachain(collective,coretime,people etc)? how can a smart contract interact with asset-hub pallets? Moonbeam has something …

[image] muddlebee: how can a smart contract interact with asset-hub pallets? Moonbeam has something called precompiles , will it be the same case here? Yes. We will be using the same system of exposing additional functionality via pre-compiles. Generally, everything that is not part of Solidit…

The minimum supported version will be 0.4.12. YUL yields better code and is considered mature since 0.8 and production ready (through --via-ir) on ethereum since version 0.8.13 released years ago . There will be minor things not supported because of the underlying bytecode and runtime differences. T…

The Etherscan team is mainly concerned about the breadth of customization needed to integrate PolkaVM – even though it sounds like not an issue, a lot of little things tend to come up. So perhaps the most cost effective solution in the expectation that a Asset Hub block explorer should have Ethersc…

Can a pallet extrinsic call a smart contract via pallet_revive? Possible scenarios are: schedule to call a smart contract Pallet functionalities are fixed, use smart contract for extending or customization

Yes this is possible. Another pallet would just call the bare_call public function of a contract. Those contracts you designated to be called just by the runtime would rather written in ink! than Solidity because they use the same type system.

bare_call isn’t safe to call a smart contract. I’m wondering about a typed and safe interface. I hope we can have this Add a pallet to demonstrate calling into a contract by ascjones · Pull Request #228 · paritytech/substrate-contracts-node · GitHub I also see you have an issue for Ink Make ink! …

The first version will be RISCV on WASM? Is there a plan that migrates the Substrate runtime to RISCV?

Contracts on AssetHub Roadmap

Tech Talk

Alex August 8, 2024, 4:01pm 8

I think that sounds reasonable.

Public good product ideas to be built for the Polkadot ecosystem

Topic		Replies	Views
Hybrid system chains make Polkadot permissionless Tech Talk	15	1479	July 16, 2024
Major Milestone for Solidity Smart Contracts: First Part of the Preview Release Now Live on Kusama Ecosystem smart-contracts , documentation	27	1884	July 24, 2025
Solidity smart contracts: Striking a balance between innovating and traction Ecosystem smart-contracts	22	1644	July 30, 2025
Polkadot Hub: Prioritizing growing ecosystem 3rd party providers, inc. DeFi, ASAP (through EVM) Ecosystem	9	1516	August 6, 2025
Can pallet revive Help Improve Polkadot's UX? Tech Talk frame , smart-contracts , ux	30	1578	July 24, 2025

Contracts on AssetHub Roadmap

Related topics