Hello, how can we help you?

Follow these steps to pair your mobile device with the inabit platform:

Step 1: Install the inabit Mobile App

1. Download the App:

• For iOS devices, visit the App Store.
• For Android devices, visit the Google Play Store.
• Search for "inabit" and download the app.

2. Install the App:

• Follow the on-screen instructions to install the inabit app on your mobile device.

Step 2: Launch the inabit Mobile App

1. Open the App:

• Locate the inabit app icon on your mobile device and tap to open it.

2. Sign In with your preferred cloud of choice:

• Google Drive (iOS / Android)
• iCloud (Exclusive to iOS)

Step 3: Initiate Device Pairing

1. Navigate to Pairing Section:

• Once logged in, go to the "Settings" or "Account" section of the app.
• Find and select the option for "Device Pairing" or "Pair Device."

2. Scan the QR code to get the Pairing Code in the App:

• The inabit platform will generate a unique pairing code or QR code.

Step 4: Pair the Device with inabit Platform

1. Log In to inabit Platform:

• On your computer or another device, log in to the inabit platform using your account credentials.

2. Access Device Pairing Option:

• Navigate to your user and find the option of "Pair Device".
• You will also have the option highlighted on any screen in the web platform, if you're in an approver-fitting role

3. Enter Pairing Code From The App:

• Enter the pairing code generated by the mobile app.

Step 5: Confirm Pairing

1. Verify Pairing / Pairing in Progress:

• A confirmation period will occur and you will need to wait with the screen opened on your mobile app

WARNING: Do not close the mobile application while device pairing is in progress!

2. Successful Pairing:

• Once confirmed, your mobile device will be securely paired with the inabit platform.
• You will be displayed with a green screen of "Pairing Completed" in the mobile app.
• Once the screen is displayed, you will instantly be moved to the next step of your mobile app onboarding.

Step 6: Test the Pairing Connection:

Test Functionality:

• Perform a test transaction or action within the inabit app to ensure the device pairing is working correctly.
• You should be receiving an approval request for every transaction within a wallet's policy that you're a set approver of.

Troubleshooting
If you encounter any issues during the pairing process, consider the following tips:

• Ensure Internet Connection: Both your mobile device and computer should have a stable internet connection.
• Update the App: Make sure you have the latest version of the inabit app installed.
• Restart Devices: Sometimes, restarting your devices can resolve connectivity issues.
• Contact Support: If problems persist, contact inabit customer support for assistance.

Summary

Device pairing is a vital security feature that enhances the safety and convenience of using the inabit platform. By following this guide, users can easily pair their mobile devices, ensuring a secure and seamless experience.

For any further assistance, please refer to the inabit support resources or contact our support team.

Learn about inabit's role system and its permissions per each role

inabit Roles Hierarchy

The following page describes inabit roles system by order "highest" to "lowest".

Owner

The owner is the one that approves signing devices and new users and is granted with all of the permissions in the entire system (account).

There's only one owner to an inabit account

Reminder -> there can be multiple organizations in an inabit account, but there cannot be multiple inabit accounts under the same owner.

Admin

An admin has access to everything in the system except being able to open new organizations, viewing the account settings & remove the owner.

An inabit account can have multiple admins per organization and an admin can be a set as a different user per each and every organization.

Signer

Signers are users similar to admins but their sole purpose is to approve or reject transactions. The signer can't perform administrative operations like add/remove new users to/from an organization.

Editor

Editors can access everything in the system but creating new wallets, approving/rejecting transactions and editing organization settings and its users.

They are still capable of creating transaction requests.

Viewer

A viewer only has viewing permissions in an inabit organization and he/she cannot initiate transactions or edit any of the settings but their own. (User photo, email, password, etc.)

API User Roles

In order to access our API capabilities and authenticate queries and mutations,
you must create an API Admin/Viewer.

API Admin

The API admin role is internally generated by inabit when an organization desires to utilize inabit's API infrastructure. Upon receiving such a request, we establish an "API user" devoid of access credentials to the platform's UI. This user's sole function is to issue an access token for inabit's API.

