The merkle-root is published as an PublishedHash event on the Integritee Parachain. Events are short-lived and purged from on-chain storage after each block, such that we don't have an ever-growing chain-state for state that is not needed for the actual chain business logic. It is an indexer's task to track the actual events on the chain and put them into its database.
The easiest way is to query the Integritee indexer on Subscan: https://integritee.subscan.io/. Then it would only be a simple curl command. However, this can only be done with the Kusama deployment and not on the testnet.
A way that would need some more engineering, but is possible without an indexer includes needs https://github.com/olisystems/BEST-Energy/issues/27, and then we can query the chain storage as it was on that specific block height.
I suggest that we simply wait for the production deployment.
The merkle-root is published as an
PublishedHashevent on the Integritee Parachain. Events are short-lived and purged from on-chain storage after each block, such that we don't have an ever-growing chain-state for state that is not needed for the actual chain business logic. It is an indexer's task to track the actual events on the chain and put them into its database.I suggest that we simply wait for the production deployment.