I’m Sergej, and I’m currently working on RegionX, a Coretime marketplace project. As we develop this project using ink! contracts, we are beginning to explore deployment options in anticipation of Coretime’s imminent launch on Kusama. We are particularly interested in deploying our contracts on Astar, but there are specific requirements that need to be met to make this feasible. In this post, I’d like to outline these requirements and seek feedback on the possibility of their implementation.
Coretime regions are represented as NFTs on the Coretime chain, allowing them to be transferred as any other asset via XCM (Enable cross-chain Coretime region transfers by Szegoo · Pull Request #3077 · paritytech/polkadot-sdk · GitHub).
Currently, Astar lacks support for handling incoming non-fungible assets, a capability that could be introduced by integrating a non-fungible pallet (e.g., pallet-uniques or orml-nft) and incorporating the appropriate asset transactor.
Additionally, we require a method to integrate with the non-fungibles pallet. After reviewing the forum post at Runtime interface contracts - Goodbye chain-extensions Welcome call-runtime, it appears that the most straightforward approach would involve enabling runtime calls to the non-fungibles pallet, along with adding a chain extension for state reads only.
I am open to feedback on whether this approach is feasible or if there are alternative methods that could facilitate this implementation.