This repository has been archived by the owner on Jan 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathmain.tex
92 lines (80 loc) · 3.32 KB
/
main.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
\documentclass[11pt,a4paper]{article}
\input{mypackages}
\input{mystyle}
\input{sections/glossary}
\graphicspath{{figs/}}
\newcounter{myCounter}
\begin{document}
\title{\ipcFull (\ipc)\thanks{\url{https://ipc.space}}}
\date{}
\author{ConsensusLab\thanks{\url{https://consensuslab.world}}}
% \authornote{Both authors contributed equally to this research.}
% \orcid{1234-5678-9012}
% \author{G.K.M. Tobin}
% \authornotemark[1]
%\email{sgoren@campus.technion.ac.il}
% \orcid{https://orcid.org/0000-0003-2158-161X}
% \affiliation{%
% \institution{Technion}
% \country{Israel}
% }
\maketitle
\begin{abstract}
Totally ordering transactions constitutes a
significant scalability bottleneck standing in the way of massive adoption of
blockchain systems, as all participants need to replicate and execute sequentially every single transaction. Layer 2 (L2) protocols aim at resolving this scalability
limitation by off-loading state and processing to a loosely coupled sub-system.
We present \ipcFull (\ipc), a new blockchain
architecture design that enhances the scaling capabilities of L2+
protocols. Users of \ipc can dynamically spawn new blockchain subsystems
(subnets) as children of any existing subnet. \ipc is based on the design principles of
on-demand horizontal scaling. Child subnets leverage the
security of their parent subnets by periodically checkpointing their state in the parent's state.
\ipc provides native communication across
subnets within the \ipc framework.
We believe that \ipc addresses several issues with existing L2 approaches,
including limited throughput capacity, isolation from each
other, centralized components, or monolithic architectures.
% We believe, however, that \ipc's flexible architecture could be implemented in
% conjunction with many of these orthogonal solutions.
In the following, we introduce the overall system architecture, native functionality,
and design decisions of our reference implementation for child
subnets based on the BFT Trantor consensus protocol, with Filecoin as
rootnet.
\end{abstract}
% ----------------------------------------------------------------
% ----------------------------------------------------------------
\input{sections/introduction}
\input{sections/example-use-case}
\input{sections/preliminaries}
\input{sections/functionality}
\input{sections/components}
\input{sections/related-work}
\input{sections/ref-impl}
\input{sections/conclusion}
% ----------------------------------------------------------------
% ----------------------------------------------------------------
%%
%% The next two lines define the bibliography style to be used, and
%% the bibliography file.
\bibliographystyle{plain}
\bibliography{bibliography}
%%
%% If your work has an appendix, this is the place to put it.
\appendix
% ----------------------------------------------------------------
% ----------------------------------------------------------------
\newpage
\printglossaries
% \input{sections/appendix.tex}
% \input{sections/algorithm.tex}
% \input{sections/QvW.tex}
% \input{sections/Yao.tex}
% ----------------------------------------------------------------
% ----------------------------------------------------------------
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}
\endinput
%%
%% End of file