-
Notifications
You must be signed in to change notification settings - Fork 4
/
index.html
executable file
·289 lines (255 loc) · 8.72 KB
/
index.html
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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title></title>
<link rel="stylesheet" href="/styles/shared.css">
</head>
<style>
html, body {
overflow-x: hidden;
}
body {
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";
margin-left: 1em;
}
@media (min-width: 980px) {
body {
margin-left: calc((100vw - 780px)/2);
}
}
#mainNavigation {
position: absolute;
top: 0;
right: 0;
text-transform: uppercase;
font-weight: 300;
}
#mainNavigation a:visited, #mainNavigation a {
color: black;
}
#mainNavigation > ul {
padding: 0;
display: flex;
flex-wrap: wrap;
justify-content: center;
list-style: none;
}
#mainNavigation > ul > li {
padding-right: 1em;
}
</style>
<header>
<h1><a href="/">Quorum Explorer</a></h1>
</header>
<nav id="mainNavigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/api">API</a></li>
<li><a href="/organizations">Organizations</a></li>
<li><a href="/health">Health</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>
<style>
x-pages > *:not([active]) {
display: none;
}
</style>
<x-pages>
<validator-page route="/validators/:id"></validator-page>
<organization-page route="/organizations/:id"></organization-page>
<health-page route="/health"></health-page>
<x-page id="home" route="/" default>
<p>
The Stellar Core network depends on validators to ensure liveness and reliability.
Operating on the Stellar Core network means putting trust in a set of validators,
also known as a quorum set. Any organization or individual can run a validator,
thus leveraging their reputation and computing resources to reinforce the network.
</p>
<p>
As the operator of a validator, as the operator of an interface to the Stellar
Core network (such as Horizon) or simply as an entity doing business on Stellar
it is important to be aware of which validators are trusted with ensuring the
health of the network.
</p>
<radial-connection-graph></radial-connection-graph>
<p>
As an introduction to organizations on the Stellar Core network, below is a list
and chart of the most trusted organizations on the network. Select one to
get more information about that organization.
</p>
<most-trusted-organizations></most-trusted-organizations>
<a class="callToActionLink" href="/organizations">Show all organizations</a>
</x-page>
<x-page id="organizations" route="/organizations">
<h2>Organizations</h2>
<ul id="organization-list">
</ul>
<h2>Nodes</h2>
<ul id="validator-list">
</ul>
</x-page>
<x-page id="about" route="/about">
<h2>
Topics
</h2>
<h3>Quorum picker</h3>
<p>This section should enable the visitor to pick a good set of validators.</p>
<p>
It should also help the visitor with selecting some preferred peers to strengthen
its chances of having a good network.
</p>
<h3>Network overview</h3>
<p>
This should answer a set of general questions:
</p>
<ul>
<li>Which validators are there?</li>
<li>What is their reliability?</li>
<li>How trusted are they?</li>
<li>How available are they?</li>
<li>How connected are they?</li>
</ul>
<h3>Node/Validator/Organization view</h3>
<p>
This should answer some questions about a specific entity.
</p>
<h2>Research</h2>
<h3>Trust Index</h3>
<p>
Quorum Explorer currently employs a crude estimate of the amount of trust
the network in general puts into a specific validator or organization. This
"trust index" number is just the amount of nodes that have this particular
validator in their quorumset, divided by the total amount of validators in
quorumsets. This number is not reliable for any decision, as it can easily
be gamed, it's just used to roughly order nodes.
</p>
<h3>
What is important when configuring a quorum set and a set of preferred peers?
</h3>
<p>
You want a quorum set that consists of as many validators that you trust as possible, and also
as diverse as possible, with a treshold so that a conspiracy would have to span as much
validators as possible, while still allowing for a maximum number of unreachable/unresponsive
validators.
</p>
<p>
This actually means that you want your quorumset to be the minimum amount of validators that
you would still trust to not have a conspiracy greater than the treshold.
</p>
<p>
The next question is which peers do we prefer. We want a group of peers that are reliably
available, and also that broadcast quorums that contain the validators we are interested in.
</p>
<p>
We receive externalize messages from our peers whenever they advance their ledgers. Associated
with the externalize messages are quorumset hashes. We use this quorumset hash to ask a peer
which members that quorumset has, and who the owner is of that quorumset.
</p>
<p>
If we receive a statement from a peer saying that it externalizes a message
by virtue a certain quorumset, how do we know it is correct? Is this pledges?
are they signed? The quorumset is signed by the message sender. This means we know that
whoever sent the quorumset believes that particular quorumslice voted for the value it
accepted.
</p>
</div>
</x-page>
<x-page id="api" route="/api">
<h2>API Documentation</h2>
<p>
The API can be found at <a href="https://api.quorumexplorer.com/v1">https://api.quorumexplorer.com/v1</a>.
</p>
<p>
The endpoints in this API simply return JSON documents that are continuously
refreshed by runs of a crawler.
</p>
<h2 id="doc-nodes-path">/nodes.json</h2>
<p>
This endpoint returns an object with basic information on all nodes that
are part of the Stellar Core network. For convenience there is also a list
of organizations, a total_trust amount which is used to relativize trust
amounts and a last_crawl_time which is the time the crawler generated this
data.
</p>
<p>
The root object is structured as follows:
</p>
<pre>
{
organizations: { id -> basic_organization },
nodes: { id -> basic_node },
total_trust: float,
last_crawl_time: integer
}
</pre>
<p>
View an example of the response to this endpoint
<a href="https://api.quorumexplorer.com/v1/nodes.json">here</a>.
</p>
<h3>nodes</h3>
<p>
This field is a map of node id to node. Node id is also known as the node
public key and can be used to uniquely identify a node. basic_info is a map
of node properties that leaves out some more data intensive fields.
</p>
<pre>
{
ledger_version: integer,
network_id: string,
overlay_min_version: integer,
overlay_version: integer,
peer_id: string,
version_string: string,
accepts_connections: boolean,
error: string | null,
address string,
known_info: known_info,
quorum: quorum,
account_info: account_info | null,
organization_name: string,
trust_table: trust_table,
trusting_nodes: [string],
trust_value: float,
organization_id: string,
last_seen: integer,
id: string,
quorum_history: [quorum]
accepts_connections_history: basic_accepts_connections_history,
seen_history: basic_seen_history
}
</pre>
<h3>organizations</h3>
<p>
This field is a map of organization id to node. Organization id's are a hash
of the organization name, in the same way as node id's are calculated by Stellar.
basic_organization is a map that leaves out some data intensive fields.
</p>
<pre>
{
id: string,
name: string,
validators: [string],
last_seen: integer
}
</pre>
</x-page>
</x-pages>
<!-- Load Babel Polyfills on all browsers that do not support modules (IE11, GoogleBot) -->
<script nomodule src="/babel-polyfill/dist/polyfill.js"></script>
<!--
Load the webcomponent polyfills for ShadowDOM, Custom Elements, and Platform Polyfills
(No-op on browsers that already have support)
-->
<script src="/node_modules/@webcomponents/webcomponentsjs/bundles/webcomponents-sd-ce.js"></script>
<span id="browser-sync-binding"></span>
<script src="/node_modules/d3/dist/d3.js"></script>
<script src="/node_modules/underscore/underscore.js"></script>
<!-- Load the module version of the app (bundled or unbundled) -->
<script type="module" src="/index.js"></script>
<!-- Load the ES5 compiled and bundled version of the app on browsers that do not support modules (IE11, GoogleBot) -->
<script nomodule src="/index.es5.js"></script>
<quorum-explorer-footer></quorum-explorer-footer>
</html>