Summary: Polkadot Hub needs a custom Etherscan integration for PolkaVM/revive Smart Contracts. The proposed $1MM Etherscan-as-a-Service integration provides Web3/Solidity developers seamless tools for deploying and interacting with PolkaVM contracts first on Westend Hub and then on Polkadot Hub, aiming for increased developer+user growth of Polkadot Hub in 2025-2026. Problem: Polkadot Hub needs a PolkaVM Block Explorer Polkadot Hub (also known as Asset Hub or &ldquo;Plaza&rdquo;) is now positioned in the Polkadot 2.0 Roadmap as the primary home for user-facing and developer-facing smart contract activities as well as staking, governance and managing programmable assets. Historically, EVM contracts have been deployed in the Polkadot ecosystem in <a href="https://moonscan.io/">Moonbeam</a> and <a href="https://astar.blockscout.com/">Astar</a> through the &ldquo;<a href="https://github.com/polkadot-evm/frontier">Frontier</a>&rdquo; pallet, but with key breakthrough <a href="https://forum.polkadot.network/t/announcing-polkavm-a-new-risc-v-based-vm-for-smart-contracts-and-possibly-more/3811">PolkaVM</a> (a RISC-V-based virtual machine also at the heart of <a href="https://graypaper.com">Polkadot JAM</a>) there is a new Polkadot Hub+Cloud roadmap: <a href="https://forum.polkadot.network/t/contracts-on-assethub-roadmap/9513">Contracts on AssetHub Roadmap</a> <a href="https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949/7">Solidity on PolkaVM</a> <a href="https://www.youtube.com/watch?v=GPuTt10dxKI">Contracts on Polkadot Introducing Project Revive</a>
These are a part of numerous <a href="https://x.com/alice_und_bob/status/1863979132062748954/photo/1">Polkadot 2.0 innovations</a> from <a href="https://www.rob.tech/blog/plaza/">Plaza: A Batteries-Included, Scalable Polkadot System Chain</a> (<a href="https://x.com/rphmeier/status/1802809037186089243">summary</a>)) to CoreVMs + CorePlay JAM Services. This roadmap enables 4th generation Web3 developers to access Polkadot in both high-performance ways in &ldquo;old&rdquo; ways (Solidity-based Smart Contracts on Polkadot Hub) and &ldquo;new&rdquo; ways &ndash; enabled by Polkadot JAM Services, not with yet another EVM Chain but with PolkaVM, revive and Polkadot 2.0 innovations at its foundations. This proposal concerns giving Web3 developers the best blockchain service available: <a href="https://etherscan.io/eaas">Etherscan as Service</a>, with dominant usage in the Ethereum ecosystem (Ethereum, Base, Optimism, Arbitrum, &hellip;) in addition to Moonbeam users in the Polkadot ecosystem.&nbsp; Etherscan&rsquo;s feature set is comprehensive and difficult for other block explorers to match. For an overview, see <a href="https://www.youtube.com/watch?v=ve1fouiC3v0">Diving deeper with EVM block explorers</a>. Our key motivation is simple: Give Users + Developers the industry-leading explorer for Polkadot Hub: Etherscan &ndash; but fully customized for PolkaVM + revive-pallet innovations. <a href="https://forum.polkadot.network/t/contracts-on-assethub-roadmap/9513/19">Alex Thiessen</a> (Parity Contracts team lead, also proponent of <a href="885">OpenGov #885 - Should we allow EVM compatible contracts on Asset Hub?</a>) indicates unequivocal support of Etherscan here: 
<img src="https://i.ibb.co/6BM05qz/image.png" alt="image.png" /> Solution: Etherscan as a Service (EAAS) Custom Integration The vast majority of Smart Contract Developers write contracts in Solidity and deploy compiled EVM byte code to an EVM chain &ndash; most commonly Ethereum and Ethereum rollups but also Polkadot rollups (Moonbeam, Astar).&nbsp; With the revive pallet deployed on Polkadot Hub, these Solidity contracts will be compiled to PolkaVM instead of EVM, and interpreted by the revive-pallet on Polkadot Hub instead. Widely used REMIX tooling has&nbsp;already been customized for PolkaVM at <a href="https://remix.polkadot.io/">https://remix.polkadot.io/ </a>and enables compilation and deployment to Polkadot Hub in 2025, but is available on WestEnd Hub now: See <a href="https://contracts.polkadot.io/deploy-your-first-contract">Deploy Your First Contract</a> to see how simple and familiar this is to everyday Solidity developers. In the same way, this proposal strives to have Etherscan also be simple and familiar as REMIX is to users and developers alike. This is enabled by a set of JSON-RPC methods necessary for indexers to do their work &ndash; our <a href="https://hackmd.io/FEHH1zuWR3aGPJUBWAS8Iw">tests</a> indicate Westend Hub is ready for Etherscan integration in early 2025 and after all systems are fully tested, can proceed to Polkadot Hub as soon as pallet-revive is deployed in mid-2025.&nbsp; &nbsp; However, a custom integration is required to fully address PolkaVM.&nbsp;
Here is a full link to the detailed proposal:
<a href="https://docs.google.com/document/d/1SfYggOIZpTIYlpdFUiP45EAjVRr4rC4h_pI6bK3YpBg/edit?tab=t.0#heading=h.v6is2ta0txr1">Etherscan-as-a-Service x Polkadot Hub - PolkaVM Block Explorer (1 Mainnet, 1 Testnet)</a>
The proposal provides adequate budget ($1MM) for the Etherscan team to address + support the PolkaVM + revive custom integration fully.&nbsp; &nbsp;Colorful Notion is taking on project management of the integration through 2025 into early 2026. Key Benefits:
(1) Technical: Fully functional PolkaVM-based Westend and Polkadot Hubs, supported by robust secure infrastructure from industry leader. (2) Developer Impact: Seamless Etherscan interface for PolkaVM/revive contracts on Polkadot Hub will attract leading Web3 teams deploying on Polkadot Hub. Tools for contract interaction and code verification match EVM. (3) User Impact: Dapp deployment on Polkadot Hub can support an order of magnitude growth in usage, driven by the above. Budget: $1,000,000 USDC Services:&nbsp;
<ul>
<li>1 TestNet EAAS Integration: Westend Hub hosted at westend-hub.polkadot.io (or similar) Expected coverage: Q2 2025 &mdash; Q1 2026 ( 1 year )</li>
<li>1 MainNet EAAS Integration: Polkadot Hub hosted at hub.polkadot.io (or similar) Expected timeline: Q3 2025 &mdash; Q2 2026&nbsp; ( 1 year )</li>
</ul>
 Merry Christmas🎄🎅 and Happy New Year 2025! 🍺🎉🤗&nbsp; We look forward to making 2025 a great success together!
 
&nbsp;

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- **Problem Statement:** Polkadot Hub lacks a PolkaVM Block Explorer, hindering smart contract activities.
- **Significance:** Enhancing Polkadot Hub with a custom Etherscan integration for PolkaVM/revive Smart Contracts is crucial for attracting developers and users.
- **Proposed Solution:** Implement a $1MM Etherscan-as-a-Service integration for seamless deployment and interaction with PolkaVM contracts on Westend Hub and Polkadot Hub.
- **Expected Outcomes:** Anticipated benefits include a fully functional PolkaVM-based ecosystem, increased developer engagement, and significant growth in Dapp deployment on Polkadot Hub.

#1345 Etherscan-as-a-Service x Polkadot Hub - PolkaVM Block Explorer (1 Mainnet, 1 Testnet)

No Active Proposals