Independent verification
Silent Data provides a great way to ask someone to prove information about their bank account without requiring them to reveal their data.
You can now download a certificate from Silent Data and verify it in an independent, open-source tool hosted on GitHub. You no longer need to trust us, or our platform in order to know that a certificate is correct and valid.
- Each Silent Data bank account check results in a certificate that lists a number of assertions.
- However, if you receive a Silent Data certificate you don’t have access to the bank account data (and neither do we), so how can you know if these assertions are correct?
- Certificates created using the Silent Data platform can now be downloaded and independently validated using an open-source tool hosted on GitHub.
Step 1: Download & independently verify a certificate
- Each Silent Data certificate now features a “Download proof data” button.
- Click the button to download your own copy of the privacy-preserving certificate.
- If you don’t yet have a certificate, you can use this one that we created from our own company bank account:
Step 2: Upload and verify the certificate in an open-source verification tool
- Follow this link to the open-source tool on GitHub
- Click the “Upload proof” button, and select the file that you downloaded in the previous step.
- Click “Verify” and you should see the validations executed and turning green.
You no longer need to trust us to know that a bank account check was carried out correctly. You can use this tool any time, and inspect the open-source code behind it to be assured that the checks were conducted as expected.
Confidential enclave versions
Silent Data uses confidential enclave technology that leverages a dedicated secure area of a computer chip in order to process private banking data.
We will use a number of confidential enclaves over time, and if a fault is discovered with an enclave, for example if the chip manufacturer reports a security vulnerability that was not known at the time a certificate was created, then we will mark this enclave as untrusted. Any certificates generated by such an enclave will need to be recreated by the users. The MRENCLAVE value that we display is a unique confidential enclave identity provided and validated by the chip manufacturer.
Using this feature, users are assured of the integrity and security of the confidential enclaves used for Silent Data bank account checks.
