Database Specs
Technical documentation on how I-AM-HUMAN SUPABASE DATABASE works
We use PostgresSQL for storing all the user data for our app. Right now we have 3 tables in our app and their purpose and functionalities are specified below
DATABASE SCHEMA
USERS TABLE
This table stores all the information relating to a user . The DB has the following schema and each column has a specified meaning relating to it as defined below
id
Unique ID assigned to each user on creation
wallet-identifier
Near Wallet address of the user
created_at
Date on which user got created
fv_token_id
Token ID of Face Verification token issued to user
fv_issued_date
Issued data of Face Verification token
fv_expire_date
Expiry date of Face Verification token
fv_status
Status of user's requested Face Verification Token. It's value can be:
og_tokens_metadata
An object containing all the information about all types of OG Tokens issued to user including the class, token_id, issued_date, expire_date
EVENTS TABLE
Logs all user actions that a user takes inside the app. It helps us to track errors. The DB has the following schema and each column has a specified meaning relating to it as defined below
id
Unique ID assigned to each event on creation
created_at
Date on which action got recorded
wallet-identifier
Near Wallet address of the user who's action was logged
event_log
Action the user took
SUPER_ADMINS TABLE
Has a list of all the superadmins that PII (Personally Identifiable Information) is visible to. The DB has the following schema and each column has a specified meaning relating to it as defined below
id
Unique ID assigned to each admin on creation
created_at
Date on which super-admin got recorded
wallet-address
Near Wallet address of the superadmin
Last updated