📚
- sirius.x docs
+ Sirius.X docs
How the pieces fit together: the TLD registry, name registration, records that
tell the resolver where a site lives, the resolver itself, and how anyone can verify anything
against the chain.
@@ -208,7 +208,7 @@ node Argus/src/update.js myname.x '{"s3":"bns/myname/"}'
node Argus/src/update.js myname.x '{"ip":"1.2.3.4","tls":"<sha256-of-leaf-cert>"}'
Pattern C — Dual host (Sia primary, VPS mirror)
- What sirius.x itself uses. Sia is the chain-authoritative source (survives
+
What Sirius.X itself uses. Sia is the chain-authoritative source (survives
if the VPS is down); the VPS serves the same content on silentmode.st/<path>
for users without a BCNR resolver installed. On the VPS side, extend the nginx vhost
serving silentmode.st with a new location block that aliases
@@ -224,7 +224,7 @@ node Argus/src/update.js myname.x '{"ip":"1.2.3.4","tls":"<sha256-of-leaf-cer
https://myname.x/ via any BCNR resolver.
The dual-host recipe, end to end
- This is the exact sequence sirius.x itself uses on every publish. The
+
This is the exact sequence Sirius.X itself uses on every publish. The
chain record stays constant; only file contents change, so no per-publish UPD is
needed.
@@ -423,7 +423,7 @@ process.exit(0);"