By utilizing the access token provided through this user's credentials, you gain access to inabit's queries and mutations within our GraphQL schema. A significant distinction between this role and other API user roles is that this API user possesses equivalent permissions to a standard Admin within the system.

With this role, you can execute various actions such as creating transactions, adjusting organization settings, inviting new users to your organizations, establishing wallets, and much more - all through the API.

How to create an API Admin?

• Contact inabit's support at support@inabit.com
  to retrieve login access credentials and fetch a JWT access token when you authenticate.
• Use the token as a bearer across all of your queries and mutations.

Note - You can also decide to create an API Viewer. The same role permissions are applied to the Viewer role in the platform, doing so you will only receive API capabilities of a viewer.

API Signer

API signer is a unique user created by inabit that is separated from an API admin/viewer.

This API user is created for the sole purpose of serving as the "API approver" to sign transactions using inabit's developed tool we call the "Docker Signer".

In a nutshell, this role's purpose is to serve as a "remote approval" application to simulate/replace the standard inabit mobile approvals app for services that develop and build their infrastructure with inabit.

• You can learn all about this in our Remote Infrastructure section.
• If you still find it hard to understand, feel free to contact us for tailored support: support@inabit.com

API Viewer

The API viewer is another role generated (currently) by inabit internally when an organization wishes to operate and utilize inabit's API infrastructure.

The sole difference between an API admin and API viewer is the permission access to the capabilities of the API.

• The API viewer isn't capable of calling mutations such as createTransferRequest or createApiWalletAddress.

See which wallet types are supported on our platform.

Overview

This page outlines the Users concept in the Inabit system. A user represents an individual who has access to the platform and belongs to a specific organization. Each user has a unique identifier and associated profile information.

Key functionalities:

• Access and use assigned resources and data within the organization.
• Perform specific actions based on assigned roles and permissions.
• Update personal profile information.
• Manage individual settings and preferences.

Relationships:

Additional Information:

Overview

This page defines Organizations within the Inabit system. An organization represents a group of users that belong to the same account. It allows for granular access control and management within the platform.

Key functionalities:

• Create and manage users within the organization.
• Assign specific roles and permissions to users.
• Manage organization-specific settings and resources.
• Track user activity and data within the organization.

Relationships:

• An organization belongs to one account (N:1).
• An organization can have many users (1:N).
• Users within an organization share access to specific resources and data based on their permissions.

Additional Information:

• You can find information on creating and managing organizations in the Organization Management API documentation: link.
• For details on user roles and permissions, refer to the User Management section in the API reference.

Overview

This page explains the concept of Accounts in the Inabit system. An account represents a single entity that uses the Inabit platform. This could be an individual, a company, or any other type of organization. Each account has its own unique identifier and is the top level of the Inabit hierarchy.

Key functionalities:

• Create and manage organizations within the account.
• View and manage user access and permissions.
• Access administrative functionalities for the account.
• Billing and subscription information are all based on the account. (account-level)

Relationships:

• An account can have many organizations (1:N).
• Organizations within an account share access to certain resources and settings.

Additional Information:

• You can find information on creating and managing accounts in the Account Management API documentation: link.
• For details on available permissions and roles, refer to the User Management section of the API reference.

This page clarifies the relationships between accounts, organizations, and users within the Inabit system.

Key Terms:

• Account: Represents a single entity that uses the Inabit system.
• Organization: A group of users that belong to the same account. An account can have multiple organizations.
• User: An individual who has access to the Inabit system and belongs to a specific organization. An organization can have multiple users. A user can be associated with multiple organizations as well.

Relationships:

• One account can have many organizations (1:N).
• One organization belongs to one account (N:1).
• One organization can have many users (1:N).
• One user belongs to one organization (N:1).

Example:

• Inabit Corporation (Account)
  • Marketing Department (Organization)
    • User1 (Marketing Manager)
    • User2 (Social Media Specialist)
  • Sales Department (Organization)
    • User3 (Sales Representative)
    • User4 (Account Manager)

