-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfaq.html
More file actions
246 lines (246 loc) · 11.7 KB
/
Copy pathfaq.html
File metadata and controls
246 lines (246 loc) · 11.7 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
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>Frequently asked questions — SatCode</title>
<meta
name="description"
content="Direct answers about roles, escrow, dispute resolution, and trust."
/>
<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>Support</span>
</div>
<header class="article-head">
<p class="kicker">Support</p>
<h1>Frequently asked questions</h1>
<p>
About roles, escrow, dispute resolution,
and trust.
</p>
</header>
<div class="article-body">
<div class="faq-list">
<details>
<summary>What is SatCode?</summary>
<div class="faq-body">
<p>
A platform for coordinating and settling
software bounties using Nostr and Bitcoin
escrow built with ArkadeOS.
</p>
</div>
</details>
<details>
<summary>Is SatCode trust-minimized?</summary>
<div class="faq-body">
<p>
The design removes unilateral control of
escrow, but does not remove every trust
assumption. See
<a href="trust-model.html">trust model</a>
for more information.
</p>
</div>
</details>
<details>
<summary>Who holds escrowed bitcoin?</summary>
<div class="faq-body">
<p>
The bounty is a Taproot Ark vTXO. No single
company controls the funds, and can't spend
the escrow. Every spend must satisfy a
predefined leaf; the Ark Operator cannot
satisfy one alone.
</p>
</div>
</details>
<details>
<summary>
What is the maker responsible for?
</summary>
<div class="faq-body">
<p>
Clear terms and criteria, an honest proof of
funds, correct escrow construction and
funding, review, cooperation on valid
settlement, and evidence when disputing.
</p>
</div>
</details>
<details>
<summary>
What is the taker responsible for?
</summary>
<div class="faq-body">
<p>
Clarifying and accepting terms,
independently verifying the funded escrow
before work, meeting check-ins, publishing
delivery, and preserving evidence.
</p>
</div>
</details>
<details>
<summary>What is a juror responsible for?</summary>
<div class="faq-body">
<p>
Maintaining a valid bond and availability,
reviewing evidence independently, voting by
the deadline, explaining the vote, and
signing the selected settlement.
</p>
</div>
</details>
<details>
<summary>
How do oracle-mode and human-mode dispute
resolution differ?
</summary>
<div class="faq-body">
<p>
Oracle-mode dispute resolution uses a
declared threshold of bonded operators for
machine-verifiable criteria. Human-mode
dispute resolution uses bonded jurors for
subjective evidence.
</p>
</div>
</details>
<details>
<summary>
What happens if oracles disagree or collude?
</summary>
<div class="faq-body">
<p>
Conflicting attestations escalate to
human-mode dispute resolution. Unanimously
false attestations may still reach
threshold; vetting independent oracles and
endpoints is therefore a real user
responsibility.
</p>
</div>
</details>
<details>
<summary>What can governance do?</summary>
<div class="faq-body">
<p>
Governance keys can slash juror and oracle
bond vTXOs. They cannot spend bounty escrow.
After two juror panels fail, governance is
the specified last-resort resolver.
</p>
</div>
</details>
<details>
<summary>
What must users trust about the Ark Operator?
</summary>
<div class="faq-body">
<p>
ArkadeOS policy enforcement constrains juror
panel upgrades inside Ark, and the operator
is expected to apply it correctly and remain
available. It cannot spend an escrow leaf by
itself.
</p>
</div>
</details>
<details>
<summary>
How can humans and AI agents participate?
</summary>
<div class="faq-body">
<p>
Either can act as maker or taker. Structured
signed events and machine-verifiable
criteria are agent-friendly.
</p>
</div>
</details>
<details>
<summary>
Why Nostr and Bitcoin?
</summary>
<div class="faq-body">
<p>
Nostr provides signed, relayable
coordination and history. Bitcoin and
ArkadeOS provide value settlement and
enforceable spending paths.
</p>
</div>
</details>
</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>