Skip to main content

FAQ

This page is meant to address commonly asked questions we hear!

We are always open to suggestions and make improvements to our codebase regularly

  • What's with all the "registration steps"?​

    The INTU Distributed Key Generation process requires input from each of the participants throughout the process to complete the MPC account.

    Each user needs to review and receive the other users info to complete their next step. So, each participant has to pre-register, before any participant can perform automate registration (which performs 3 rounds of cryptographic sharing). Once each user is done with automateRegistration, they can store their encrypted data to chain with registerAllSteps. Then, once everyone has registered, the account can finally be completed - where the address is generated for the MPC account.

    preRegistration

    automateRegistration

    registerAllSteps

    completeVault

  • How and why do you use the smart contract?​

    We use a smart contract to primarily act as data storage. Our goal with INTU was to be entirely decentralized, without any reliance on any 3rd parties, other networks, or any other dependenncy.

  • MPC or AA or SSS?​

    An EOA is your core identity within Web3.

    Account Abstraction allows for additional functionality, but adds an additional layer of complexity and overhead as well.

    Shamir's Secret Sharing is quick, but it relies on the full private key being formed, and then SSS is ran on it. It also doesn't allow for threshold signatures, requiring every participant to be involved in the process for every signature.

    Multi Party Computation is a leaderless process which has benefits like the private key never actually being created in full, so a single participant can never have access to it.

    We think that Web3 accounts are stronger with MPC technology like INTU's and Account Abstraction can be combined.

  • Why do you use percentages for thresholds instead of set numbers?​

    By using percentages, we can always determine the threshold (number of signers needed) of your choosing even if you add or remove participants.
    As an example, if you were to set a threshold of 4 when you have 4 total participants - and were later to remove a user - then you would have an impossible level of threshold to reach (4 threshold 3 users). This is a common question and we do look to address it in a more straightforward way in the future.

  • What is nostr?​

    We use nostr as a decentralized communication layer between the participants, so they can share cryptographic information between eachother without needing to write anything to chain.

  • How are the 'shares' stored?​

    The shares are encrypted with a signature from the user, and stored on chain. We took this approach so that we could be truly decentralized, without any reliance on any 3rd parties for storage or computation, just the EVM.