Glossary
Let's consider the following entities and terminology
PureFi Dashboard
The main frontend application which allows to partners managing PureFi Subscriptions and to users passing KYC (PoH) verifications
PureFi Issuer
The main backend application that is responsible for issuance and verification of user credentials
PureFi Subscription
Subscription is determined by owner and chain. In other words, if you need to support two diffirent chains you have to have two subscriptions and manage them on each chain separately, Subscription Owner must be another EOA
Subscription Owner
It's EOA that holds a subscription and is responsible for its management via PureFi Dashboard
Resolver
It's a smart contract that implements particular interface, so resolve() method will be invoked during user verification process and the result of the call will let Issuer know if a user is allowed to perform an action from your (Resolver) perspective or not. You can think of it as of ultimate blocklist/whitelist feature that is managed by this contract
Custom Signer
In basic scenario it's EOA that is in charge to sign messages on your behalf, so Issuer will trust it
Environment
There are two major environments at the moment - STAGE and PROD
Each environment is determined by chains it supports, issuer and corresponding dashboard
STAGE
Chains
- Sepolia
- Polygon Amoy
- Optimism Sepolia
- Arbitrum One Sepolia
- Base Sepolia
- BSC Testnet
- Avalanche Fuji
Dashboard https://stage.dashboard.purefi.io
Issuer https://stage.issuer.app.purefi.io
Issuer swagger https://stage.issuer.app.purefi.io/swagger
PROD
Chains
- Ethereum
- Polygon
- Optimism
- Arbitrum One
- Base
- BSC
- Avalanche
Dashboard https://dashboard.purefi.io
Issuer https://issuer.app.purefi.io
Issuer swagger https://issuer.app.purefi.io/swagger