Spaces:
Build error
Build error
Merge branch 'master' of https://github.com/pkiage/tool-credit-risk-modelling
Browse files
README.md
CHANGED
@@ -61,10 +61,10 @@ python setup.py install
|
|
61 |
streamlit run app.py
|
62 |
|
63 |
## Deployed setup details
|
64 |
-
For faster model building and testing (particularly XGBoost) a local setup is recommended.
|
|
|
|
|
65 |
|
66 |
-
Free Heroku dyno type was used to deploy the app
|
67 |
-
https://devcenter.heroku.com/articles/dyno-types
|
68 |
|
69 |
|
70 |
Memory (RAM): 512 MB
|
@@ -181,3 +181,11 @@ code2flow src/models/util_predict_model.py -o docs/call-graph/util_predict_model
|
|
181 |
```shell
|
182 |
code2flow src/models/util_model_comparison.py -o docs/call-graph/util_model_comparison.svg
|
183 |
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
61 |
streamlit run app.py
|
62 |
|
63 |
## Deployed setup details
|
64 |
+
For faster model building and testing (particularly XGBoost) a local setup or on a more powerful server than free heroku dyno type is recommended. ([tutorials on servers for data science & ML](https://course.fast.ai))
|
65 |
+
|
66 |
+
[Free Heroku dyno type](https://devcenter.heroku.com/articles/dyno-types) was used to deploy the app
|
67 |
|
|
|
|
|
68 |
|
69 |
|
70 |
Memory (RAM): 512 MB
|
|
|
181 |
```shell
|
182 |
code2flow src/models/util_model_comparison.py -o docs/call-graph/util_model_comparison.svg
|
183 |
```
|
184 |
+
[A list of open problems in DeFi](https://mirror.xyz/0xemperor.eth/0guEj0CYt5V8J5AKur2_UNKyOhONr1QJaG4NGDF0YoQ?utm_source=tldrnewsletter)
|
185 |
+
* Automated risk scoring of lending borrowing pools -> Increasingly important problem
|
186 |
+
* One alternative way of looking at the problem would be, looking at a function for calculating the probability of default given the pool of assets you have.
|
187 |
+
* Managing Risk for lenders and distributing risk/ Undercollateralized Loans
|
188 |
+
* Tradfi is plagued by NPAs [(Nonperforming assets)] but still ultimately fall back to some sort of credit score establishment [[Spectral finance](https://www.spectral.finance/) solving this, but still an open problem].
|
189 |
+
* But still, most credit score methods would rely on onchain history for credit establishment, we are moving towards privacy-centric defi is this approach extendable to that idea? [Homomorphic encryption could provide a solution]
|
190 |
+
|
191 |
+
|