Deep Account Analytics (Polkadot Data Alliance) Milestone 2

[sourabhniyogi]

Milestone Delivery Checklist

• The milestone-delivery-template.md has been copied and updated.
• This pull request is being made by the same account as the accepted application.
• I have disclosed any and all sources of reused code in the submitted repositories and have done my due diligence to meet its license requirements.
• In case of acceptance, an invoice must be submitted and the payment will be transferred to the BTC/ETH/fiat account provided in the application.
• The delivery is according to the Guidelines for Milestone Deliverables.

Link to the application pull request: w3f/Grants-Program#1768

[sourabhniyogi]

@takahser -- This project is not suitable for Docker-based review. This is because Polkaholic.io, while open source, depends on a Google Cloud backend (BigTable, MySql, GS, BigQuery) and in this case Apache Superset. We have worked with @michaelis @ w3f who has audited both Milestone 1 and 2 to his satisfaction, which I hope should satisfy the majority of your audit concerns. Here is a log of @mkchungs 's conversation with him for the milestone 1/2:

Chat_Export_1_PDA_deep_analytics.pdf
Chat_Export_2_michael&michalis_deep_analytics.pdf

I booked a time slot for Dec 11, but I recommend you check in with him before the call if possible

[takahser]

See comment in the M1 delivery PR.

[sourabhniyogi]

Based on data collected from OpenGov referendum #248 + #366, Colorful Notion has decided to discontinue the polkaholic.io website. Polkaholic remains as the indexer to support Dune + Google BigQuery for the Polkadot ecosystem. It turned out there was little demand to covering APIs, cloud costs, SaaS subscriptions not already covered by Subscan, which covers block explorers and API for the ecosystem adequately.

The work on this grant on traces, staking and governance directly informed how we did our first Dune dashboards, and we are deeply grateful for @michalis's deep and consistently thoughtful requests and feedback and support on this grant.

As we are occupied with executing on #366 intensely over the next 2-4 months, we will come back to doing the Polkaholic public repo cleanup later this summer.

[takahser]

@sourabhniyogi thx for the update. Does this mean we can terminate the grant? What exactly do you mean by "Polkaholic public repo cleanup"?

[keeganquigley]

pinging @sourabhniyogi does this essentially mean this milestone won't be delivered?

[sourabhniyogi]

We already delivered all the milestones and submitted evidence of this in November from michalis. However, the last reviewer created a new requirement that we deliver a Docker container (which makes no sense given the GCP backend) + clean up our polkaholic repo, which is an unbounded task with ad hoc evaluation. We did a lot of Dune dashboards on staking and governance and got actionable feedback from michalis. We believe the correct thing to do is to 1. isolate the traces part from Milestone into a new repo that actually CAN be put into a Docker container and loaded in like a Dune table 2. Adjust our Milestone 2 report with documentation of how the Dune dashboards work, which we did in Jan/Feb This appears more substantive to me because (1) can be used by others and quite cheap to execute on by anyone. (2) is more useful for the Polkadot community because we'll actually maintain it.

…

On Fri, 5 Apr 2024 at 09:41, Keegan | W3F ***@***.***> wrote: pinging @sourabhniyogi <https://github.com/sourabhniyogi> does this essentially mean this milestone won't be delivered? — Reply to this email directly, view it on GitHub <#1045 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACUXO27TCNOZ5LSS7BDPFDY33H2DAVCNFSM6AAAAAA62JGKSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBQGIZTOMRQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>