What is Comms?
Operational reconciliation for tokenized real-world assets.
The question Comms answers
Know whether an RWA token’s onchain state matches its offchain reserves and operational lifecycle.
A wallet, protocol, issuer or user supplies an RWA token address. The intended service compares current onchain state with verified offchain reserve and lifecycle information, returning SAFE, WARNING or BLOCK.
Operational verification, not a credit rating or investment quality score. SAFE does not mean risk-free.
Source: PDF p1 §1
Why token liquidity is not enough
A token can remain liquid while its underlying asset, legal structure or attestation pipeline has desynchronized.
- Reserve desynchronization: onchain supply exceeds verified offchain backing.
- Stale attestations: the PoR pipeline is offline, delayed or unverified.
- Infrastructure restrictions: bank accounts or custodian rails are frozen or restricted.
- Compliance mismatches: transfer policies have changed offchain without synchronization.
- Oracle or contract failure: NAV data is stale or administrative permissions have changed.
Source: PDF p1 §2
What is available today
This deployment provides the Comms frontend, address-format validation, report/evidence/permission views and documentation. It is not connected to a reconciliation backend. Entering an address does not perform chain reads, reserve checks or signature verification. No live status is issued.
The target in the source API example is Robinhood Chain Testnet, chain ID 46630. The official network documentation lists mainnet separately as 4663.
Source: Frontend delivery boundary; PDF p3 §7; Robinhood network documentation