[WIP - DO NOT READ YET][ShannonScan] Foundational changes for Relay Mining & Probabilistic Proofs

[Olshansk]

Objective

A handful of enhancements to set the foundation of getting visibility into onchain services, probabilistic proofs and relay mining in Shannon.

Goals

• Get visibility into the following in Shannon via ShannonScan
  • Onchain services
  • Relay Distribution
  • Relay Mining
  • Compute Units
  • Probabilistic Proofs
  • Claims & Proofs
• Set a baseline for critical Pocket related metrics
• Enable iterating and making more complex improvements down the line
• Note:
  • Baseline: These stats can most likely be accessed through basic indexing / querying
  • Advanced: This will require more complex ETL (Extract Transform Load) data pipelines w/ aggregation of prior Claims & Proofs, etc...

Deliverables

1. Services (Baseline)

Why? Need to be able to get visibility into onchain services: what's available and at what cost.

• Add support for Services under the Blockchains drop-down
  
• Show baseline service state (equivalent of querying it onchain)

   $ pkd_beta_query query service show-service anvil

  Output:

   service:
     compute_units_per_relay: "13"
     id: anvil
     name: ETH Anvil
     owner_address: pokt1ytsx06dfxrp7cgt7t95jkxuyu2m97563zqz5pn

• Allow scrolling and searching for service name by ID

1.1 Relay & Compute Units per Service(Advanced)

Why? Visibility into onchain usage of the network: relays, compute units, payments and earnings.

• Relays:
  • Total Relays: Show the total amount of relays each service has served on-chain
  • Relay Ranges: Allow filtering the total amount of relays served by a service between blocks A and B
• Compute Units
  • Total Compute Units: Show the total amount of compute units each service has served on-chain
  • Compute Unit Ranges: Allow filtering the total amount of compute units served by a service between blocks A and B
• Distributions (pie chart or table)
  • App payments: Relays / Compute units serviced based on Applications paying for service
  • Supplier Earnings: Relays / Compute units serviced based on Suppliers servicing requests

2. Blocks

Why? Need to get visibility into onchain scalability and state bloat

• Block Distribution
  • Update the block page (example with:
    • Pie chart showing transactions, claims, proofs, other

---

Creator: @Olshansk
Co-Owners: @RawthiL @jorgecuesta @Alann27 @bryanchriswhite @red-0ne @okdas