search

use-ink / contracts-ui

Web application for deploying wasm smart contracts on Substrate chains that include the FRAME contracts pallet
https://contracts-ui.substrate.io/
GNU General Public License v3.0
61 stars 44 forks source link

Create Other Resources and Links, Integrate WASM Contract Explorer #468

Open sourabhniyogi opened 1 year ago

sourabhniyogi commented 1 year ago

Is your feature request related to a problem? Please describe. Having "Other Resources and Links" page with other resources and links, which can include WASM contract explorers and development tools like ChainIDE could be useful. Currently looking up activity for a code hash, contract address, storer or deployer is not tractable without an indexed backend of WASM Contract activity.

Describe the solution you'd like Adding a QuickLinks section pointing to "Other Resources and Links" as recommended by #466 . It seems silly to have a page with one link, but its a start. See Alternative 2 for something about 10x

Describe alternatives you've considered Alternative 1. Adding a quick links page on the front page with WASM Contract Explorer.

Alternative 2. Having tighter links to WASM Contract Explorers + Block Explorers using code hashes, contract addresses, storer and deployer addresses, similar to the way polkadot.js apps links to polkaholic.io + subscan via block hash.

statictype commented 1 year ago

@sourabhniyogi I see the explorer currently supports only Astar and Shiden. what is your timeline to support other chains? we could link to code hashes and addresses once you support all the networks that have deployed the contracts pallet.

As far as I see Chain IDE doesn't support Substrate, why would we link to it?

sourabhniyogi commented 1 year ago

Polkaholic's indexing scope has been all public Polkadot+Kusama parachains, potentially funded within a "Parent/Child Bounty" structure of the WASM Parent Bounty or a Substrate + XCM Big Data Parent Bounty. We are only aware of Astar/Shiden/Amplitude/Pendulum parachains deploying the contracts pallets in production -- since there is marginal extra effort to index WASM Contracts for these parachains, we would expect to cover all parachains that have deployed the contracts pallet in the future with extremely low effort. For Rococo, there is additional new effort but we would happily cover this critical "development" case + also others (Aleph Zero?) outside Polkadot+Kusama if deemed appropriate by the parent bounty curators. Kindly advise if you would like to see more than this, very happy to explore going outside Polkadot+Kusama parachains.

Astar is leading efforts with Chain IDE + WASM Contracts, nothing is public. We imagine a tight integration is possible with Ink Verification Service API and this WASM Contract Explorer (and others, maybe) -- once Chain IDE (or other IDEs) have WASM Contract Template support, it is highly appropriate. Until then, we can plan for it.