Rule-setting: Keyring Connect

1. Onboarding programme

For each supported website, a data hook to the website's server is coded according to Keyring’s base rule language. The Policy Owner defines the set of user requirements from a menu of options, given in the Rule Builder. Typical verifications include:

  • Valid KYC

  • Non-US resident

  • Accredited investor

2. Data extraction

The user is directed to the data source's website and their data is notarised via the Keyring browser extension, enabling secure exchange of keys and information (MPC-TLS) between the server, the notary and the user’s browser.

3. Verification process

The browser extension creates a Merkle Proof to reveal certain information as defined by the policy and sends the proof to the notary server. That proof is verified by the Attestation service.

4. Outcome

Once verified, the proof is fed to the Policy's Risk Matrix to yield a binary {pass,fail} result (the Rule Outcome) according to the requirements defined by the Admission Policy. The user can check the status of their onboarding on the Keyring UI.

Last updated