Add a Content Identifier (CID) page and a Content Identifiers (CIDs) page. Add Protocol fee column to the Actions and Payments Table on the Request page

[MantisClone]

Motivation

Users want to analyze CIDs, and the Protocol fee required to store a given request

Definiton of Done

• [ ] Support CID in the Search Bar
• [ ] Add Protocol fee column to the Actions and Payments Table on the Request page
• [ ] Add a Content Identifier (CID) page
  • [ ] List of labels and values (similar to the Request page)
  • [ ] CID (with copy button next to it)
  • [ ] Age and Datetime
  • [ ] Blockchain Transaction ID in which the CID was submitted on-chain
  • [ ] Size of data
  • [ ] Protocol fee to store the CID
    • [ ] This would require us to add the protocol fee to the storage subgraph
  • [ ] Transactions Table (encrypted and unencrypted), Actions Table (unencrypted only)
  • [ ] Columns: Action, Request ID, Age, From/Signer, To, Protocol fee
  • [ ] Link each Request ID to the Request page
  • [ ] Link each address to the Address page
• [ ] Add a Content Identifiers (CIDs) page
  • [ ] Dynamic metrics at the top: All-time # of Content Identifiers, Last hour # of Content Identifiers, Last week # of Content Identifiers, Last month # of content identifiers
  • [ ] Content Identifiers Table
  • [ ] Columns: Content Identifier (CID), Age and Datetime, Blockchain Transaction ID, Size of data, Protocol fee, Number of actions
• [ ] All Content Identifiers (CIDs) have a Copy button to the right of them
• [ ] All Content Identifiers (CIDs) are truncated showing only the first 14 characters

Considerations

There are two options for implementing the Protocol fee columns:

1. Easy option: Display the fee to store the whole CID, even if the request is part of a batch.
2. Harder option: Display the fee to store only this request. If part of a batch, calculate the fee from the size of the data - using the same calculation used in the smart contract.