Repository navigation
Expand file tree
/
Copy pathtutorial.html
More file actions
132 lines (126 loc) · 30.3 KB
/
Copy pathtutorial.html
File metadata and controls
132 lines (126 loc) · 30.3 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
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="referrer" content="strict-origin-when-cross-origin" />
<meta name="theme-color" content="#eee8f2" />
<meta name="description" content="An optional guide to the service behind Castonaut and to running a personal Farcaster Snapchain test node." />
<title>How it works — Castonaut</title>
<meta name="application-name" content="Castonaut" />
<meta name="mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-title" content="Castonaut" />
<link rel="stylesheet" href="/src/styles.css" />
<link rel="stylesheet" href="/src/site-shell.css" />
<link rel="stylesheet" href="/src/guide.css" />
<link rel="stylesheet" href="/src/guide-refresh.css" />
<link rel="stylesheet" href="/src/page-polish.css" />
<link rel="stylesheet" href="/src/soft-reset.css" />
<link rel="stylesheet" href="/src/desktop-polish.css" />
<link rel="stylesheet" href="/src/experience-finish.css" />
<link rel="icon" href="/favicon.ico" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="apple-touch-icon" href="/apple-touch-icon.png" />
<link rel="manifest" href="/site.webmanifest" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Castonaut" />
<link rel="canonical" href="https://castonaut.vercel.app/tutorial.html" />
<meta property="og:url" content="https://castonaut.vercel.app/tutorial.html" />
<meta property="og:title" content="How it works — Castonaut" />
<meta property="og:description" content="A clear guide to using Castonaut and understanding the Farcaster service behind it." />
<meta property="og:image" content="https://castonaut.vercel.app/og-castonaut-pocket-atlas.png" />
<meta property="og:image:secure_url" content="https://castonaut.vercel.app/og-castonaut-pocket-atlas.png" />
<meta property="og:image:type" content="image/png" />
<meta property="og:image:width" content="1730" />
<meta property="og:image:height" content="909" />
<meta property="og:image:alt" content="Castonaut’s warm paper atlas, with a classic desktop computer displaying an orbital map." />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="How it works — Castonaut" />
<meta name="twitter:description" content="A clear guide to using Castonaut and understanding the Farcaster service behind it." />
<meta name="twitter:image" content="https://castonaut.vercel.app/og-castonaut-pocket-atlas.png" />
<meta name="twitter:image:alt" content="Castonaut’s warm paper atlas, with a classic desktop computer displaying an orbital map." />
</head>
<body>
<a class="skip-link" href="#guide-main">Skip to setup guide</a>
<div class="app-frame guide-frame">
<aside class="sidebar" aria-label="Setup guide navigation">
<a class="brand" href="/" aria-label="Castonaut home"><img class="brand-mark" src="/favicon.svg" alt="" aria-hidden="true" /><span><strong>castonaut</strong><small>FIELD JOURNAL · FARCASTER</small></span></a>
<div class="rail-label">SETUP GUIDE</div>
<nav class="nav-list guide-nav"><a class="nav-item" href="/#desk"><span class="nav-symbol">⌂</span><span>Back to home</span><span class="nav-arrow">↗</span></a><a class="nav-item active" href="#quickstart"><span class="nav-symbol">▧</span><span>Quickstart</span><kbd>1</kbd></a><a class="nav-item" href="#concepts"><span class="nav-symbol">⌘</span><span>How it works</span><kbd>2</kbd></a><a class="nav-item" href="#operator-tips"><span class="nav-symbol">⌁</span><span>Operator tips</span><kbd>3</kbd></a><a class="nav-item" href="#security"><span class="nav-symbol">◇</span><span>Keys & safety</span><kbd>4</kbd></a></nav>
<div class="sidebar-note"><span class="note-led"></span><div><strong>Built for a clean setup</strong><small>Three commands, no managed read API key.</small></div></div><div class="sidebar-foot"><span>INDEPENDENT CLIENT</span><span>GUIDE 01</span></div>
</aside>
<div class="main-column">
<header class="topbar"><div class="crumb"><span class="crumb-dot"></span><span>CASTONAUT GUIDE</span><span class="crumb-slash">/</span><span>FOR CURIOUS BUILDERS</span></div><div class="top-actions"><a class="avatar-button home-avatar" href="/" aria-label="Return to the client">↗</a></div></header>
<main id="guide-main" class="guide-main">
<nav class="guide-mobile-nav" aria-label="Guide sections"><a href="#quickstart">Quickstart</a><a href="#concepts">How it works</a><a href="#operator-tips">Operator tips</a><a href="#security">Keys & safety</a></nav>
<section class="guide-hero"><div class="overline"><span class="live-pip"></span> YOUR FARCASTER WORKSTATION</div><h1>Make it<br />your own.</h1><p class="lead">Start with Castonaut, then make the whole route yours: run the client on your computer, connect a Snapchain node you control, and authorize a limited Farcaster app key.</p><div class="hero-meta"><span><i>01</i> YOUR CLIENT</span><b>→</b><span><i>02</i> YOUR NODE</span><b>→</b><span><i>03</i> YOUR ACCOUNT</span></div><div class="guide-hero-actions"><a class="button button-orange" href="#quickstart">Start the 3 steps <span>↓</span></a><a class="guide-hosted-link" href="/">Try Castonaut now <span>↗</span></a></div><p class="guide-hero-note">The hosted client is the quick way to explore. Running your own client and node gives you more control over the software and the read path. You can start with the client and add your node later.</p></section>
<section class="guide-section quickstart-section" id="quickstart">
<div class="section-kicker"><span>01</span><span>QUICKSTART</span><span class="section-rule"></span><span>3 STEPS</span></div>
<div class="section-intro"><h2>Three steps to your own setup.</h2><p>Use the hosted client first if you like. The self-run route below keeps the client on your computer and reads through a node you operate.</p></div>
<div class="quickstart-map" aria-label="Three steps to a self-run Castonaut setup"><article><span>01 · YOUR COMPUTER</span><strong>Prepare the client and cloud tools</strong><small>Install Castonaut and the Google Cloud CLI; choose a billing-enabled project.</small></article><article><span>02 · YOUR NODE</span><strong>Provision and sync Snapchain</strong><small>Your VM runs a read node that catches up with the network.</small></article><article><span>03 · YOUR COMPUTER</span><strong>Run Castonaut and connect</strong><small>Your local client reads through your node and sends signed messages to the validator network.</small></article></div>
<div class="cast-path" role="img" aria-label="Cast path: Castonaut runs on your computer, reads feed data from your Snapchain node, and sends signed Farcaster messages through it to the validator network; validators decide and replicate the messages."><div class="cast-path-title"><span>THE CAST PATH</span><small>Who runs each part</small></div><div class="cast-path-flow"><div><span>YOUR COMPUTER</span><strong>Castonaut client</strong><small>Feed, local Desk, signing</small></div><b aria-hidden="true">↔</b><div><span>YOUR NODE</span><strong>Snapchain read node</strong><small>Stores state · serves API · relays writes</small></div><b aria-hidden="true">↔</b><div><span>VALIDATOR NETWORK</span><strong>Farcaster validators</strong><small>Decide blocks · replicate messages</small></div></div><p>Validators run the network consensus. Your read node follows and serves network data; it is not a validator and does not vote.</p></div>
<div class="prereq-strip"><span class="prereq-icon" aria-hidden="true">⌘</span><div><strong>Before you begin</strong><small>Node.js 22, Google Cloud CLI, a billing-enabled GCP project, and an existing Farcaster account with storage. The node costs about $0.25/hour plus network charges; credits and trial eligibility vary. The VM has a public IP; local client requests reveal your computer’s public egress IP to your node.</small></div></div>
<div class="cost-note"><span class="cost-mark" aria-hidden="true">$</span><div><strong>Check billing before provisioning.</strong><p>A budget is only an alert. A stopped VM can still incur disk and reserved-IP charges. Run <code>npm run destroy -- us-central1-a</code> only when finished: it deletes the VM, disk, firewall rule, and synced data.</p></div></div>
<details class="hardware-option first-run-setup" open><summary>Prerequisites · one-time setup before the three commands</summary><div class="first-run-commands"><p>Install Node.js 22, the Google Cloud CLI, and this repo’s dependencies:</p><button type="button" class="copy-command" data-copy="git clone https://github.com/wlplease/castonaut.git; cd castonaut; npm ci" aria-label="Copy repository install command">COPY INSTALL</button><p>Sign in, choose a project with billing enabled, and select it:</p><button type="button" class="copy-command" data-copy="gcloud auth login" aria-label="Copy Google Cloud sign-in command">COPY SIGN IN</button><button type="button" class="copy-command" data-copy="gcloud projects list" aria-label="Copy Google Cloud project list command">COPY PROJECT LIST</button><p>Run <code>gcloud config set project YOUR_PROJECT_ID</code> with your project ID. Verify billing/trial credit and create a budget alert in Cloud Billing before provisioning. The three numbered commands below are the actual provision → start → connect flow.</p></div></details>
<div class="command-stack">
<article class="command-card"><div class="command-number">01</div><div class="command-content"><div class="command-head"><div><span class="overline">CREATE</span><h3>Provision your node.</h3></div><button class="copy-command" data-copy="npm run provision -- us-central1-a" aria-label="Copy provisioning command">COPY</button></div><p>Creates a 4-vCPU VM and 2-TB disk. Review the estimate; type <code>CREATE</code> to proceed.</p><pre><code>npm run provision -- us-central1-a</code></pre></div></article>
<article class="command-card"><div class="command-number">02</div><div class="command-content"><div class="command-head"><div><span class="overline">SYNC</span><h3>Start Snapchain.</h3></div><button class="copy-command" data-copy="npm run node -- us-central1-a" aria-label="Copy node setup command">COPY</button></div><p>Follow the official read-node setup prompts. Leave the VM running while the first snapshot syncs; it can take hours.</p><pre><code>npm run node -- us-central1-a</code></pre><p>In another terminal, repeat this check until it says <strong>READY</strong> and the endpoint is reachable:</p><div class="step-command"><code>npm run node:check -- us-central1-a</code><button type="button" class="copy-command" data-copy="npm run node:check -- us-central1-a" aria-label="Copy node readiness command">COPY CHECK</button></div></div></article>
<article class="command-card"><div class="command-number">03</div><div class="command-content"><div class="command-head"><div><span class="overline">OPEN</span><h3>Connect Castonaut.</h3></div><button class="copy-command" data-copy="npm run client -- --zone us-central1-a" aria-label="Copy client command">COPY</button></div><p>Keep the node running and open the local link. Connect an existing Farcaster account with storage using its recovery phrase. Castonaut checks the account in this tab, then uses it to authorize a separate, scoped browser key. This authorization is gasless; it needs no wallet extension or Optimism transaction. A test cast is optional and will be public.</p><pre><code>npm run client -- --zone us-central1-a</code></pre><small class="privacy-note">The node sees your computer’s public IP in local mode. Only enter a recovery phrase on a build whose code and operator you trust.</small></div></article>
</div>
<figure class="node-ready-example"><img src="/docs/screenshots/node-ready.png" alt="Snapchain node status example: VM running, API responding, three active shards, one-second maximum delay, and READY status; shard heights and message counts are included." loading="lazy" /><figcaption><strong>What ready looks like.</strong> This real status capture shows all three shard heights, sync delay, and a READY result. Heights and counts change as the network advances; this is an example, not a live reading.</figcaption></figure>
<div class="sync-guidance"><strong>If sync is slow</strong><p>First sync can take hours. Run <code>npm run node:status:once -- us-central1-a</code> more than once and compare shard heights and delays. If heights are advancing and delay is falling, leave the VM running and check again later. If progress stalls, inspect the status output for disk space, peer mesh, and recent logs. Don’t delete the database or repeatedly recreate the node to force sync.</p></div>
<details class="hardware-option quickstart-cost"><summary>Monitoring and cleanup commands</summary><div class="quickstart-details"><p>Use this read-only snapshot to inspect sync, disk, and container health:</p><code>npm run node:status:once -- us-central1-a</code><div class="trial-saver-actions"><button type="button" class="copy-command" data-copy="npm run node:status:once -- us-central1-a" aria-label="Copy the read-only node status command">COPY STATUS</button><button type="button" class="copy-command" data-copy="npm run destroy -- us-central1-a" aria-label="Copy the node cleanup command">COPY CLEANUP</button></div><small>Cleanup asks you to type <code>DELETE</code>. It removes the VM, disk, firewall rule, and node data. <a href="https://cloud.google.com/signup-faqs" target="_blank" rel="noreferrer">Google trial details ↗</a></small></div></details>
<details class="hardware-option"><summary>Run your own client?</summary><div class="quickstart-details"><p>The hosted site needs no setup or personal node. To run the client locally, clone the repo, run <code>npm ci</code>, then connect it to a node you trust:</p><code>npm run client -- --node-url https://YOUR-NODE</code><button type="button" class="copy-command" data-copy="npm run client -- --node-url https://YOUR-NODE" aria-label="Copy local client command">COPY CLIENT COMMAND</button><p>This opens a local web app, not a packaged desktop app. If you use your own public node, it can see your computer’s public IP.</p><a href="https://github.com/wlplease/castonaut" target="_blank" rel="noreferrer">MIT source on GitHub ↗</a></div></details>
<details class="hardware-option"><summary>Use your own computer?</summary><p>A home node needs 4 CPU cores, 16 GB RAM, about 2 TB storage, stable internet, and public ports. Its peers can see your home public IP. <a href="https://github.com/farcasterxyz/snapchain#running-a-node" target="_blank" rel="noreferrer">Node requirements ↗</a></p></details>
</section>
<section class="guide-section concept-section" id="concepts">
<div class="section-kicker"><span>02</span><span>PROTOCOL BASICS</span><span class="section-rule"></span><span>THE PIECES BEHIND THE WINDOW</span></div>
<div class="section-intro"><h2>Small pieces.<br />Clear responsibilities.</h2></div>
<div class="concept-grid">
<article class="concept-card"><span class="concept-index">A / IDENTITY</span><div class="concept-symbol">⌑</div><h3>Farcaster identity</h3><p>A Farcaster account has a custody address registered in the Optimism ID Registry, which maps it to a numeric Farcaster ID (FID). Castonaut derives and checks that account from your recovery phrase locally. A username or FID alone is never treated as proof of identity.</p></article>
<article class="concept-card"><span class="concept-index">B / CUSTODY</span><div class="concept-symbol">⌑</div><h3>Custody address</h3><p>The Ethereum address registered to the FID. It authorizes signer changes and controls the account’s recovery path.</p></article>
<article class="concept-card"><span class="concept-index">C / APP ACCESS</span><div class="concept-symbol">KEY+</div><h3>Scoped app key</h3><p>A separate Ed25519 key signs app messages. Gasless <code>KEY_ADD</code> is authorized by an EIP-712 custody signature and restricts message types.</p></article>
<article class="concept-card"><span class="concept-index">D / STORAGE</span><div class="concept-symbol">▤</div><h3>Storage rent</h3><p>An existing FID needs protocol storage units to publish messages. This client does not register new accounts or buy storage.</p></article>
<article class="concept-card"><span class="concept-index">E / MESSAGE</span><div class="concept-symbol">✉</div><h3>Snapchain message</h3><p>A signed, encoded message such as a cast, follow, or reaction. Castonaut signs it in your browser and sends it through the app service.</p></article>
<article class="concept-card"><span class="concept-index">F / NODE ROLE</span><div class="concept-symbol">R ≠ V</div><h3>Read node / validator</h3><p>Your read node follows decided blocks and serves APIs. It can accept a signed message and relay it to validators; validators propose and vote on blocks.</p></article>
</div>
<div class="flow-panel"><div class="flow-label">A CAST’S JOURNEY</div><div class="flow-track"><div><span>01</span><strong>Browser</strong><small>creates + signs</small></div><b>→</b><div><span>02</span><strong>Your read node</strong><small>accepts + relays</small></div><b>→</b><div><span>03</span><strong>Validators</strong><small>include in a block</small></div><b>→</b><div><span>04</span><strong>Read back</strong><small>confirm merge</small></div></div><p>A successful submit response means the node accepted the message for relay. The app checks again and only reports publication after the message appears in network state.</p></div>
</section>
<section class="guide-section operator-section" id="operator-tips">
<div class="section-kicker"><span>03</span><span>OPERATOR FIELD GUIDE</span><span class="section-rule"></span><span>KEEP IT HEALTHY</span></div>
<div class="section-intro"><h2>Good habits.<br />Fewer surprises.</h2></div>
<div class="concept-grid operator-grid">
<article class="concept-card"><span class="concept-index">01 / BEFORE YOU CONNECT</span><div class="concept-symbol">✓</div><h3>Check readiness.</h3><p>Run <code>npm run node:check -- us-central1-a</code>. Connect only when it reports <strong>READY</strong> and the public endpoint is reachable. Recheck later; a node can fall behind.</p></article>
<article class="concept-card"><span class="concept-index">02 / ROUTINE CHECK</span><div class="concept-symbol">⌁</div><h3>Watch the basics.</h3><p>Run <code>npm run node:status:once -- us-central1-a</code>. Look at shard delay, free disk, and container health. Save the output when troubleshooting; a single sample is not a trend.</p></article>
<article class="concept-card"><span class="concept-index">03 / COST CONTROL</span><div class="concept-symbol">$</div><h3>Check billing, not just uptime.</h3><p>Set a budget alert and inspect actual charges. Stopping a VM can stop compute charges, but attached disks and reserved IPs may still cost money. Delete resources only when you no longer need their data.</p><a href="https://docs.cloud.google.com/compute/docs/instances/suspend-stop-reset-instances-overview" target="_blank" rel="noreferrer">Google Cloud billing behavior ↗</a></article>
<article class="concept-card"><span class="concept-index">04 / PROTECT YOUR DATA</span><div class="concept-symbol">▤</div><h3>Don’t reset data to fix sync.</h3><p>Keep the data disk mounted and check logs, network, and disk space first. Never remove Snapchain’s data directory as a routine fix; a reset discards the local database and may mean another long sync.</p></article>
<article class="concept-card"><span class="concept-index">05 / NETWORK PRIVACY</span><div class="concept-symbol">◎</div><h3>Know what is public.</h3><p>Hosted node requests come from the host service; local mode connects from your computer’s public IP. This setup exposes the node endpoint over plain HTTP to the internet. Treat it as public: never send credentials through it, and don’t assume it hides your IP.</p></article>
<article class="concept-card"><span class="concept-index">06 / WHEN SOMETHING FAILS</span><div class="concept-symbol">?</div><h3>Pause before retrying.</h3><p>Check readiness and recent logs first. If a signer or cast confirmation is pending, check its status before creating another key or resending. A relay response alone does not prove the cast was committed.</p></article>
</div>
<div class="cost-note operator-safety-note"><span class="cost-mark" aria-hidden="true">◇</span><div><strong>Keep credentials out of the repo.</strong><p>Never commit recovery phrases, private keys, service-account JSON, or local <code>.env</code> files. Treat terminal output and screenshots as public if they contain credentials or private endpoint details.</p></div></div>
<details class="hardware-option operator-runbook"><summary>Quick recovery: what should I check?</summary><div class="quickstart-details"><p><strong>Node says NOT READY:</strong> wait for sync, then rerun <code>npm run node:check -- us-central1-a</code>. Compare the shard delays over time; do not clear the database to force progress.</p><p><strong>Endpoint is unreachable:</strong> confirm the VM is running, verify its current IP and firewall, then inspect recent logs. This setup opens the node ports publicly and does not configure HTTPS; add a TLS proxy and suitable access controls before treating it as a private service.</p><p><strong>Disk is nearly full:</strong> pause the test and review disk use before continuing. Do not delete Snapchain data files by hand.</p><p><strong>Signer is still pending:</strong> use the client’s check-again action and wait for the signer to appear. Don’t authorize another key just because confirmation is slow.</p><p><strong>Cast is not visible:</strong> a submit acknowledgment only means relay acceptance. Refresh the feed or check network state before resending to avoid duplicate casts.</p><p><strong>Done for now:</strong> stopping the VM preserves its disk and data but may leave storage/IP charges. Destroying it removes the disk and synced data too.</p></div></details>
</section>
<section class="guide-section security-section" id="security">
<div class="section-kicker"><span>04</span><span>KEYS & SAFETY</span><span class="section-rule"></span><span>ONE CAPABILITY AT A TIME</span></div>
<div class="security-grid"><div><div class="section-intro"><h2>Your account<br />stays in control.</h2><p>Use your Farcaster recovery phrase to authorize a separate app key. It stays in this browser’s IndexedDB as non-extractable Web Crypto key material.</p></div><a class="button button-outline" href="/#desk">Open the client <span>↗</span></a></div><div class="security-card"><div class="security-card-head"><span>ACCOUNT SECURITY</span><span>SCOPED APP KEY</span></div><h3>Know what you’re authorizing.</h3><p>Your custody account signs a limited authorization for a separate app key. It is a gasless message signature, not a transaction. The phrase is processed in the tab, cleared from the field, and never saved or sent to the server. Website code can read it while you enter it, so only use phrase sign-in on a site whose code and operator you trust.</p><ul><li>The key is limited to social actions. Its 30-day sliding expiry can refresh with use, so an active key may stay valid; revoke it from the account’s signer controls to disable it sooner.</li><li>JavaScript cannot promise secure zeroization from memory. Close the page after setup and protect your device.</li><li>“Forget this browser” removes the local app key but does not revoke the network signer. Revoke the signer separately from the account’s signer controls.</li><li>Review the source and only run software you trust. Never enter a phrase into a site from an unknown developer.</li></ul><h3>Practical security limits</h3><p>Non-extractable browser key material makes ordinary key export harder; it does not make a compromised browser or device safe. Active page code can use a stored signer to request actions within its permissions. Browser profiles, extensions, operating-system accounts, backups, and remote-support tools may have access to local data. A source repository is reviewable, but source availability is not an independent security audit and does not prove that a hosted deployment is running that source.</p><ul><li>Verify the domain and certificate before entering a phrase; close other tabs and avoid public or shared computers.</li><li>Use a unique device login, current browser and operating system, screen lock, and trusted extensions. Remove extensions you do not recognize.</li><li>Review the account identifier and every authorization prompt. Stop if the FID, custody address, requested action, or app-key details do not match what you expect.</li><li>Use “Forget this browser” only to remove local access. Then separately revoke the signer in Farcaster account controls if you want to disable its network authorization.</li><li>For a suspected compromise, stop using the device, revoke the signer from a trusted environment, review recent account activity, and follow the account provider’s recovery process. Do not paste a phrase or private key into support requests.</li></ul><p>These steps reduce some risks; they cannot eliminate them. Castonaut does not guarantee that a device, key, node, browser, or protocol is secure, and cannot restore a lost recovery phrase or reverse an already accepted network action.</p></div></div>
</section>
<section class="guide-section source-section" id="source-lens">
<div class="section-kicker"><span>05</span><span>CLIENT SOURCE</span><span class="section-rule"></span><span>INCLUDE OR HIDE BY APP</span></div>
<div class="section-intro"><h2>Your feed.<br />Your source lens.</h2><p>Filter by app FID when Snapchain provides it.</p></div>
<div class="source-explainer"><div class="source-sample"><div class="sample-row"><span class="sample-dot"></span><span>CAST / FID 12</span><b>APP FID 123</b></div><div class="sample-row"><span class="sample-dot unknown"></span><span>CAST / FID 28</span><b>SOURCE UNKNOWN</b></div><div class="sample-row"><span class="sample-dot"></span><span>CAST / FID 81</span><b>APP FID 123</b></div></div><div><h3>Attribution has limits.</h3><p>Find the app FID on the client’s Farcaster profile. For gasless app keys, Snapchain signer records can associate a signer with a requester FID when the requesting app uses its own FID. Older signers, missing metadata, self-requested keys, or unrecognized signers may not identify a client. Castonaut labels those casts “source unknown” and never guesses.</p><p>The source field is an aid for personal feed control, not proof of authorship or a complete audit trail.</p></div></div>
</section>
<section class="guide-section verify-section" id="verify">
<div class="section-kicker"><span>06</span><span>VERIFY & CLEAN UP</span><span class="section-rule"></span><span>PROVE THE LOOP WORKS</span></div>
<div class="verify-grid"><div><h2>Test the whole loop.</h2><p>Have another person repeat setup on their own computer and account, then share an honest public vouch if it works.</p></div><ol class="check-list"><li><span>01</span><div><strong>Node status</strong><small><code>/v1/info</code> returns a version, shard heights, and falling block delay.</small></div></li><li><span>02</span><div><strong>Verify their account</strong><small>Use a dedicated Farcaster test account with storage and its recovery phrase; don’t type a username or FID as identity.</small></div></li><li><span>03</span><div><strong>Confirm scoped signer</strong><small>Review the FID and authorize the gasless app key; wait until Snapchain confirms it before opening the desk.</small></div></li><li><span>04</span><div><strong>Read and write as that account</strong><small>Check its following feed, post, follow, and react; wait for query confirmation after relay acceptance.</small></div></li><li><span>05</span><div><strong>Clean up</strong><small>Delete the GCP VM to stop compute charges; revoke test signer access if needed.</small></div></li></ol></div>
</section>
<section class="references-section"><div class="overline">PRIMARY REFERENCES</div><div class="reference-links"><a href="https://github.com/farcasterxyz/snapchain" target="_blank" rel="noreferrer">Snapchain repository <span>↗</span></a><a href="https://snapchain.farcaster.xyz/guides/running-a-node" target="_blank" rel="noreferrer">Run a node <span>↗</span></a><a href="https://snapchain.farcaster.xyz/node-types" target="_blank" rel="noreferrer">Read nodes vs validators <span>↗</span></a><a href="https://snapchain.farcaster.xyz/guides/writing-messages" target="_blank" rel="noreferrer">Writing messages and gasless keys <span>↗</span></a><a href="https://snapchain.farcaster.xyz/reference/httpapi/httpapi" target="_blank" rel="noreferrer">Snapchain HTTP API <span>↗</span></a><a href="https://docs.farcaster.xyz/developers/guides/basics/hello-world" target="_blank" rel="noreferrer">Farcaster developer quickstart <span>↗</span></a><a href="https://docs.farcaster.xyz/learn/architecture/overview" target="_blank" rel="noreferrer">Farcaster architecture <span>↗</span></a></div><p class="reference-footnote">Protocol behavior and sizing were checked against the linked official docs on 18 October 2026. Recheck before running commands because releases and resource requirements can change.</p></section>
<footer class="page-footer guide-footer"><span>CASTONAUT · AN INDEPENDENT FARCASTER CLIENT</span><span class="legal-links"><a href="/endorsements.html">Field notes</a><a href="/privacy.html">Privacy</a><a href="/terms.html">Terms</a><a href="/#desk">Back to the client</a></span></footer>
</main>
</div>
</div>
<div class="toast" id="guide-toast" role="status" aria-live="polite" hidden></div>
<script type="module" src="/src/site-shell.js"></script>
<script type="module" src="/src/tutorial.js"></script>
</body>
</html>