The theseus.x website: Theseus downloads, extensions, plug-ins, whitepaper and developer docs
A developer / agent landing page on both .X sites so an LLM or a human porting the resolver has everything in one place and does not need the public gateway to understand how to talk to BNS. ariadne.x/dev/ is the canonical page. Covers: - Why: resolve names directly from the chain, with no operator in the middle. - BNS1 in one page: beacons, cash-token certificates, OP_RETURN payloads, REG/UPD/REL, chipnet network constants, the six indexer rules (including the 2026-10-04 one-message rule). - The record-type table — u, h, a, ip, p, s3, tls, c, bl. - A minimum viable resolver in under 100 lines of Node.js that pulls the beacon's history, parses the OP_RETURNs, and prints a name's records. - Pointers to every production implementation (Argus JS, Ariadne Kotlin, the Windows Thread, the gateway) and every spec document on the forge. - Public endpoints with a trust note: convenience, not consensus. - Three paths for embedding Ariadne's Thread in your own app: chain-install the Windows service, import the resolver library directly, or call the local HTTP API; platform coverage table; MPL-2.0 licence note. theseus.x/dev/ is a shorter page that cross-links to ariadne.x/dev/ for the resolver work and covers Theseus-specific topics inline — the extension publishing path (register a .x name on sirius.x, PUT signed tarball to /api/ext, Theseus verifies the signature against the on-chain owner before anything runs) and the first-party plug-in surface. Both pages are wired into the home-page topnav, mobile dropdown, and footer Product column. |
||
|---|---|---|
| assets | ||
| brand | ||
| dev | ||
| dl | ||
| extensions | ||
| plug-ins | ||
| whitepaper | ||
| index.html | ||