Chris Pollett > Students >
Mayuri

    ( Print View)

    [Bio]

    [Blog]

    [C297 Proposal]

    [Bitcoin Slides-pdf]

    [Deliverable 1]

    [Deliverable 2]

    [Deliverable 3]

    [Deliverable 4]

    [CS 297 (PDF)]

    [CS 298 Proposal]

    [Deliverable 5]

    [Deliverable 6]

Deliverable 6

Tracking and updating the credit score in the Credit Bureau Smart Contract

Mayuri Shimpi (mayuripraveen.shimpi@sjsu.edu)

The Credit Bureau Smart contract

In the ALOE system [1], client anonymity is preserved, while their credit score is openly linked to their Ethereum address. The process initiates with a registration phase, where an initial credit score is allocated to an Ethereum address according to the client's real-world credit score. Upon the creation of a new loan, borrowers and lenders engage to either request or invest funds. Once the loan amount garners adequate demand from borrowers and sufficient investment from lenders, the loan terms come into effect.

The Credit Bureau Smart Contract (CBSC) maintains a mapping linking Ethereum addresses with corresponding credit scoring data. This supplementary data includes the credit score linked with the hashed identity, a timestamp marking when this linkage was established, and a position in our credit scoring spectrum. The CBSC facilitates the connection between lenders and borrowers, monitors loan transactions and repayments, and manages updates to the borrower's credit score. Exclusive authority to invoke specific methods of this smart contract rests with the notary.

In this deliverable, I have implemented the updateScoreBorrow, updateScoreRepayment, and update the getScore methods as described below: