Back to treasury proposals
Treasury Proposal#210 >> Council Motion#555
Rejected
Requested: 1.75K KSM

#210 Polkaholic.io - Polkadot+Kusama XCM/Multichain Block Explorer (Q2+Q3 2022)

Proposer:
DakP...tZbN
 
in Treasury
2nd Oct '22

Detailed Proposal:

https://docs.google.com/document/d/1_ao-Hk-GxIPUDpWijDK4KXUjst0rglZZBzIuMGG7aVQ/edit#

Short Description:

Support Colorful Notion’s Polkaholic.io open source XCM/Multichain block explorer, indexing of all Polkadot + Kusama + parachain data with a special emphasis on XCM Transfers / Messages, made available in UI/API/CDN/BigQuery form to support Polkadot+Kusama ecosystem’s multichain initiatives.

Proposal Summary:

Colorful Notion proposes to:

  • Expose and maintain public archive of all the raw data indexed by Polkaholic.io (blocks, extrinsics, events and traces) available in CDN form and then in BigQuery form and indexed data (specifically and especially XCM transfers and XCM messages) in API form
  • Continue to index all Polkadot chains to the fullest extent possible to generate and maintain the archive with APIs, which may be relied upon by large scale archival systems. These APIs maintain Value transfers/XCM transfers according to DEX info on top “defi” parachains
  • Model XCM Transfers and Messages across the entire Polkadot/Kusama ecosystem
  • Enhance Polkaholic.io indexing as the Polkadot ecosystem expands: New parachains, new pallets generating XCM extrinsics/messages with new XC Assets, support for ERC20/PSP22/ERC721/PSP34 assets, XCMv3, and new bridges

Show More

Deadline: Not Set
Please Log In to comment

4Comments
GLVe...F7wj
 
 
6th Oct '22

Hi @Sourabh, thank you for your proposal. It looks very interesting, and useful for users to understand what XCM and "visualize" transactions in the overall ecosystem.

My question is related with the costs included in the proposal:

Image

  1. Am I right in understanding this covers Q2 and 3 only?
  2. On the proposal you also list "proposed enhancements" in some of the sections of "Polkaholic UI + API + CDN Service Detail": are these covered by the proposal as well? if not, how do you plan to cover?
  3. You have presented quite good use-cases for the explorer in the proposal: do you have some metrics on the number of users in the first phase of your project?

Thank you!

Hide replies
DakP...tZbN
 
 
7th Oct '22

Thank you for your questions!

  1. Yes, this covers Q2+Q3 2022 only. We hope to submit Q4 2022 with a progress reports on our enhancements in January. We are self-funded but with consistent Treasury support, we can operate with the reliability and redundancies that parachains expect for their users. If polkaholic.io fails on these dimensions on a trailing 3 month basis and/or we don't implement the proposed enhancements, we should like to not have our next proposal accepted.

  2. Yes, proposed enhancements will be developed in Q4 2022/Q1 2023 with treasury support. We invite and appreciate discussion from all "fellows" about how to prioritize our proposed enhancements for maximum ecosystem impact in 2023.

Fellows: the doc is open to comments, please share your guidance. We will make all efforts to implement it quickly if is easy, ask for advice on how to do it correctly -- Thank you!

2'. For how we expect to cover 2023-2024 and not be on perpetual Treasury support:

Long-term: we believe that as (XCM-enabled) bridges between Polkadot+Ethereum (and others) materialize, a fees based business model will become clear to us and others like us. The DAUs, swap/xcm fees in the ecosystem need to grow a lot more though, so we want tools like ours to stimulate this growth.

Medium-term: leading parachains need advanced indexing functionality to grow their ecosystem (on XCM Connected Contracts/EVM+/WASM/PSP22/NFTs/specialized defi/...), either funded through their own treasury, with a collator rewards model, or a SaaS model like Etherscan.

Short-term: for "new" parachains that are trying to get started, they need help in the birthing process and having a SaaS model for all parachains would appear too much to ask.

Big picture, however, we believe a full archive of all raw data should be sought and not be contingent on { fees, collator rewards, or Saas }, and we are happy to play a role getting raw traces, etc. for everyone. We can be guided by Wikipedia's full history download + the Internet Archive spirit here, where it should be considered inexcusable that any relaychain/parachain's full history could possibly be lost! We do not have to play this role forever but are happy to get it started since we have to do it for our XCM indexing.

  1. We have included a new section "Polkaholic.io User Metrics" doc showing a recent Google Analytics covering Q3 (July-Sept 2022) [we did not have users in Q2]. We have 100-150 DAU consistently. As Polkaholic.io becomes more feature complete with our proposed enhancements and stronger SLAs required by leading teams, it may be appreciated as a system of record for XCM and archival data.
DakP...tZbN
 
 
19th Oct '22

For councillors that did not vote "Aye" on this (as well as those who did), it would be valuable if you could share your concerns/feedback, ideally in the form of

"I would vote yes once you do this _____"

"I would vote yes if you do this in Q4 ____"

"I vote no because ____"

( or whatever you would like )

If you wish to chat with us, we have a public Matrix room, can set up a private telegram group and are eager to learn and get feedback on how to work to have maximal impact in the ecosystem.

Thank you!


Discover similar proposals


Empty Icon

No Active Proposals