satcodexyz.github.io/roles.html at main · satcodexyz/satcodexyz.github.io · GitHub

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
<!doctype html>
<html lang="en">
    <head>
        <meta charset="utf-8" />
        <meta name="viewport" content="width=device-width,initial-scale=1" />
        <title>Roles and responsibilities — SatCode</title>
        <meta
            name="description"
            content="Who acts, what they must verify, and what no role can do alone."
        />
        <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>Getting started</span>
                </div>
                <header class="article-head">
                    <p class="kicker">Getting started</p>
                    <h1>Roles and responsibilities</h1>
                    <p>Participant roles and their purpose in SatCode</p>
                </header>
                <div class="article-body">
                    <h2 id="maker">Maker</h2>
                    <p>
                        The <strong>maker</strong> publishes the bounty, terms, deadline,
                        check-in interval, refund address, and
                        dispute-resolution choice. After acceptance, the maker
                        constructs and funds the real escrow. The maker reviews
                        delivery, cooperates with taker on a valid payout, or
                        opens a dispute.
                    </p>
                    <h2 id="taker">Taker</h2>
                    <p>
                        The <strong>taker</strong> clarifies and accepts terms, supplies a payout
                        address, and—before starting to work—verifies the escrow
                        vTXO. They then check in according to the terms, and
                        submits work. After delivering the final work, taker
                        cooperates with maker to release escrow funds to the
                        taker, or opens a dispute.
                    </p>
                    <h2 id="adjudicators">Jurors and oracles</h2>
                    <p>
                        <strong>Jurors</strong> enter juror registry by staking a bond in
                        Bitcoin. They remain available during a dispute, review
                        evidence, publish vote, and sign the winning spend in
                        human-mode dispute resolution.
                        <br />
                        <br />
                        <strong>Oracle</strong> operators bond Bitcoin, monitor declared data
                        sources, publish signed attestations, and sign outcomes
                        in oracle-mode dispute resolution.
                    </p>
                    <h2 id="others">Supporting roles</h2>
                    <p>
                        A
                        <strong>watcher</strong>
                        collects signatures and assembles witnesses but holds no
                        keys. Anyone can run a watcher service, but takers have
                        the strongest incentive, because they want to construct
                        the spending transaction to get paid.

                        <br>
                        <br>
                        <strong>Platform developers</strong> can
                        slash bond vTXOs with their governance keys, to punish dishonest oracles and jurors.
                        Governance keys are not embedded in escrow, they can only slash.
                    </p>
                    <h2 id="ark-labs">Ark Operator</h2>
                    <p>
                        The Ark server run by Ark Labs co-signs transactions and
                        enforces SDK policy, but cannot spend an escrow leaf
                        alone.
                    </p>
                </div>
                <nav class="article-nav" aria-label="Article navigation">
                    <a href="getting-started.html">
                        <small>Previous</small>
                        How SatCode works
                    </a>
                    <a class="next" href="agents.html">
                        <small>Next article</small>
                        Who is SatCode for? →
                    </a>
                </nav>
            </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>