Wish to enable Off ramping for your account?

Apply Here

What is On Ramp?

An On-Ramp is a service or process that allows users to purchase cryptocurrency using traditional fiat currency. This is typically done through a cryptocurrency exchange or a payment service that accepts fiat currency (e.g., credit/debit card, bank transfer) in exchange for digital assets like Bitcoin, Ethereum, etc.

What is Off Ramp?

An Off-Ramp is the opposite process, where users convert cryptocurrency back into fiat currency. This is essential for cashing out your digital assets into a traditional bank account or other fiat-based financial systems.

Which countries are supported by inabit?

inabit proudly extends its support to diverse regions worldwide, spanning over 150 countries across 5 continents. Our commitment to global accessibility ensures that users from virtually anywhere can benefit from our platform's services. Whether you're in North America, Europe, Asia, Africa, or Oceania, we've got you covered. 

To see the complete list of supported countries, click here.

Which currencies are supported by inabit?

We are proud to support a wide range of currencies, including all major ones such as USD, EUR, INR, JPY and many more. In fact, we support 45 different currencies, ensuring that our platform is accessible and convenient for users around the world.  

To view the full list of supported currencies, click here.

Which Tokens are accepted by inabit?

Inabit supports USDT on the Ethereum, TRON, and Polygon networks, as well as USDC on the Ethereum network.

Discover what Disaster Recovery means in cryptocurrency and how it works in inabit.

What is Disaster Recovery?

In crypto, Disaster Recovery (DR) involves plans and procedures to restore and access digital assets after major disruptions (disasters) like cyberattacks or hardware failures. It includes backup systems, security measures, geographic redundancy, testing, communication plans, and regulatory compliance to ensure the safety and availability of assets in emergencies.

inabit - being a self-custody wallet solution, offers the option to recover digital assets from its wallets.

Disaster Recovery in inabit

inabit offers an organization-based disaster recovery (DR).

In order to fully execute a truely self-custody recovery solution and ensuring the safety of the sensitive files (such as the encrypted wallet.dat file - the file in which all of the mnemonic seed phrases are held encrypted), inabit chose to partner with Vaultinum.

About Vaultinum
Vaultinum is a trusted independent third party specialized in the protection and audit of digital assets.

Since 1976, they have enabled thousands of digital creators, digital businesses and tech investors secure their innovations by providing solutions to:

Protect their Intellectual Property with IP Deposit and IP Audit.

Ensure the continuity of their business activity with Software Escrow.

Mitigate cyber and software risks through in-depth Technology Due Diligence (KYS-Know Your Software).

Create an unforgeable proof of date and time of event with our Certified Time-stamping solution.

With secure servers based in Europe, ISO 27001 certification, and a unique double expertise in IT and legal, their clients benefit from the highest levels of security and protection for all their sensitive assets.

Overview

Creating strong policy rules is a vital step in maintaining control over your transaction outflows. Owner and admin can set the policies rules, such as whitelisting addresses to prevent unauthorized transactions and setting spending limits for both the entire wallet and individual transactions.

Only approvers are allowed to edit/change a wallet's policy. (both tiers & settings)

Who's an Approver?

An approver is a platform user with signing permissions that successfully paired their device. Applicable approver roles: (signer, admin, owner)

Wallet Policy Settings

Our governance layer which we call "Transaction Policy", is defined per wallet, meaning each wallet can have its own custom policy settings.

The organization owner and his admins are the ones allowed to edit/change a wallet's policy settings.

Do note that every change in a wallet's policy setting will require the owner's approval via the mobile application.

You can view the list of wallets and their policies in the Policy tab.

Clicking on a wallet from the list will open the tiers tab first by default, you can then switch to the "Wallet Settings" tab.

Currently, there are two settings that can be changed within a wallet's policy:

• Allowance to send funds exclusively to saved addresses that the user defines.
• Allowance to perform off-ramp transfers from the wallet.

Set Whitelisted Addresses

