Tracking Issue - Analytics

[grtlr]

There are several statistics that can help us better understand how a network is used. The following analytic endpoints should be supported by Chronicle:

• Add current ledger status statistics #328
  • Total number of minted NFTs
  • Total number of native tokens created
  • Total number of tokens locked for storage deposit #424
• Add activity statistics within time intervals #329
  • Total number of active addresses #419
  • Total number of IOTA / SMR tokens transferred #423
  • Total number of NFTs / native tokens moved (minted / transfered / burned) #516

The activity analytics should be implemented for set time intervals of 24h, 7d, 30d, and 90d.

In addition to these required statistics @Alexandcoats has some more brainstorming ideas below, which we could tackle afterwards.

Here is what the endpoints will look like:

Activity

• /activity ?startIndex & endIndex
  • /blocks (total count)
    • /transaction
    • /tagged-data
    • /milestone
    • /treasury-transaction
  • /outputs (total count/amount created
    • /alias
    • /basic
    • /nft
    • /foundry
    • /storage-deposit
  • /base-tokens (use ledger update table)
  • /native-tokens (use ledger update table)
  • /nfts (use ledger update table)

Ledger Status

• /ledger ?ledger_index (total count unspent)
  • /storage-deposit (byte cost at ledger index)
  • /nfts (count of the number of unspent nft ouputs)
  • /native-tokens (count of the number of unspent foundry outputs)

[DaughterOfMars]

Some requirements:

Granularity

• Daily
• Weekly?
• Monthly?

Messages

• Total
• Average per second

Transactions

• Total
• Average per second
• Included count
• Conflicting count?
• Transferred tokens

Outputs

• Average per address
• Max per address

Addresses

• Total unique used
• Unique sending
• Unique Receiving

[dharam0034]

hello, i think It would be nice to have a feature to see the "value" activity on tangle (i.e. the number of blocks that contain transaction payloads within a given time period only, excluding other message type of Milestone, Indexed and No payload).

I think "value" TPS (or per day/week) is one of the important metrics from tokenomics point of view.

[DaughterOfMars]

This information is already (almost) provided by the proposed API, indirectly, as transactions per second/day/week can be calculated easily using the time period given to the API and the total count. However, this does not work if you do not send a start or end time. We could either:

1. Provide the time range in the endpoint response.
2. Directly calculate those values (perhaps based on query params?)
3. Leave the endpoint as-is, so that it is only possible to calculate these values when providing both start and end time.

[grtlr]

In general it might be cool to have a payload analytics endpoint that counts the number of different payloads during an interval.

[dharam0034]

if query params are 1) time range & 2) payload type
and if the response of query contains the "timestamp of transactions" instead of count

then that's exactly what would be needed to make a chart like ...

[grtlr]

Thanks for the feedback @dharam0034! We will provide block level statistics that can be used to generate such a graph.