#
KYC (Know-Your-Contract) Level System
Metapad's KYC Level System follows consensus-based approvals between the applicant and the KYC reviewer role. The leveling system is consists of 4 levels/tiers. These levels are applied on an in order basis.
From project owner's perspective, this is where they prove smart contracts and project ownership, establish more trust credibility scores to their users, and add more integrity to their projects.
For users, this tiering can be a guide to get informed and understand more about the project's smart contracts cans and risks.
Below are the levels/tiers list. The example is collected from https://testnet.metapad.dev/token/3.
#
KYC Level 1: Token Info
This refers to the project information and their respective smart contracts. Projects owners should enlist their project first and is subject for review.
KYC Level 1 shows the following information:
- Token Name
- Token Description
- Token Image
- Chain
- Creator Address (minter of the project Metapad token)
- Owner Address (current owner of the project Metapad token)
- Project Type
- Website
- Contract Addresses (with indicator if the Metapad token owner address matches the owner address of the project's contracts)
- Web Archive (Wayback Machine) of the project website during KYC Level 1 approval
Project owner can still edit KYC Level 1 details except the contract addresses section.
For upgradeable contracts or trying to add new contract to the project, project owner can enlist it as a new token instead.
Updating KYC Level 1 details is also subject for consensus-based approval. The Token's KYC level will be as is.
#
KYC Level 2: Contract Notes
Contract notes contains the contracts rules written now in user-friendly language (layman's term). Contract notes fees varies from contract to contract scope.
You can find the open-sourced list here listed by token:
https://github.com/Nuxify/metapad-contract-notes/tree/testnet
KYC Level 2 shows the following information:
- Reviewed contract addresses
- ERC standards used
- Contract summary in layman's term
- Contract user and owner functionalities, capabilities
- Contract owner cans and cannot
- Update time
- Contract notes GitHub link
Issues found in contract notes is directly filed, discussed, and addressed in the contract notes GitHub repository. Project owners or anyone can file issues there.
#
KYC Level 3: Contract Audits
Contract audits contains the contract audit reports from smart contract auditing companies. The audit reports are stored indefinitely in IPFS.
KYC Level 3 shows the following information:
- Audit reports from smart contract auditing companies
Audit reports can be updated following consensus-based approvals.
The Metapad team also offers smart contract auditing. You can hit us at [email protected]
#
KYC Level 4: Crews
Crews refers to the team members of the project. These are the brave souls that wanted to leave a strong footprints in their works and are doxxed.
All info here are public and stored in IPFS (referenced by the Metapad's contract).
KYC Level 4 shows the following information:
- Team members info (name, profile image, verified LinkedIn accounts)
- Team members video introduction video
Crews can be updated following consensus-based approvals.
Team members should have verified LinkedIn accounts as a requirement for approval.