This policy setting is selected by default and allows you to send a wallet's funds to specific addresses that are saved (whitelisted) within the dedicated whitelist addresses list.

You can add/remove saved addresses directly through the wallet policy settings interface, as well as decide if you'd like to disable this setting (by toggling off the button).

Allow Off Ramp Transfers

This policy setting is also selected by default and defines wether the wallet's funds can be used for off ramp transfers or not.

Reminder - Each change made on the wallet settings / policy tiers will require the account's owner mobile approval.

Wallet Policy Tiers

Wallet policy tiers are essentially an advanced policy setting that can be enabled on a wallet to apply an additional layer of security to govern your wallets assets.

There are three fields you can set according to your liking in a policy tier:

1. Transaction amount range.
2. Dedicated transaction approvers.
3. Minimum amount of approvals. (Taken from the dedicated transaction approvers)

Note that changing a wallet's policy tiers can only be done by a signer or above. (applicable approver - Signer/Admin/Owner).

In addition, any change on the policy will require the account's owner mobile approval.

Default Policy Tier

The default policy tier is essentially the default transaction policy set upon creation of an inabit wallet. There's a difference between the default policy tier of a standard inabit wallet and an API wallet.

Here's a table explaining the differences:

Do note that the policy default tier cannot be removed, but can be changed. You can still decide on the approvers and the minimum required approvals of a policy rule.

Removing Policy Tiers
You can dispose of a previous tier by clicking on the trash icon on the right hand side of the tier.

Approve Policy Changes

Once a change request has been made, the wallet's policy status will be changed to Pending.
Afterwards the account owner will receive a mobile request.

Anyone can still view the policy settings and tiers of a wallet's policy that's pending approval by visiting the policy page and clicking on the wallet for its policy details.

You will notice that when a wallet's in Pending status, you will be able to review the changes that are waiting for an approval, as well as what's the current rule settings that are set, by switching through the toggle shown above.

The owner of the account can also view the changes and the current state of the wallet policy settings before approving on his/her mobile device:

If the owner rejected the changes, they will have the option to undo the rejection for a duration of 3 seconds after the rejection was made, on their mobile screen.

When a rejection was set, the rule changes back to Live status and the old settings of the wallet are still applicable. When approved -> the new changes take place.

If you have any further questions regarding the wallet's policy (governance) feature, don't hesitate to contact us at: support@inabit.com.

Inabit prioritizes the security of your data and transactions. One key layer of protection we employ is Trusted Execution Environment (TEE) technology. TEE creates a secure enclave within the main processing unit, acting as a dedicated vault for sensitive information and operations.

What is TEE?

Imagine a secure room within your hardware, isolated from the main operating system. This protected space, enabled by TEE, safeguards sensitive data and code from unauthorized access, even if the main system is compromised. This isolation ensures:

• Confidentiality: Your data remains encrypted and unreadable outside the TEE enclave.
• Integrity: Any code or data stored within the enclave cannot be tampered with.
• Attestation: You can verify the authenticity and integrity of the TEE environment itself.

How does Inabit use TEE?

In Inabit systems, TEE can be utilized in various ways to enhance security, including:

• Protecting sensitive user credentials: Login details, encryption keys, and other critical information can be stored and processed within the TEE enclave, minimizing the risk of theft or misuse.
• Securing critical system functions: Specific system functions handling sensitive data or transactions can be executed within the TEE, isolating them from potential vulnerabilities in the main system.
• Enabling secure communication channels: TEE can establish secure tunnels for data communication between Inabit's systems and your devices, ensuring the integrity and confidentiality of data in transit.

By incorporating TEE, Inabit strives to provide an additional layer of defense for your data and transactions, fostering a more secure and trustworthy user experience.

Accelerating transactions in Bitcoin - How does it work and how inabit utilizes it?

Accelerating a Bitcoin Transaction

