Repository navigation
Expand file tree
/
Copy pathbeta-guide.html
More file actions
107 lines (107 loc) · 9.1 KB
/
Copy pathbeta-guide.html
File metadata and controls
107 lines (107 loc) · 9.1 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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="Setup and safety guide for the CATalyst v1.4 beta with optional Splash offer broadcasting.">
<meta name="theme-color" content="#080C12">
<meta name="referrer" content="strict-origin-when-cross-origin">
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; base-uri 'self'; object-src 'none'; script-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self'; connect-src 'none'; frame-src 'none'; form-action 'none'; upgrade-insecure-requests">
<title>v1.4 beta guide | CATalyst</title>
<link rel="icon" type="image/png" href="assets/icon.png">
<style>
:root { color-scheme: dark; font: 16px/1.65 system-ui, sans-serif; background: #080c12; color: #dbe6ef; }
* { box-sizing: border-box; }
body { margin: 0; }
a { color: #64dfc0; }
a:focus-visible { outline: 3px solid #d4a84b; outline-offset: 3px; }
header, main, footer { max-width: 860px; margin: 0 auto; padding: 24px; }
nav { display: flex; flex-wrap: wrap; gap: 18px; align-items: center; }
nav a { text-decoration: none; }
h1, h2, h3 { line-height: 1.25; color: #fff; }
h1 { font-size: clamp(2rem, 5vw, 3.2rem); margin: 48px 0 12px; }
h2 { margin-top: 42px; padding-top: 14px; border-top: 1px solid #263848; }
h3 { margin-top: 24px; }
p, li { max-width: 75ch; }
li { margin: 8px 0; }
.eyebrow { color: #64dfc0; font-weight: 700; letter-spacing: .08em; text-transform: uppercase; }
.lead { font-size: 1.15rem; color: #b9c9d7; }
.notice { background: #13222c; border-left: 4px solid #d4a84b; padding: 16px 20px; margin: 28px 0; }
.notice strong { color: #fff; }
.checklist { padding: 4px 20px; background: #101923; border: 1px solid #263848; border-radius: 12px; }
code { background: #172631; padding: 2px 5px; border-radius: 4px; overflow-wrap: anywhere; }
footer { border-top: 1px solid #263848; color: #9cb0c1; }
</style>
</head>
<body>
<header>
<nav aria-label="Primary navigation">
<a href="index.html">CATalyst home</a>
<a href="index.html#download">Downloads</a>
<a href="https://github.com/catalystxch/catalyst-bot/issues" rel="noopener">Feedback and bugs</a>
</nav>
<h1>v1.4 beta guide</h1>
<p class="eyebrow">New Dexie only beta testing · Windows and Linux</p>
<p class="lead">CATalyst connects to Sage Wallet locally, builds Chia CAT/XCH offers, and publishes them to Dexie. Optional Splash P2P can also broadcast offers. TibetSwap, AMM pricing, Arb Sniper, and Close the Gap are retired in this beta.</p>
<div class="notice"><strong>Real wallet actions:</strong> Offers, cancellations, and coin preparation can move or lock funds and incur network fees. Test with a separate wallet funded only with amounts you can afford to lose, and back up an existing CATalyst profile before upgrading. Review the selected wallet, exact CAT asset ID, campaign limits, and fee scope in the app before proceeding.</div>
</header>
<main>
<section aria-labelledby="why-dexie">
<h2 id="why-dexie">Why CATalyst changed</h2>
<p>TibetSwap has shut down. Earlier CATalyst versions used its AMM data for pricing and arbitrage, so those TibetSwap-dependent features are retired. We redesigned CATalyst to manage CAT/XCH offers through Dexie without relying on TibetSwap. Read <a href="https://v2.tibetswap.io/" rel="noopener">TibetSwap's closure notice</a> for the venue's announcement.</p>
<p>Dexie is the offer marketplace for this beta. Splash remains an optional way to broadcast the same signed offers, starts off for new installs, and does not replace Dexie.</p>
</section>
<section aria-labelledby="tester-status">
<h2 id="tester-status">Tester status</h2>
<p>This is a test build. Windows and Linux package smoke checks, automated tests, and an isolated Sage offer lifecycle have passed. The current build is still undergoing real-wallet offer and recovery testing, independent second-PC live acceptance, and long-running stability checks. Please report unexpected behavior; a successful install does not mean those checks have passed.</p>
<p>Dexie is the primary offer publication path. Splash is optional and starts off for new installs; delivery to a separate Splash peer has not yet been confirmed for this build. Leave Splash off unless you specifically intend to test it, and verify offer visibility independently.</p>
</section>
<section>
<h2>1. Download and verify</h2>
<ol>
<li>Use the <a href="index.html#download">CATalyst download panel</a> only when it explicitly lists the v1.4 Dexie beta. It links to official Windows and Linux releases.</li>
<li>Compare your downloaded package's SHA-256 with the value shown on the page and in its release sidecar before running it.</li>
<li>Windows: a blue “Windows protected your PC” screen may appear because this beta installer does not yet have a verified publisher certificate. After checking the SHA-256, choose More info, check the app name, then Run anyway if you want to install. Stop if Windows or your antivirus reports malware or a potentially unwanted app.</li>
<li>Linux x86-64: the download panel offers the Debian package. The <a href="https://github.com/catalystxch/catalyst-bot/releases/tag/v1.4.1" rel="noopener">exact release</a> also offers an AppImage and tarball, following the packaging path used for earlier working Linux releases.</li>
</ol>
</section>
<section>
<h2>2. Connect Sage and check the pair</h2>
<ol>
<li>Start Sage Wallet, choose the intended <strong>mainnet</strong> wallet, and wait for sync. CATalyst will show its connection state in the native app.</li>
<li>Read the Risk Disclosure in the app. Choose the intended CAT/XCH pair and verify the full CAT asset ID and wallet fingerprint, not just the ticker or logo.</li>
<li>Check spendable balances, pending transactions, and existing offers in Sage. If any state is unexpected, stop before starting a bot or campaign.</li>
</ol>
</section>
<section>
<h2>3. Review the market and limits</h2>
<p>The Market view shows Dexie offer-book evidence and its freshness. When the book cannot support a trustworthy reference price, Follow mode can hold or withdraw exposure instead of quoting from stale or invented data.</p>
<p>Choose a liquidity mode and review offer sizes, inventory limits, price corridor, and any Bootstrap campaign duration and budget. A Bootstrap campaign for a thin market is a separate, bounded decision. It does not begin just because you selected a pair.</p>
<div class="checklist">
<h3>Before any start action</h3>
<ul>
<li>Confirm the wallet fingerprint and exact CAT asset ID again.</li>
<li>Review the displayed buy and sell sizes, total inventory budgets, and maximum network fee.</li>
<li>Check for pending transactions or existing offers that could overlap the new plan.</li>
<li>Approve the exact action in the app only if its limits match what you intend.</li>
</ul>
</div>
</section>
<section>
<h2>4. Coin preparation and offers</h2>
<p>Each offer needs suitable wallet coins. Coin Prep can split coins and may cancel existing offers first. Its estimated network fee and spending ceiling require a separate approval. Review the on-screen summary and recovery state before repeating any interrupted operation.</p>
<p>Once running, compare CATalyst's Offers view with Sage's wallet offers and the Dexie links. A posted offer may take time to appear in a public indexer; Sage and confirmed chain state are authoritative for wallet effects.</p>
<p>Splash P2P is an optional offer broadcasting path in Settings. It starts off for new installs and can share your signed offers with peers when enabled. A running local Splash node does not by itself prove that peers received an offer; check peer status and exact offer rediscovery before relying on broadcast reach.</p>
</section>
<section>
<h2>5. Stop, recover, and report</h2>
<p><strong>Stop Bot</strong> stops new trading work. Existing offers can remain live until you explicitly cancel them and confirm they are terminal in Sage. <strong>Cancel All</strong> is a separate protected action. On restart, use the Previous Session choices only after checking which offers are still active.</p>
<p>If the app shows a safety block, stale wallet state, unknown Coin Prep outcome, or conflicting offers, leave it stopped and gather a Debug Bundle from the Logs tab. Do not repeatedly retry a wallet action whose outcome is unknown.</p>
<p>Report bugs through the <a href="https://github.com/catalystxch/catalyst-bot/issues/new/choose" rel="noopener">public issue forms</a>. Never post seed phrases, private keys, wallet TLS keys, or unredacted personal wallet data.</p>
</section>
</main>
<footer>
<p>This guide is for the v1.4 Dexie beta. See the <a href="docs.html">current FAQ and screenshots</a> for Linux setup and package verification.</p>
</footer>
</body>
</html>