v2 docs update

Author: marcello33

docs/pos/architecture/heimdall_v2/clerk.md

@@ -104,6 +104,7 @@ One can run the following query commands from the clerk module :
 * `record` - Query for a specific event record by its ID.
 * `record-list` - Query a list of event records by page and limit.
 * `is-old-tx` - Query if the event record is already processed.
+* `latest-record-id` - Query the latest record (state-sync) id from L1.
 
 
 ### CLI commands
@@ -128,6 +129,10 @@ heimdalld query clerk record-sequence [tx-hash] [log-index]
 heimdalld query clerk is-old-tx [tx-hash] [log-index]
 ```
 
+```bash
+heimdalld query clerk latest-record-id
+```
+
 ### GRPC Endpoints
 
 The endpoints and the params are defined in the [clerk/query.proto](/proto/heimdallv2/clerk/query.proto) file.
@@ -153,6 +158,10 @@ grpcurl -plaintext -d '{"tx_hash": <>, "log_index": <>}' localhost:9090 heimdall
 grpcurl -plaintext -d '{"tx_hash": <>, "log_index": <>}' localhost:9090 heimdallv2.clerk.Query/IsClerkTxOld
 ```
 
+```bash
+grpcurl -plaintext -d '{}' localhost:9090 heimdallv2.clerk.Query/GetLatestRecordId
+```
+
 ### REST endpoints
 
 The endpoints and the params are defined in the [clerk/query.proto](/proto/heimdallv2/clerk/query.proto) file.
@@ -162,6 +171,10 @@ Please refer to them for more information about the optional params.
 curl localhost:1317/clerk/event-records/list?page=<page>&limit=<limit>
 ```
 
+```bash
+curl localhost:1317/clerk/event-records/latest-id
+```
+
 ```bash
 curl localhost:1317/clerk/event-records/<event-id>
 ```
@@ -176,4 +189,4 @@ curl localhost:1317/clerk/sequence?tx_hash=<tx-hash>&log_index=<log-index>
 
 ```bash
 curl localhost:1317/clerk/is-old-tx?tx_hash=<tx-hash>&log_index=<log-index>
-```
+```

docs/pos/architecture/heimdall_v2/heimdallv2_swagger.yaml

@@ -1539,6 +1539,45 @@ paths:
           format: uint64
       tags:
         - Query
+  /clerk/event-records/latest-id:
+    get:
+      summary: GetLatestRecordId queries the latest record id from L1.
+      operationId: GetLatestRecordId
+      responses:
+        '200':
+          description: A successful response.
+          schema:
+            type: object
+            properties:
+              latest_record_id:
+                type: string
+                format: uint64
+              is_processed_by_heimdall:
+                type: boolean
+        default:
+          description: An unexpected error response.
+          schema:
+            type: object
+            properties:
+              error:
+                type: string
+              code:
+                type: integer
+                format: int32
+              message:
+                type: string
+              details:
+                type: array
+                items:
+                  type: object
+                  properties:
+                    type_url:
+                      type: string
+                    value:
+                      type: string
+                      format: byte
+      tags:
+        - Query
   /clerk/event-records/list:
     get:
       summary: GetRecordList queries a list of records
@@ -4204,6 +4243,14 @@ definitions:
     properties:
       is_old:
         type: boolean
+  heimdallv2.clerk.LatestRecordIdResponse:
+    type: object
+    properties:
+      latest_record_id:
+        type: string
+        format: uint64
+      is_processed_by_heimdall:
+        type: boolean
   heimdallv2.clerk.RecordListResponse:
     type: object
     properties:

docs/pos/architecture/heimdall_v2/introduction.md

@@ -8,8 +8,8 @@ Heimdall v2 is a modernized and revamped consensus client that is at the heart o
 - Orchestrates the state sync mechanism between Ethereum and Polygon PoS.
 - Addresses other essential aspects of the system.
 
-It uses the latest [*Cosmos SDK*](https://github.com/maticnetwork/cosmos-sdk) and [*CometBFT*](https://github.com/cometbft/cometbft) for its consensus.
+It uses a fork of [*Cosmos SDK*](https://github.com/0xPolygon/cosmos-sdk) based on `v0.50.13` and a fork of [*CometBFT*](https://github.com/0xPolygon/cometbft/) based on `v0.38.17` for its consensus.
 
-Heimdall removes certain modules from Cosmos SDK but primarily utilizes a customized version of it, following a similar pattern.
+Heimdall leverages some modified versions of `cosmos-sdk` modules (`auth`, `bank` and `gov`) plus some fully customized modules (`bor`, `chainmanager`, `checkpoint`, `clerk`, `milestone`, `stake` and `topup`).
 
-For detailed instructions on running Heimdall v2, refer to the [Readme](https://github.com/0xPolygon/heimdall-v2/blob/develop/README.md) in the Github repository
+For detailed instructions on running Heimdall v2, refer to the [Readme](https://github.com/0xPolygon/heimdall-v2/blob/develop/README.md) in the Github repository