Bitcoin transactions are typically processed by miners on the blockchain network, but sometimes they can take longer than expected to confirm. This delay can be frustrating, especially if you're in urgent need of completing a transaction. Fortunately, there are methods to accelerate your Bitcoin transaction, ensuring it gets confirmed faster. One such method is using Child-Pays-for-Parent (CPFP) technique.

What is CPFP (Child-Pays-for-Parent)?

CPFP is a method used to prioritize the confirmation of a Bitcoin transaction by attaching a high fee to a related transaction. When a Bitcoin transaction is created, it often includes multiple inputs and outputs. If one of these transactions is unconfirmed due to a low fee, CPFP allows users to create a new transaction that spends the unconfirmed output of the original transaction.

Miners are incentivized to include both the original (parent) transaction and the new (child) transaction in the same block because the combined fees from both transactions are higher than those of individual transactions. This method is particularly useful when the sender of a transaction urgently needs it to be confirmed and is willing to pay a higher fee to expedite the process.

In summary, CPFP is a valuable tool for accelerating Bitcoin transactions, especially in situations where time is of the essence. By attaching a high fee to a related transaction, users can incentivize miners to prioritize the confirmation of both transactions, ensuring faster processing on the blockchain network.

Accelerating Transactions in inabit

inabit utilizes the CPFP technique to accelerate Bitcoin transactions for its platform wallets. (inabit native wallets).

Everytime there's a Bitcoin transaction being broadcasted, you can accelerate the transaction through the transaction's page.

Accelerate transaction button

Note that accelerating Bitcoin transactions will require an additional approval (For the accelerated transaction) as well as a charge higher fee than a regular Bitcoin transaction.

Trusted Execution Environment (TEE)

What is a UTXO?

UTXO stands for Unspent Transaction Output, and it's a fundamental concept in cryptocurrencies
like Bitcoin.

Every transaction output in the Bitcoin blockchain that has not been spent yet is considered an unspent transaction output (UTXO). Each UTXO has an associated value (the amount of bitcoins) and a locking script, which specifies the conditions under which the bitcoins can be spent (usually by providing a public key or a script that corresponds to a private key).

What is UTXO Consolidation?

If you regularly run operations on the Bitcoin blockchain, you will likely notice that the list of UTXOs in your wallets grows very quickly. This can be a major problem for retail-facing operations.

A process utilized by most companies is "consolidating UTXOs", or creating a transaction that will take many small unspent UTXOs and turn them into a single larger UTXO (Consolidated UTXO).

UTXO Consolidation in inabit

Every UTXO created from your transactions in Bitcoin or example, is saved in a database table with all UTXO relevant data (such as UTXO amount, is_spent flag, etc.)

inabit developed a unique logic to calculate which UTXOs should be used to send a transaction in Bitcoin, instead of registering a new UTXO from a new transaction.

By applying this logic, inabit takes another step forward towards optimizing Bitcoin transactions, making them much more efficient.

In crypto, Disaster Recovery (DR) involves plans and procedures to restore and access digital assets after major disruptions (disasters) like cyberattacks or hardware failures. It includes backup systems, security measures, geographic redundancy, testing, communication plans, and regulatory compliance to ensure the safety and availability of assets in emergencies.

inabit - being a self-custody wallet solution, offers the option to recover digital assets from its wallets.

Disaster Recovery in inabit

inabit offers an organization-based disaster recovery (DR).

In order to fully execute a truely self-custody recovery solution and ensuring the safety of the sensitive files (such as the encrypted wallet.dat file - the file in which all of the mnemonic seed phrases are held encrypted), inabit chose to partner with Vaultinum.

About Vaultinum

Vaultinum is a trusted independent third party specialized in the protection and audit of digital assets.

Since 1976, they have enabled thousands of digital creators, digital businesses and tech investors secure their innovations by providing solutions to:

• Protect their Intellectual Property with IP Deposit and IP Audit.
• Ensure the continuity of their business activity with Software Escrow.
• Mitigate cyber and software risks through in-depth Technology Due Diligence (KYS-Know Your Software).
• Create an unforgeable proof of date and time of event with our Certified Time-stamping solution.

