FAQs
Frequently Asked Questions
Real-Time Proof of Reserves continuously brings together reserve and liability data from connected sources. The information is aggregated, analysed and used to generate updated CPA/CA attestation reports according to the reporting cadence established for the engagement.
Reserve information can be updated as frequently as every 30 seconds when the underlying data sources support it. The actual reporting frequency depends on the availability of each data source, the integration method and the requirements of the engagement.
LedgerLens supports more than 50 active integrations across exchanges, custodians and banks. Information can be collected through APIs, FTP, FIX, virtual machines, and CSV or PDF parsing.
A system-generated attestation is compiled and produced automatically based on the requirements and inputs established by the CPA or CA performing the engagement. This reduces manual compilation while allowing reports to be generated at the agreed reporting frequency.
Ripcords are automated checks applied before a report is published. If a check fails or a data anomaly is identified, publication is halted so that the issue can be investigated before the report reaches its intended users.
For most deployments, the standard integration timeline is approximately two to four weeks once development begins. The final timeline depends on the scope, number and type of data sources, and client onboarding requirements.
Real-Time Proof of Reserves continuously brings together reserve and liability data from connected sources. The information is aggregated, analysed and used to generate updated CPA/CA attestation reports according to the reporting cadence established for the engagement.
Reserve information can be updated as frequently as every 30 seconds when the underlying data sources support it. The actual reporting frequency depends on the availability of each data source, the integration method and the requirements of the engagement.
LedgerLens supports more than 50 active integrations across exchanges, custodians and banks. Information can be collected through APIs, FTP, FIX, virtual machines, and CSV or PDF parsing.
A system-generated attestation is compiled and produced automatically based on the requirements and inputs established by the CPA or CA performing the engagement. This reduces manual compilation while allowing reports to be generated at the agreed reporting frequency.
Ripcords are automated checks applied before a report is published. If a check fails or a data anomaly is identified, publication is halted so that the issue can be investigated before the report reaches its intended users.
For most deployments, the standard integration timeline is approximately two to four weeks once development begins. The final timeline depends on the scope, number and type of data sources, and client onboarding requirements.
FAQs