Paul Kiage commited on
Commit
75eb02f
·
unverified ·
1 Parent(s): 37c732e

include defi open problems in PESTLE

Browse files
Files changed (1) hide show
  1. README.md +10 -0
README.md CHANGED
@@ -128,3 +128,13 @@ Other:
128
  >* Clear and adequate information to the user;
129
  >* Appropriate human oversight measures to minimise risk;
130
  >* High level of robustness, security and accuracy."
 
 
 
 
 
 
 
 
 
 
 
128
  >* Clear and adequate information to the user;
129
  >* Appropriate human oversight measures to minimise risk;
130
  >* High level of robustness, security and accuracy."
131
+
132
+
133
+ [A list of open problems in DeFi](https://mirror.xyz/0xemperor.eth/0guEj0CYt5V8J5AKur2_UNKyOhONr1QJaG4NGDF0YoQ?utm_source=tldrnewsletter)
134
+ * Automated risk scoring of lending borrowing pools -> Increasingly important problem
135
+ * 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.
136
+ * Managing Risk for lenders and distributing risk/ Undercollateralized Loans
137
+ * Tradfi is plagued by NPAs 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].
138
+ * 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]
139
+
140
+