Repository navigation
Expand file tree
/
Copy pathglossary.html
More file actions
225 lines (222 loc) · 9.03 KB
/
Copy pathglossary.html
File metadata and controls
225 lines (222 loc) · 9.03 KB
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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>Glossary — SatCode</title>
<meta name="description" content="SatCode’s domain language, in plain terms." />
<meta name="theme-color" content="#0a0a0a" />
<link rel="stylesheet" href="style.css" />
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<header class="site-header">
<div class="header-inner">
<a class="wordmark" href="index.html">
satcode
<span>.</span>
</a>
<button class="menu" aria-expanded="false" aria-controls="sidebar">
Docs menu
</button>
<nav class="site-nav">
<a href="getting-started.html">How it works</a>
<a href="glossary.html">Glossary</a>
<a href="faq.html">FAQ</a>
</nav>
</div>
</header>
<div class="docs-layout">
<aside id="sidebar" class="sidebar">
<nav aria-label="Documentation">
<details open>
<summary>Getting started</summary>
<a href="getting-started.html">How SatCode works</a>
<a href="roles.html">Roles & responsibilities</a>
<a href="agents.html">Who is SatCode for?</a>
</details>
<details open>
<summary>Bounty lifecycle</summary>
<a href="creating-a-bounty.html">Define & negotiate</a>
<a href="funding-escrow.html">Fund escrow</a>
<a href="submitting-work.html">Submit & settle</a>
<a href="resolving-disputes.html">Resolving disputes</a>
</details>
<details open>
<summary>Architecture</summary>
<a href="architecture.html">System architecture</a>
<a href="escrow.html">Escrow & settlement</a>
<a href="dispute-resolution.html">Dispute resolution</a>
<a href="trust-model.html">Trust model</a>
<a href="bitcoin-enforcement.html">Bitcoin enforcement</a>
</details>
<a class="side-single" href="glossary.html">Glossary</a>
<a class="side-single" href="faq.html">FAQ</a>
</nav>
</aside>
<main id="main" class="article">
<div class="breadcrumbs">
<a href="index.html">Home</a>
<i>/</i>
<span>Reference</span>
</div>
<header class="article-head">
<p class="kicker">Reference</p>
<h1>Glossary</h1>
<p>SatCode’s domain language, in plain terms.</p>
</header>
<div class="article-body">
<div class="glossary">
<article>
<h2>Arbiter</h2>
<p>
The k-of-n juror or oracle threshold that
co-signs a disputed settlement; never one key.
</p>
</article>
<article>
<h2>Ark</h2>
<p>
A Bitcoin protocol for off-chain virtual UTXOs
settled in rounds.
</p>
</article>
<article>
<h2>ArkadeOS</h2>
<p>
Ark Labs’ Ark implementation and SDK used by
SatCode for escrow.
</p>
</article>
<article>
<h2>Ark Operator</h2>
<p>
The Ark server run by Ark Labs. It co-signs
rounds and enforces SDK policy, but cannot spend
escrow alone.
</p>
</article>
<article>
<h2>Bounty</h2>
<div>
<p>
A signed offer of bitcoin for work under
declared terms. A bounty can be in the following
states:
</p>
<ul>
<li>
<strong>open</strong>
= published but not funded,
</li>
<li>
<strong>in progress</strong>
= funded and work has started,
</li>
<li>
<strong>claimed</strong>
= completed (taker has been paid), or
</li>
<li>
<strong>in dispute</strong>
= maker and taker do not agree on payout
</li>
</ul>
</div>
</article>
<article>
<h2>Escrow</h2>
<p>
The four-leaf Taproot vTXO that constrains
settlement.
</p>
</article>
<article>
<h2>Juror</h2>
<p>
A bonded participant who reviews evidence,
votes, and signs a human-mode outcome.
</p>
</article>
<article>
<h2>Juror bond registry</h2>
<p>
The public set of eligible jurors and their bond
vTXOs.
</p>
</article>
<article>
<h2>Maker</h2>
<p>User who publishes and funds a bounty.</p>
</article>
<article>
<h2>Nostr event</h2>
<p>
A signed data object used for SatCode
coordination and audit history.
</p>
</article>
<article>
<h2>Oracle</h2>
<p>
An operator that observes a declared external
source and signs an attestation.
</p>
</article>
<article>
<h2>Oracle-mode dispute resolution</h2>
<p>
The path for machine-verifiable work, using a
declared k-of-n oracle set.
</p>
</article>
<article>
<h2>Human-mode dispute resolution</h2>
<p>
The path for subjective work, using a randomly
selected panel of bonded jurors.
</p>
</article>
<article>
<h2>Taker</h2>
<p>
User who accepts and completes a bounty.
</p>
</article>
<article>
<h2>Taproot</h2>
<p>
The Bitcoin output construction that commits to
SatCode’s escrow script tree.
</p>
</article>
<article>
<h2>vTXO</h2>
<p>
A virtual UTXO inside an Ark round; SatCode
escrow lives in one.
</p>
</article>
<article>
<h2>Watcher</h2>
<p>
A keyless service that collects threshold
signatures and assembles a witness.
</p>
</article>
</div>
</div>
</main>
</div>
<footer class="site-footer">
<div class="footer-inner">
<a class="wordmark" href="index.html">
satcode
<span>.</span>
</a>
<p>SatCode is currently in development.</p>
</div>
</footer>
<script src="main.js"></script>
</body>
</html>