PHAETON IDENTITY — PART 2
A Dive into Phaeton Protocol Identity Solution
The Phaeton platform has an ecosystem offering users access to a decentralised global market. Its sidechains allow independent dApps, facilitating customisation, scalability, and a departure from high network fees providing multiple benefits for the users. The protocol has been designed to make it convenient, secure, seamless for all stakeholders. Let us dive into the Phaeton Identity creation, validation, and other aspects of the Phaeton protocol.
PROTOCOL USERS
When it comes to the users on the protocol, they can be segregated into three types:
1. Individual users — these are individual users who join the Phaeton protocol.
2. Claim verifiers are protocol admins or third-party users who verify or corroborate the claim issued by the individual users.
3. Administrators — these are the users whose role is to administer the protocol.
IDENTITY LEVELS
Phaeton protocol has several Identity Levels based on the claims:
Level 1: Cryptographic Identity constitutes Level 1 of the identity mechanism. Level 1 on Phaeton protocol includes wallet keys, email id, phone no., and national identity. Facial recognition and liveness checks are conducted through a 3rd party.
Level 2: Address Verification makes up this level.
Level 3: This level includes other personal credentials such as health records, academic certificates, government credentials, etc.
DECENTRALISED IDENTITY PROTOCOL
Phaeton has put in place a decentralised identity protocol that constitutes the following steps:
1. User Onboarding
The user will create a Phaeton Wallet key pair or use an existing Phaeton Wallet in this phase. The public key will constitute the cryptographic identity of the user, while the private key is used to authenticate their activities on the protocol. The wallet uses a password to encrypt and safely store keypairs. This password is required to sign a transaction or export keys. The user will provide an email address and phone number verified using OTP (one-time-password). The verification timestamp will become part of the verified claim. The user will give real-world identity-related information in claims like National Identity document and Address Verification document, etc. The Admin will confirm the identity, and the verification timestamp and Admin signature will become part of the verified claim. For facial recognition and liveness check, a third-party integration will take place. The user will provide a selfie or video snippet for verification.
2. Claims Management
The user will provide various data points that will constitute identity claims. Each claim will need to be verified using either digital means or through manual verification. Each verified claim will become part of the Identity smart contract. The documents will be stored off-chain using decentralised storage. The document hashes are held in the smart contract. The user’s decentralised identity will be ready for use to sign the transactions wherever identity verification is required.
3. Claims Verification
KYC Verification will be done via the cryptographic identity, verified digitally by connecting the wallet to the dApp. The Email Id is verified digitally through OTP. The National Identity will be verified either by a designated official from the admin panel. The Address Proof will be verified either by a designated official from the admin panel. If the National Identity used has a time-based expiry, the system will send prior notifications to ensure the documents are up to date in the system.
ADMIN FEATURES
The administrator panel on the Phaeton protocol will have the following features:
a. Admin Login — the Admin user will have pre-defined login credentials with the option to set up 2-Factor Authentication for logging into the dashboard. Admin can access various features of the application from the dashboard.
b. Admin Users and ACL (Access Control List) Module — the Admin can create multiple admin users with different roles and permissions.
c. User Management — the Admin would be able to manage the various types of users on the platform.
d. Manage Master Data — the Admin user will manage the master data for a different type of discrete data.
e. KYC (Know Your Customer) Verification — the Admin user can view and approve the KYC verification status of the users on the platform.
ADDRESS SYSTEM IN PHAETON ECOSYSTEM
In Phaeton, the user must initially choose a 12-word passphrase to create an address for creating a new account. Blake3 hashes this passphrase into a 256-bit string used as the seed to spawn both the private and public keys using the Ed25519 signature scheme. After that, a final step transforms the public key into the address. The address format has been designed to make it convenient for users when communicating their address.
WRAPPING UP
Ownership, identification, and trust in blockchain ecosystems are funnelled by controlling private keys, designing address systems, and remote key management systems. Admin features support the efficiency of the mechanism. Address system has been designed to boost security as well as convenience. It enhances security and adds a significant layer of trust to the package.
More information at https://phaeton.io