# TrustChain reports For a demo example of following steps, here is the policy timestamp: **1675176247.137536341** ### **Task** Create a report to check a chain of documents. ### **Preparation** We will use example 4 to assemble multiple documents to build a realistic-looking *Trustchain*. Let’s add several additional attributes into the documents to simplify the document search.

### **Building the trustchain report:** 1. Using the ‘***reportBlock***’ 1.1 Add new container

1.2 Add ‘***reportBlock***’

In Guardian policy ‘**reportBlock**’ finds VP documents based on their *id* or *hash* and displays document information, related policy and token information. To retrieve the linked information ‘**reportItemBlock**’ must be used. 1.3 We will build the following chain in this example: \*\*mint \*\****VP – MRV Report – Project (approved and signed the the Approver) – Approver document – Project (created and signed by the user) – User document.*** We will need 6 ‘**reportItemBlock**’ items correspondingly, 1 per each document.

The ‘**reportItemBlock**’ items are executed sequentially, thus in the filter for each consecutive ‘**reportItemBlock**’ we can use values from the previous blocks/documents. 1.3.1 ‘**mint\_document**’. To find this document which described the token mint operation we will use one of the **Common Variables** - *actionId*

1.3.2 ’**report\_document***’*. To find the MRV report (i.e. data document which was the basis of the decision to mint tokens) we will also use one of the **Common Variables** – *documentId*

To find further documents we will need to use values from the **Ref** variable which point to the previous document. Let’s save in a new variable:

1.3.3 ’**project\_document(approver)***’* - Lets use the previously defined variable alongside the static filtration parameters.

Save the author of the document signature so we can display the information about the user later

**Use the same approach to continue the chain until the end.** 1.3.4 ***’*****approver\_document*****’***

1.3.5 ’**project\_document(user)***’*

1.3.6 ’**user\_document***’*

2. To activate the ‘**reportBlock**’ an id or a hash of the VP document is needed, we will add the grid containing the list of the VP documents and links to the trustchain. 2.1 Add ‘**interfaceContainerBlock**’, ‘**interfaceDocumentsSourceBlock**’ and ‘**documentsSourceAddon**’

2.2 Add new column with the type **BUTTON**

Setting the **Action** to LINK will cause the Policy Engine to attempt to switch the display to the target policy block upon the user clicking the link (if possible). ### **Demo** #### VPs:

#### Trustchain:

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.guardianservice.app/technical-information/library-of-policy-examples/trustchain-reports.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.