Files
papers/lux-decentralized-cloud/sections/99-conclusion.tex
zeekay 4a753bb639 papers: reorganize into per-paper dirs, add Antje Worring as co-author
Restructured from flat .tex/.pdf files into per-paper subdirectories.
Added Antje Worring as co-author on all papers.
Synced PDFs to pdfs/ for download site.
2026-04-18 21:50:07 -07:00

84 lines
3.8 KiB
TeX

\section{Conclusion}
\label{sec:conclusion}
The centralized cloud model treats providers as data custodians who
extract rent from switching costs. The Lux provider model treats
providers as service markets competing on quality, with users retaining
ownership of their keys, their data, and their exit rights.
The key contributions of this paper are:
\begin{enumerate}
\item \textbf{Five-role provider taxonomy.} Relay, storage, gateway,
recovery, and compute as separable, composable service roles, none of
which require custodial access to user data.
\item \textbf{Surveillance-free reputation.} A provider reputation
protocol based entirely on verifiable on-chain signals---receipt
completion, stake tenure, slashing history, proof-of-service---that
requires no inspection of user traffic.
\item \textbf{Chain-enforced SLAs.} Service level agreements as smart
contracts with automatic stake-backed penalties, replacing the legal
fiction of centralized SLA credits.
\item \textbf{Resource markets.} Continuous double-auction markets
for inference, storage, bandwidth, recovery, and gateway services
with second-price settlement and EIP-1559-style dynamic pricing.
\item \textbf{Provable portability.} A formal proof that users can
switch providers with zero data loss and bounded downtime, even under
Byzantine fault assumptions.
\end{enumerate}
The decentralized cloud is not a replacement for AWS. It is a different
category of infrastructure: one where the user is sovereign, the provider
is a vendor, and exit is not a migration---it is a market transaction.
\begin{thebibliography}{99}
\bibitem{synergy2024cloud}
Synergy Research Group, ``Cloud infrastructure services market reaches \$76 billion in Q4 2024,'' \emph{Synergy Research Group Report}, 2024.
\bibitem{aws2021outage}
Amazon Web Services, ``Summary of the AWS service event in the Northern Virginia (US-EAST-1) region,'' \emph{AWS Post-Event Summary}, December 2021.
\bibitem{benet2017filecoin}
J.~Benet and N.~Greco, ``Filecoin: A decentralized storage network,'' \emph{Protocol Labs Technical Report}, 2017.
\bibitem{akash2020}
G.~Gadiraju and A.~Prem, ``Akash Network: Decentralized cloud compute marketplace,'' \emph{Akash Network Whitepaper}, 2020.
\bibitem{golem2016}
The Golem Project, ``The Golem Project: Crowdfunding whitepaper,'' \emph{Golem Factory Technical Report}, 2016.
\bibitem{iexec2017}
G.~Fedak et al., ``iExec: Blockchain-based decentralized cloud computing,'' \emph{iExec Whitepaper}, 2017.
\bibitem{kleppmann2019localfirst}
M.~Kleppmann, A.~Wiggins, P.~van~Hardenberg, and M.~McGranaghan, ``Local-first software: You own your data, in spite of the cloud,'' in \emph{Onward!}, ACM, 2019.
\bibitem{bernerslee2016solid}
T.~Berners-Lee, ``Solid: A platform for decentralized social applications based on Linked Data,'' \emph{MIT CSAIL Technical Report}, 2016.
\bibitem{shamir1979share}
A.~Shamir, ``How to share a secret,'' \emph{Communications of the ACM}, vol.~22, no.~11, pp.~612--613, 1979.
\bibitem{gennaro2020frost}
R.~Gennaro and S.~Goldfeder, ``One round threshold ECDSA with identifiable abort,'' \emph{IACR ePrint 2020/540}, 2020.
\bibitem{androulaki2008reputation}
E.~Androulaki, S.~G.~Choi, S.~M.~Bellovin, and T.~Malkin, ``Reputation systems for anonymous networks,'' in \emph{PETS}, Springer, 2008.
\bibitem{kerschbaum2009reputation}
F.~Kerschbaum, ``A verifiable, centralized, coercion-free reputation system,'' in \emph{ACM WPES}, 2009.
\bibitem{roughgarden2020eip1559}
T.~Roughgarden, ``Transaction fee mechanism design for the Ethereum blockchain: An economic analysis of EIP-1559,'' \emph{arXiv preprint arXiv:2012.00854}, 2020.
\bibitem{wood2016polkadot}
G.~Wood, ``Polkadot: Vision for a heterogeneous multi-chain framework,'' \emph{Polkadot Whitepaper}, 2016.
\end{thebibliography}