Skip to content

Commit b876825

Browse files
committed
docs: Update the reputation-based trust system
1 parent e5773c2 commit b876825

File tree

2 files changed

+35
-5
lines changed

2 files changed

+35
-5
lines changed

docs/whitepaper/math_model.tex

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
\section{Incentive Analysis for Malicious Behavior in Decentralized Systems}
2+
\label{sec:math_model}
23

34
\subsection{Introduction}
45

docs/whitepaper/proposed_solution.tex

Lines changed: 34 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,45 @@ \subsubsection{Decentralized Infrastructure}
1515

1616
\subsubsection{Reputation-Based Trust System}
1717
\label{subsec:reputation_system}
18-
Unlike typical Web3 solutions that rely on consensus mechanisms, our platform implements a robust reputation system:
18+
19+
Unlike typical Web3 solutions that rely on consensus mechanisms to mitigate the Byzantine Fault Tolerance (BFT) problem --- allowing up to 50\% (or a bit less on some platforms) of the network to be malicious --- our platform takes a different approach. We primarily rely on conventional legal contracts and Service Level Agreements (SLAs), supplemented by a robust blockchain-tracked reputation system. This dual approach ensures accountability through traditional means while providing an additional layer of trust and transparency.
20+
21+
In the anonymous blockchain space, an actor is more likely to behave maliciously than in the real world. In the real world there is a lot more at stake than in the blockchain space, an actor would be much less likely to behave maliciously, given that they risk suffering both legal and financial consequences for malicious behavior. Malicious behavior may still occur, but the potential benefit of such behavior needs to clearly compensate the potential cost, which may come in the form of a loss of the long-term financial benefit and the potential financial loss in the following legal processes, as analyzed in more details in Section~\ref{sec:math_model}.
22+
23+
Decent Cloud is designed with this in mind, and it focuses on incentivizing honest behavior and providing high-quality service while implementing mechanisms to penalize poor performance or malicious actions. Good reputation is hard to earn, and it's easy to lose. Especially if big clients (with high reputation) are dissatisfied with the provided services.
24+
25+
\paragraph{Building Reputation:}
26+
Node providers and developers accrue reputation through successful transactions and positive interactions on the platform:
27+
1928
\begin{itemize}
20-
\item Node providers and developers build and maintain long-term reputations
21-
\item Users can select providers based on their track record of reliability and performance
22-
\item The system incentivizes honest behavior and high-quality service
29+
\item Each completed transaction between a developer and a node provider results in a 2\% transaction fee, from which there is a 1\% increase in both parties' reputation scores.
30+
\item Consistent user satisfaction contributes to gradual reputation increases of node providers over extended periods and numerous transactions.
31+
\item Developers who rent many resources or spend significant amounts over longer periods of time will have higher reputation scores than those who do not.
2332
\end{itemize}
2433

25-
This approach addresses the trust and security concerns associated with decentralized systems while maintaining the performance advantages of traditional cloud services.
34+
\paragraph{Reputation Dynamics:}
35+
Our system introduces an innovative approach to managing reputation:
36+
37+
\begin{itemize}
38+
\item Both node providers and developers build reputation through successful transactions.
39+
\item Rather than complicating the platform to autonomously track and judge honest behavior, we empower users to report and penalize malicious behavior.
40+
\item If dissatisfied with a service or collaboration, a user can choose to reduce another party's reputation. This action comes at a cost: the sender's reputation decreases by the amount spent, while the receiver's reputation decreases by a higher amount, such as 200%.
41+
\end{itemize}
42+
43+
This mechanism offers several advantages:
44+
45+
\begin{itemize}
46+
\item Robustness: It's straightforward to implement and reason about.
47+
\item Quality Incentive: It motivates node providers to maintain high-quality service and prioritize user satisfaction.
48+
\item Resilience against Malicious Actors: Malicious node providers would quickly acquire poor reputations, limiting their ability to attract new users. Similarly, malicious developers quickly lose power to hurt the reputation of others, as they lose their own reputation in the process.
49+
\end{itemize}
50+
51+
\paragraph{Reputation System Impact:}
52+
53+
This dynamic reputation system empowers users to make informed decisions when selecting node providers. It addresses trust and security concerns associated with decentralized systems while preserving the performance advantages of traditional cloud services. All reputation scores are publicly visible and immutably recorded on the blockchain, ensuring transparency and creating a reliable history of interactions and service quality.
2654

2755
\subsubsection{Efficient Resource Allocation}
56+
2857
Our platform can be used to ensure optimal resource allocation. For instance:
2958
\begin{itemize}
3059
\item Task requirements can be matched with available node resources in real-time

0 commit comments

Comments
 (0)