circlesubi / circles-dashboard Goto Github PK

Currently the graph feels laggy and inresponsive when there are too many nodes, let's look for alternatives!

Related: CirclesUBI/circles-core#34

Maybe add a message like:
"Between these two addresses no payment paths have been found"

It was deleted in #11,
but the visual component

import GrainIcon from '@material-ui/icons/Grain';

  <Chip
    icon={<GrainIcon />}
    label={`${health.graph.entityCount} entities`}
  />

and the complete query to the graph

{
  indexingStatusForCurrentVersion(subgraphName: "${process.env.SUBGRAPH_NAME}") {
    synced
    health
    entityCount
    fatalError {
      message
      block {
        number
        hash
      }
      handler
    }
    chains {
      chainHeadBlock {
        number
      }
      latestBlock {
        number
      }
    }
  }
}

can be added back once the index-node requests work again on thegraph.com.

Accounts

• x deployed Safes
• x registered usernames
• x unfinished registrations

HubTransfers

• x HubTransfer events (transitive transfers)
• Average amount: x Circles
• Average total received transfers per user: x
• Max total received transfers per user: x
• Velocity (Circles / Day): x

Transfers

• x transfers
• Average amount: x Circles
• x UBI Payouts:
• Average Amount: x Circles

Trust

• x trust connections
• x created trust connections
• x revoked trust connections
• Average outgoing trust connections: x (‘canSendToAddress’)
• Maximum: x
• Average incoming trust connections: x (‘userAddress’)
• Maximum: x

Ownership / Devices

• x ownership changes
• x manually removed devices
• x added devices (x added via deploying Safe)
• x manually added devices

Balances

• x Circles total balance
• Average x per Safe
• Max: x Circles
• Min: x Circles

Update the query to query the health of the graph.
Issue similar to: CirclesUBI/circles-api#101

Example: https://status.thegraph.com/incidents/fdr43b15bqnf