Get Your appId - Create a Sismo Connect App

Before you begin integrating , you must first register a Sismo Connect app in the . This step is mandatory to obtain an application Id (appId), which is required during the Sismo Connect development process.

Why is an appId required for Sismo Connect?

The appId will be used to compute a vaultId, which is the unique identifier for a user on your app. The vaultId is simply the hash of a user's Vault secret and the appId.

$vaultId = hash(vaultSecret, appId)$

If we remove the appId from this simple calculation, we would have had the same vaultId for the same vaultSecret, effectively leaking information about a user that uses Sismo Connect on two different apps. The vaultId would be the same across different apps, and the user could be tracked if the vaultIds became public.

By introducing an appId, the vaultId is now different between apps, and the same user will have two different vaultIds on two different apps, effectively preserving the user's privacy.

You can learn more about this notion in this .

Feel free to add *.com to authorized domains when developing in local. This will allow you to easily whitelist localhost. Don't forget to update the authorized domains when deploying in production.

Once created, you should have all information about your app displayed in your profile:

The appId displayed on your app’s profile in the Factory is its unique identifier. You will use it to request proof from your users in your app’s front end and to verify it in the back end or your smart contracts.

In this example, my appId is 0xde1d47d45d449d7efe9242e66a05e1c1.

PreviousTutorials NextOnchain Tutorial (1/2): Code Your Airdrop Contract With Privately-Aggregated Data

Last updated 1 year ago