With secure servers based in Europe, ISO 27001 certification, and a unique double expertise in IT and legal, their clients benefit from the highest levels of security and protection for all their sensitive assets.

inabit's Disaster Recovery guide using our Keys Recovery Tool

The following utility provides you with a simplified approach to generating a recovery package enabling you the ability to recovery your organization's keys in case of a disaster.

WARNING:

You should never perform this procedure unless a disaster event has occurred and you need to extract your private keys/mnemonic phrases. This procedure decrypts your encrypted keys and will revoke access to the organization!

In order to begin using inabit's recovery tool, you'll need to extract the following files:

1. Encrypted Master Key
2. Encrypted Wallets Key
3. Encrypted Password (for Wallets Key file)

Recovery Flow Steps

The flow of recovering your all of your organization's mnemonics, is split between two parts:

1. Issuing disaster recovery through inabit's platform (as the account Owner) and downloading the recovery package from the mobile application.
2. Extracting the walletKey file from Vaultinum.
3. Decrypting the mnemonics file using all three files.

In this page we'll go over the recovery flow and all three steps above.

What's a "Backup Email"?

A backup email, or what we also call "Recovery Email" is the owner's set email for disaster recovery. This is set by upgrading an organization's security level via the owner's settings.

Once there's a request to set a backup email, our support team is contacting the owner in order to define a specific email address to serve as "backup"/"recovery". (this email will receive the encrypted password file from Vaultinum) (See below for further).

Step 1: Extract the Recovery Package

Let's begin by explaining the first step of your recovery - Extracting the Recovery Package for your organization:

• As the account owner, make sure you're set on the organization you wish to perform the DR in. Once you've confirmed you're on the right organization, go to your "Settings" tab at the bottom left of your screen.
• At the bottom of the "Settings" page, you'll find a red button mentioning: "Issue Disaster Recovery" - click on it and go through your user 2FA to confirm the action.
• Once you've issued the request, you'll receive a notification to your mobile device (inabit mobile app). You will need to approve the request in the app.
• After approving the request, the screen will display a Download Recovery Package button where you'll need to download the recovery_package.zip file to a secured location (wether if its your email, any folder you have on your mobile that's secured by your PIN/strong password, or you can also share the file to your desktop and save it on a secured location there - it's your call.
• Make sure to unzip the file in order to fetch all three files from the package: Encrypted master key, encrypted wallets key, a disaster recovery guide pdf.

✅ Great news! You've finished step 1 of your recovery flow! Move on to the next step below.

Step 2: Extract Encrypted Password from Vaultinum

Step two of the recovery flow is explained as follows:

• The account owner requests to extract the walletKey from Vaultinum,
• Vaultinum then initiates a KYC verification that the owner (individual) must complete.
• Once the verification process is completed, Vaultinum sends the encrypted password file to the owner's recovery/backup email.

✅ Great news! You've finished step 2 of your recovery flow! Move on to the next step below.

Step 3: Decrypt Mnemonics File Using All Files

Prerequisite Checklist
Here's the full checklist of prerequisites you'll need before you can use our Python-based
Keys Recovery Tool.

• The owner issued Disaster Recovery in their platform settings. (for the specific organization)
• Owner approved the DR request on their mobile app.
• Owner downloaded the recovery_package.zip file from the mobile to a secured location and unzipped the package.
• Owner contacts Vaultinum and successfully goes through a KYC process.
• Owner recovers the Wallet Keys encrypted password file from his backup email.

Done with the above? You're ready to use our python-based keys recovery tool! ✔️

Using The Tool to Decrypt The Mnemonics:

inabit developed a self-service recovery tool to recovery your wallets' keys (mnemonic seed phrases).

The tool we provide is Python-based Keys Recovery Tool in our GitHub repository. (It will require basic knowledge of how to run code in Python)

Instructions on how to use the tool are provided in the repository's README.md file. The repository is public and can be viewed by anyone.

If instructions are still unclear, feel free to reach out to us for help: support@inabit.com.

🔑 inabit Keys Recovery Tool