satcodexyz.github.io/architecture.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
<!doctype html>
<html lang="en">

<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width,initial-scale=1" />
  <title>System architecture — SatCode</title>
  <meta name="description" content="How signed coordination and Bitcoin enforcement fit together." />
  <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>Architecture</span>
      </div>
      <header class="article-head">
        <p class="kicker">Architecture</p>
        <h1>System architecture</h1>
        <p>Leveraging Nostr and Arkade.</p>
      </header>
      <div class="article-body">
        <h2 id="nostr">Nostr</h2>
        <p>
          Nostr is the social layer of Satcode. Bounties, taker acceptance, comments,
          submissions, disputes, evidence, selection, votes, verdicts,
          registrations, and attestations are all signed Nostr events that
          cannot be altered or forged. Satcode users don't have to be Nostr
          experts in order to use the platform effectively.
        </p>
        <h2 id="arkade">Arkade</h2>
        <p>
          The SatCode design leans on <strong>Arkade</strong>, Ark Labs'
          implementation and SDK for the Ark protocol, for vTXOs,
          Taproot script construction, threshold Tapscript, and most notably,
          output introspection. Ark Labs operate the Ark server but cannot move
          user funds from the escrow unilaterally. That being said, there is still
          trust involved that the Ark server remains reachable and operational to
          enforce the escrow contracts.
        </p>
        <h2 id="bitcoin">Bitcoin</h2>
        <p>
          Bitcoin acts as the final settlement layer for Arkade. Timelocks
          enforced on-chain ensure unilateral exits for user funds. What Bitcoin L1
          <strong>does not</strong> enforce are the Arkade SDK-specific covenant-esque
          features in the escrow contracts that dispute resolution depends on.
        </p>
      </div>
      <nav class="article-nav" aria-label="Article navigation">
        <a href="resolving-disputes.html"><small>Previous</small>Resolving disputes</a><a class="next"
          href="escrow.html"><small>Next article</small>Escrow & settlement →</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>