The aim of this document is to provide an overview of the BidiPass authorization platform (BDP) which employs blockchain technology, peer-to-peer two-layer security, HOTP algorithm, an SDK, biometric authentication mechanisms and other related technologies.
To reduce the size of this document, we will focus on unique features of the BDP platform that are essential to achieving its stated goals.
Introduction
BidiPass is an identity authentication protocol designed to strengthen the KYC model that global businesses depend on today. The BidiPass platform is a user-friendly, secure and reliable way to authorize actions within connected platforms (e.g. approving transactions on a trading platform) by using a two-layer security protocol that operates in a distributed, peer-to-peer manner.
This document is not intended to be the ultimate reference with respect to all the implementation details. Some particulars are likely to change during the development and testing phases.
Brief Description of BidiPass Components
The BidiPass platform consists of its blockchain, SDK and mobile applications.
The blockchain will the foundation of the BidiPass platform and will be used to issue, confirm and keep track of Authorization Requests on its ledger. The Authorization Requests will contain information about the actions and timestamps of interactions (e.g. triggered, confirmed), unique OTP codes generated using HOTP algorithm [2] and the reasons for declines when necessary.
The SDK, designed and distributed through BidiPass, will include a library written in several programming languages (e.g. JavaScript [NodeJS], PHP, etc.) that can be easily connected to the Providers’ software and used to interact with both the blockchain and the users’ mobile devices.
It will also be able to validate OTP codes using the HOTP algorithm. This will provide a simpleto-use interface that will speed up development and ensure that best practices are being used.
The SDK will have comprehensive documentation for developers that clearly outline the end-toend integration process.
Mobile applications will be distributed through the official Android and iOS marketplaces, and will be used to connect BidiPass to Provider platforms and Identities (users) in order to authorize requests using the BidiPass software. This will feature a simple and user-friendly UI with seamless access to the platform. Through this, users will be able to view and approve new authorization requests with only a few steps: click “approve” or “reject” and confirm each transaction by using the fingerprint or facial recognition mechanism through the device and/or mobile platform.
techpaper