Monitoring cross-chain transactions
Overview
This guide introduces the tools and processes available for Subnet Auditors to monitor transactions within a Rayls Private Subnet. It provides an overview of the key tools—Subnet Auditor Explorer and Flagging Transactions—that enable auditors to ensure the network's compliance, security, and data integrity.
These tools are essential for Subnet Auditors to fulfill their role in monitoring and auditing the network while respecting privacy controls and maintaining security.
Prerequisites
Before utilizing the monitoring tools, ensure the following components are fully deployed and operational:
- Commit Chain: Running and accessible, as it records all cross-chain transactions.
- Governance API: Deployed and functioning to support the retrieval and management of flagged transactions.
- Listener: Actively monitoring the Commit Chain for incoming transactions.
- Flagger: Running to detect and flag discrepancies within the network.
- Subnet Auditor Explorer: Configured for Subnet Auditor access, with the appropriate permissions for viewing decrypted cross-chain transaction data.
Subnet Auditor Explorer:
The Subnet Auditor Explorer provides decrypted visibility into cross-chain transactions within the Rayls Private Subnet, allowing auditors to monitor transaction details across different token standards and teleport protocols. It focuses on cross-chain activities recorded on the Commit Chain, while intra-ledger transactions remain private.
Learn more about using the Subnet Auditor Explorer here
Flagging Transactions:
The Flagger automatically identifies potential issues, such as double minting or inconsistent balances, by comparing decrypted net token balances with published ledger states. Discrepancies are flagged for further investigation by the Subnet Auditor.
Updated about 2 months ago