Introduction

Specification

Data services

Credit record storage

Credit record storage provides decentralized storage of the self-sovereign credit record (SSCR) of the users. Each record represents a unique global decentralized identity and contains general-purpose and protocol-specific verifiable credentials. The credentials data is encrypted and accessible only by the identity owner.

The SSCR contains both hard information (facts such as credit score and history, debt-to-income ratio, bank account verification, and business financial indicators) and soft information (such as endorsement, community membership, and self-declared business plans) that are used in the credit risk assessment.

Potential types of verifiable credentials to be stored in the SSCR include:

Credential category Type Proof Description
KYC hard identity proves a successfully passed KYC process (including AML/CFT risk check)
Financial data hard creditworthiness shows the financial habits of the user, as well as the trends in his cash flow (eg. transaction history, products)
Savings history hard creditworthiness proves the financial discipline of the user (eg. regular micro-payments)
Credit history hard creditworthiness & trustworthiness proves the financial discipline of the user (eg. past loans from the protocol)
Business activity hard creditworthiness proves past and future revenue (income statement, cash flow, balance sheet)
Ownership hard creditworthiness proves the ownership of assets required for achieving the goals (eg. land, machines, raw materials)
Community membership soft reputation asserts the trust of the organization
Social endorsement soft reputation asserts the trust of other protocol participants having a certain reputation level
Financial health soft trustworthiness proves successfully passed financial education or mentoring

Local data services

Some of the Growr services require database collections storing editable and manageable data locally in the node. This data usually does not contain lending or funding events and is not required to be distributed in the network (eg. user registration and onboarding). The collections can be implemented in MongoDB or other NoSQL databases.

The Growr protocol’s local collections are:

Distributed data services

For storing and distributing project lending and funding data, Growr is using Holepunch’s Hyperbee, an append-only B-tree based on Hypercore. It provides a key-value data store that is both fast and efficient, making it good for storing large amounts of data in a decentralized network. Additionally, it supports peer-to-peer synchronization, allowing the data to be replicated across the network in a highly efficient and fault-tolerant manner.

In addition, read-only copies are created and contain aggregated data plus audit logs, sanitized from any personal-revealing data. This data is publicly exposed to ensure transparency in the network and to monitor its global impact. Those read-only copies are implemented as a Hyperswarm with published well-known Public Key and Topic.

The Growr protocol’s distributed data logs are: