Restaking cloud has created a subgraph for the K2 protocol:

https://thegraph.com/hosted-service/subgraph/restaking-cloud/k2-protocol

Data points will be added over time for the K2 subgraph. Highlights include:

• Natively delegated BLS public keys
• Node runner representatives for the BLS public keys
• Activity events
• Reward claims

Holesky support for K2 is comming soon.

​

Querying all natively delegated BLS public keys

This is the query for establishing which Goerli validator, regardless of liquid staking protocol or solo staker, has natively delegated to K2 via MEV Plus:

{
  blspublicKeys(first: 1000) {
    id
  }
}

​

Example response:

{
  "data": {
    "blspublicKeys": [
      {
        "id": "0x82216ed82308bd4a2db9d4ba960b275e5ca50ac6924ed7199d7d7f1d31c4e2a4e2499a9bc52e4c4c0d07589887106469"
      }
    ]
  }
}

​

Querying the validators natively delegated by a specific node runner

In order to query the natively delegated validators by the Ethereum wallet address of a node runner, the following query can be run (make sure to replace the node runner address with the correct address and also make sure the node runner address is ALL lower case):

{
  blspublicKeys(
    first: 1000
    where: { nodeRunner: "0x7d3e58a4aea62417807a5c0929d936372a0a42fe" }
  ) {
    id
  }
}

Example response:

{
  "data": {
    "blspublicKeys": [
      {
        "id": "0x800330fec42ea0a795f5f87751bca39ce22858ef2828a12452505a4a5563c5c31519261f7167de746eb12bf92ae875d3"
      }
    ]
  }

​

Querying protocol activity events

The following can be used to see what activity is taking place in the underlying protocol (ordered from newest to oldest event):

{
  events(orderBy: blockNumber, orderDirection: desc, first: 1000) {
    keys
    values
  }
}

​

Github

All entities, code etc, can be found here:

https://github.com/restaking-cloud/K2-Subgraph

Any improvements, issues and more can be managed from this repository.