commit d392305c0bda987043b6f2f3de9576a5c36f6b52 Author: Local Dev Date: Sat Sep 12 00:07:34 2026 +0200 Initial commit diff --git a/GOTCHAS.md b/GOTCHAS.md new file mode 100644 index 0000000..085a3a7 --- /dev/null +++ b/GOTCHAS.md @@ -0,0 +1,67 @@ +# site/ — gotchas + +Hand-authored static tree for **silentmode.st**. No build step. Served by nginx +from `/opt/silent-mode/site/` on the VPS (ssh alias `silentmode`), and mirrored +to Sia (`s3://bns/silentmode/` → `silentmode.bch`) by the +`silentmode-sia-sync.timer` on the VPS every 5 minutes. Anything that lands in +`/opt/silent-mode/site/` reaches the `.bch` mirror on its own; you do not need to +run `sia-upload.js` for site files any more. + +## Never `rsync --delete` (or blanket-overwrite) `site/` → the VPS + +`/opt/silent-mode/site/` holds far more than this folder: `sirius-x/`, +`deviant/` (the full Deviant site incl. `wallet/`, `artemision/`, `katalogos/`, +`agora/`), `apps/`, `code/`. Those are deployed from **other repos**. In +particular `site/deviant/` here is a **stale Aug-31 copy**; the canonical +source is `D:\Dev\Deviant\site\deviant\` and the VPS already carries the newer +Sep-1 pages. Pushing this folder wholesale would roll them back. + +Ship **individual files**: `scp site/ silentmode:/opt/silent-mode/site/`. + +## The release manifest lives in three places + +- `https://dl.silentmode.st/releases-manifest.json` — canonical + (`/opt/silent-mode/dl/`), what `releases.silentmode.bch` points at. +- `/opt/silent-mode/site/releases-manifest.json` — what `tools/index.html` + links as `../releases-manifest.json`, and what the Sia mirror syncs. +- `site/releases-manifest.json` — the committed source of both. + +The ship checklist (`Ship Theseus …` commits) must scp it to **both** VPS +paths. It was missed for `site/` from 0.3.4 through 0.3.16 (found 2026-09-07): +the HTML pages were current while the JSON next to them still said 0.3.3. + +## Old Theseus builds fill the VPS disk + +`scripts/theseus-vps-archive.sh ` moves everything older than N-1 to +Sia and deletes it from `/opt/silent-mode/dl/`. Run it after every ship; when +it is skipped the 48 GB disk climbs ~245 MB per release. + +## Pages that are not silentmode.st pages + +`hephaestus.x/` is the landing for the `.x` name and is served from Sia via the +gateway (`navigate.st/bns/hephaestus.x/`); the copy under `/opt/silent-mode/site/` +is just parity. `choose/` has no top nav on purpose. + +## CORS on `/js/*.js` — required for BCNR pages + +The shared bundles (`bns-register.js`, `libauth.js`, `wizardconnect.js`) live +under `silentmode.st/js/` and are `import`ed cross-origin by pages served on +their own origin: `sirius.x`, `theseus.x`, any BCNR-served site opened in +Theseus (origin `bns://`). Without CORS the browser refuses to load the +module and every wallet/register/mint flow silently breaks — the launcher +click does nothing. + +The nginx block on VPS (`/etc/nginx/sites-enabled/silentmode-st`) MUST carry: + +``` +location ~ ^/js/.*\.js$ { + add_header Cache-Control "no-cache, must-revalidate" always; + add_header Access-Control-Allow-Origin "*" always; + add_header Access-Control-Allow-Methods "GET, OPTIONS" always; +} +``` + +Added 2026-09-08 after Theseus reported "CORS blocked" from origin +`bns://sirius.x`. If a future nginx-config rebuild drops the `add_header +Access-Control-*` lines, every non-silentmode.st page that imports the bundle +starts failing again with "No 'Access-Control-Allow-Origin' header". diff --git a/apps/index.html b/apps/index.html new file mode 100644 index 0000000..ea9faa0 --- /dev/null +++ b/apps/index.html @@ -0,0 +1,29 @@ + + + + + +Moved — Silent Mode + + + + + + + +

Downloads moved.

The apps page merged with the tools hub. Everything you were looking for is now at + silentmode.st/tools/. Redirecting you there.

+ + diff --git a/brand/avatar.svg b/brand/avatar.svg new file mode 100644 index 0000000..5d8cf53 --- /dev/null +++ b/brand/avatar.svg @@ -0,0 +1,20 @@ + diff --git a/brand/banner.svg b/brand/banner.svg new file mode 100644 index 0000000..3f1a52f --- /dev/null +++ b/brand/banner.svg @@ -0,0 +1,28 @@ + diff --git a/brand/index.html b/brand/index.html new file mode 100644 index 0000000..1c58169 --- /dev/null +++ b/brand/index.html @@ -0,0 +1,241 @@ + + + + + +Brand — Silent Mode + + + + + + + + + + + + + + + + + + +

Silent Mode — brand

Two interlocking chain links, one acid green — the family mark for + every Silent Mode product. Kit below: logo, wordmark, avatar, banner, palette, + usage. Every asset is a scalable SVG; raster it to whatever platform demands + a PNG.

+ +

+ + +

Assets

+ +

Logo

Two interlocking chain links. Use where the mark stands alone — favicons, + app icons, small tile placements. Reads at any size from 16 px up.

SVG · viewBox 200×200 · scalable

+ SVG + Open +

+ +

Wordmark

Mark + "Silent Mode" set at 56 px, letter + spacing 0.4. Use for horizontal placements — page headers, business cards, + email signatures.

SVG · viewBox 640×120

+ SVG + Open +

+ +

Avatar

Square 400×400 with radial background, centred mark, wordmark below. + Sized for social profile pictures — X, Mastodon, Nostr, GitHub org avatar. + Rasters cleanly to 200×200 and 100×100.

SVG · viewBox 400×400

+ SVG + Open +

+ +

Banner

Wide 1500×500 header for X / Mastodon covers, GitHub org banners, OG social + cards. Tagline and second-line URL are text nodes — edit in a vector editor + if you need a different language or campaign.

SVG · viewBox 1500×500 · 3:1 aspect

+ SVG + Open +

+ +

Favicon

The same mark, compressed for tab-bar and bookmark rendering. Served from + /favicon.svg. Also works as a 16×16 PNG once + rasterised — the shape holds.

SVG · viewBox 32×32

+ SVG +

+ + +

Palette

Small palette on purpose — one accent, one text tone, three greys, + a couple of semantics. Same tokens the whole site's shared.css + exposes as CSS variables.

+ +

Acid

#d6ff3d

The accent — links, marks, active state, one CTA per view.

Ink (bg)

#0b0e14

Page background. Dark by default; a light theme is the exception.

Panel

#141a24

Cards, buttons ghost, elevated surfaces.

Text

#e7eaf1

Body ink.

Muted

#8b98a9

Secondary text, disabled state, muted mark stroke.

Dim

#5e6678

Meta, timestamps, "less important than muted".

Sia

#b39ddb

Storage badge. Only for "content lives on Sia".

Server

#4fd1a5

Server badge. Only for "content lives on an ordinary server".

+ + +

Usage

Where the mark goes

Anywhere Silent Mode itself is the subject: project sites, README banners, + social profiles, presentation title slides. If a specific product is the + subject (Theseus, Sirius, Prometheus, Hermes, Helios), prefer that + product's own mark and reserve this one for the umbrella.

Clear space

Give the mark clearance equal to one chain-link on every side. On the banner + this is honoured by the left-margin; when placing the logo yourself, respect it.

Colours in prose

The word "Mode" is in acid; the rest is body text. Don't reverse — "Silent" + in acid + "Mode" in body doesn't read as this brand.

Rasterising

SVG is the canonical format. Any modern image tool can convert it to PNG + at the size you need; Inkscape and rsvg-convert are the free defaults. + Don't distribute a low-fidelity trace as "the logo".

+ +

+ Don't: +

Recolour the mark into the palette of another product or brand.
Distort the chain-link proportions (they read as chain because of the ratio; squished, they don't).
Place the mark on a busy image without a solid backing panel.
Use the mark to endorse a third-party product, service, or claim without written permission.

+ +

Related brand kits. Navigate.st has its own mark (a compass + rose in a chain-link ring) at navigate.st/brand/. + Each Silent Mode product (Theseus, Sirius, Prometheus, Hermes, Helios) will + eventually have its own kit; this one is the umbrella.

+ +

+ + + + + diff --git a/brand/logo.svg b/brand/logo.svg new file mode 100644 index 0000000..a1ff73e --- /dev/null +++ b/brand/logo.svg @@ -0,0 +1,7 @@ + diff --git a/brand/og.png b/brand/og.png new file mode 100644 index 0000000..e7dc229 Binary files /dev/null and b/brand/og.png differ diff --git a/brand/wordmark.svg b/brand/wordmark.svg new file mode 100644 index 0000000..853dd91 --- /dev/null +++ b/brand/wordmark.svg @@ -0,0 +1,13 @@ + diff --git a/choose/free/index.html b/choose/free/index.html new file mode 100644 index 0000000..50f6318 --- /dev/null +++ b/choose/free/index.html @@ -0,0 +1,148 @@ + + + + + +You took the red one — Silent Mode + + + + + + + + + + + + + + + + +

+ + +

Anonymous by default. Not by exception.

Two missing layers, and everything follows from them. The part that + grants permission — and can therefore withdraw it — is absent. So is the part that + could ever be asked who you are, because it never collected the answer. Not held on + your behalf. Not held at all.

+ +

A registrar that logs who bought the name→ + A certificate you hold, on a public ledger. Your key, your name — nobody learns you asked for it.

A card or bank in the middle of every payment→ + Pay direct in crypto. No processor, no chargeback, and nobody to refuse it on your behalf.

An account that can be suspended→ + No account at all. Nothing was granted, so nothing can be revoked.

A browser and pages that report home→ + Theseus resolves names straight from the chain — no lookup service in the middle logging what you typed.

A host with an acceptable-use policy→ + Your own server, a paid swarm of strangers, or the chain itself.

A certificate authority vouching for you→ + A fingerprint you publish on-chain and your browser checks.

Reach that belongs to the platform→ + A name that travels with you, because nobody else is holding it.

+ +

+ The honest part. Nobody being in charge cuts both ways. There is no support desk, + no password reset and no undo — lose your recovery phrase and the name is gone, with + nobody able to help. Nothing here is moderated, so you will find things you would rather + not. And there is one layer this stack does not remove for you: your IP address. + A server still sees where a request came from, and so does whoever your traffic passes + through. If that matters, add Tor or a paid VPN — the two questions (who you are on the + account, where you are on the network) are independent, and Sirius only answers the + first. This is an alpha on a test network: the coins are free and worth nothing, + which is the honest place to try it before real money is involved. +

+ +

Three steps, about ten minutes

+ + Step one + Get a browser that reads it + Theseus resolves names straight from the chain. Ordinary sites keep working. + + + Step two + Take a name + Made in your browser, minted to your key. A few cents, no account, no renewal desk. + + + Step three + Put something on it + On-chain for something small, your own server, or the Sia network. Change it whenever. + +

+ +

+ ← Back to the choice · silentmode.st
+ Second thoughts are allowed. Nothing here has happened yet. +

+ +

+ + + diff --git a/choose/index.html b/choose/index.html new file mode 100644 index 0000000..38124d4 --- /dev/null +++ b/choose/index.html @@ -0,0 +1,258 @@ + + + + + +Choose — Silent Mode + + + + + + + + + + + + + + + + +

+ +

Silent Mode

Two internets. Twice over.

The web you use every day is owned. Companies decide which names exist, + which pages load, and whose voice carries. Registrars record who bought what. Card + networks and banks sit in the middle of every payment. The browser you are reading this + in reports home, and so does most of what it loads. There are privacy-forward providers + that will hold your identity on your behalf — but they still hold it, and a + court order still reaches them. Sirius removes the surface instead: names you hold by + key, pages nobody can pull, payment with no card and no bank, and a browser with nobody + to report to. Anonymous by default, not by exception. Whether you want to + use it or build on it, it starts the same way: something you install, + and a name that is actually yours.

+ + +

+ First choice +

The web you browse

Where you read, post, and are read. Pick the one you want to live in.

+ +

+ + + +

The blue one

Stay where it is easy.

Your account is a permission. It exists while the platform allows it, + under terms they rewrite when they like.
You are measured everywhere you go. The browser reports home, the pages + report home, and the profile follows you between them. Attention is the business + model, so being watched is not a bug — it is the system.
What you publish stays up until it does not. Moderation is theirs, + appeals go to them, and the reasons need not be given.
The reach you built is not portable. Leave, and the audience stays + behind.

+ It works. Mostly. → + + + + +

The red one

Step outside it.

No account, anywhere. No email, no sign-up, no password to reset. + Nothing to suspend, because nothing was granted.
A browser with nobody to report to. Theseus resolves names straight + from the chain — no lookup service in the middle logging what you typed.
A name that is yours by key, not by permission. Held on a public + ledger; no registrar stands between you and it, and none of them learns your + name to give you one.
Pages nobody can pull. On your own server, spread across strangers + who are paid to keep it, or inside a transaction the whole network stores.
Nobody to petition, because nobody is in charge. That cuts both ways, + and it is the honest trade.

+ Show me → + + +

+ + +

+ Second choice +

The web you build on

If you ship things, the question repeats one layer down — and this time the + gatekeepers have invoices, and a record of who paid them.

+ +

+ + + +

The blue one

Rent it, like everyone.

Anonymous only by exception. The default path binds the name to your + legal identity — WHOIS/RDAP holds the registrant data, ICANN requires it be + accurate, and the card ties it all together. Privacy providers like Njalla take + Monero and behave well — pair them with Tor or a VPN and the real-world privacy + is genuinely good. Pay with a bank card, and none of it applies. Either way, the + provider still holds what they were told and can be compelled to produce + it.
Renewal is the model, and it is a reasonable one. A yearly fee keeps + the namespace alive — unused names return to the pool instead of being hoarded + forever, and the registrar has a business that survives. That part is fine. + Sirius works the same way for the same reason. What differs is who holds the + record and can be leaned on to change it.
Suspension is a supported feature. Registrars act on court orders, UDRP + rulings and their own policy — by design, not by failure.
Every layer keeps a veto, and a bank sits under all of them. Host, + CDN, certificate authority, payment processor. Any one can decline.
It is genuinely good infrastructure. Fast, cheap, supported, and + someone answers the phone. That is the deal you are making.

+ The conventional stack → + + + + +

The red one

Own the name outright.

Sirius.x — names and hosting, paid in crypto

Anonymous by default, not by exception. No account, no email, no card, + no bank — because the stack does not support them. Nothing to compel out of a + provider that never held it.
Payment is peer to peer. You pay in crypto, direct to the seller, with + no processor deciding whether you may and no bank keeping a record of the + purchase. Add Tor or a VPN to cover the network layer, which nothing else can + do for you — no stack removes your IP.
The name is a certificate you hold. A CashToken on Bitcoin Cash — your + key controls it, and there is no company in the middle to ask.
Host it however you like. Your own server, the Sia storage network, or + on-chain for something small. Repoint it whenever, for free.
The whole stack is yours to run. Browser, resolver, indexer, registry — + a node plus a small BNS-only indexer fits a one-core VPS. Any TLD works; the + protocol has no allowlist.

+ Find a name on Sirius → + + +

+ +

+ Running on Bitcoin Cash chipnet — an alpha on a test network, free to try, and + honest about being early.
+ You are reading this on silentmode.st, the + ordinary-web face of the project. The same pages served the other way live at + silentmode.bch. +

+ +

+ + + diff --git a/choose/registrars/index.html b/choose/registrars/index.html new file mode 100644 index 0000000..3d4cac3 --- /dev/null +++ b/choose/registrars/index.html @@ -0,0 +1,157 @@ + + + + + +The conventional stack — Silent Mode + + + + + + + + + + + + + + + + +

+ + +

Rent it, like everyone.

This is the stack almost every site on the internet is built on. It is + mature, it is inexpensive, and it is very good at its job. It is also five separate + companies, each of whom can independently decide your project is over — and every one + of them keeps a record that reaches back to you.

+ +

+ The identity bind, and its limits. The default path binds a domain to a verified + legal identity: ICANN's registrar accreditation agreement obliges registrars to hold + accurate registrant data, WHOIS/RDAP publishes some of it, and the card or bank transfer + ties the record together. Privacy-forward registrars like Njalla or MyNymBox exist — + they take Monero, do not require a legal name, and behave well. If you also connect over + Tor or a paid VPN and do not volunteer personal details, the real-world privacy you get + from them is genuinely good.

+ But the mechanism is different. Those providers hold an identity, or a payment, + or a network address on your behalf, and can be compelled to produce what they + have. Anyone who paid with a bank card, or opened an account with an email that reaches + back to them, has not really used the privacy path at all — they have used a privacy + brand attached to the ordinary rails. The conventional stack is + anonymous only by exception, and the exception is compellable. Sirius is + anonymous by default — the identity, the payment record, and the account were + never collected, because the stack cannot collect them. +

+ +

Who holds what

Registrar GoDaddy, Namecheap, Cloudflare

Leases you the name, yearly. Can suspend or transfer it on a + court order, a UDRP ruling, or its own policy — and must, by contract with the + registry.

Host AWS, Hetzner, DigitalOcean

Runs the machine. Can terminate under acceptable-use terms, + usually with notice, sometimes without.

CDN / proxy Cloudflare, Fastly

Sits in front of your traffic. Can stop carrying it — and has, + publicly, for customers who broke no law.

Certificate authority Let's Encrypt, DigiCert

Vouches that you are you. Can revoke, at which point browsers + refuse the connection regardless of who is right.

App store / payments Apple, Google, Stripe

If money or an app is involved, two more parties with terms and a + right to decline.

+ +

What it costs

+ + + + + + + +

Item	Typical	Note
.com, first year	$1–12	usually a promotional rate
.com, renewal	$12–20/yr	the real price; wholesale is ~$9.59
Small VPS	$4–8/mo	plus your time
TLS certificate	$0	Let's Encrypt, genuinely free
Renewal	every year	keeps the namespace alive; abandon a name and it returns to the pool. Fair enough.

+ +

+ To be fair to it. This stack is fast, well documented, supported at 3am, and + integrates with everything. The vetoes above also remove phishing sites, malware hosts + and worse — they exist for reasons, and most of the time they are used reasonably. If + you are shipping a normal business, this is the sensible default and it is not close. + The alternative gives up the support desk along with the gatekeeper. +

+ +

Sirius removes two of these surfaces — the one that decides whether the name + is still yours, and the one that could ever be asked what you paid or who you are. + Not held on your behalf; not held at all. The rest of your choices stay open. Same + day, few cents, no account, no card.

+ See what a name costs there → +

+ +

+ ← Back to the choice · silentmode.st
+ Company names are examples of each layer, not endorsements or accusations. +

+ +

+ + + diff --git a/choose/stay/index.html b/choose/stay/index.html new file mode 100644 index 0000000..d7337a2 --- /dev/null +++ b/choose/stay/index.html @@ -0,0 +1,132 @@ + + + + + +You took the blue one — Silent Mode + + + + + + + + + + + + + + + + +

+ + +

Nothing changes. That is the point.

The conventional web is fast, free at the point of use, and mostly + excellent. Billions of people use it every day and are perfectly well served. We are + not going to pretend it is a dystopia — but it is worth being clear about what the + arrangement actually is, because it is easy to forget you made one.

+ +

The bargain, stated plainly

Your account is a permission, not a possession. + It exists because a company allows it to, under terms they can change. That is + not a conspiracy; it is what a terms-of-service relationship is.

Your domain is on the registrar's record. + Registration is yearly — that part is fine, and the same shape as any name + service that needs to recycle unused names. What matters is what a court order or + UDRP ruling can do to it while the registrar holds that record.

Attention is the business model. + Services that cost nothing are paid for by measuring what you do and selling + access to your attention. Being observed is not a flaw in that design — it is the + design working.

Reach is not portable. + The audience you build lives inside the platform. Leaving does not take it with + you, which is what makes leaving expensive.

Every layer keeps a veto. + Registrar, host, CDN, certificate authority, app store, payment processor. Any + one of them can decline, and each of them sometimes does.

+ +

+ To be fair to it. Those vetoes also stop fraud, take down malware and remove + genuinely vile material, and the people operating them are mostly trying to get it + right. The support desk is real, the uptime is excellent, and someone answers when it + breaks. A system with nobody in charge gives all of that up too. Anyone selling you the + alternative without mentioning that is selling you something. +

+ +

Carry on, then

+ No hard feelings. The ordinary web is right through here.

+ Search + Wikipedia + Video + Forums + News +

+ +

Still curious what the other one actually does? It costs nothing to look, and + nothing on this machine changes until you install something.

+ Show me the other one → +

+ +

+ ← Back to the choice · silentmode.st +

+ +

+ + + diff --git a/deviant/anthemus/index.html b/deviant/anthemus/index.html new file mode 100644 index 0000000..5356e02 --- /dev/null +++ b/deviant/anthemus/index.html @@ -0,0 +1,252 @@ + + + + + + Anthemus — Native Bitcoin Cash DEX + + + + + + + + + +

+ Deviant + +

+ +

+ + +

Anthemus

Decentralized exchange

+ +

One of the two markets under Agora — the trading floor for what the mechanism can't price alone.

+ +

Potidaea handles counterparty-free swaps for backed assets — the price is the mechanism, no other participant needed. Anthemus handles everything else: Token-class assets, wrapped foreign coins, cross-chain price discovery — the parts of the ecosystem where a market has to emerge rather than be enforced.

+ +

Order book plus AMM over one engine. Swap is the exchange with order-making automated; the AMM is a maker on the same book. A single Deposit rail brings assets in from every supported chain — asset × chain → unified USD on Bitcoin Cash — without a per-stablecoin pair matrix.

+ +

Native to Bitcoin Cash. No bridges to trust, no custody to grant. The BCH base layer is the settlement layer.

+ +

— The Anthemus interface

Swap

One-click trade against the order book. Order-making automated; you pick the pair and the amount.

Exchange

Pro grid — chart, book, order form. Full-depth market data, limit orders, historical fills.

Deposit

Bring assets in from EVM, Tron, Solana, Bitcoin. Ends as unified USD on BCH — one balance, one currency.

+ +

+ Open Anthemus + About Agora +

+ + + + diff --git a/deviant/brand-redirect.html b/deviant/brand-redirect.html new file mode 100644 index 0000000..78b1651 --- /dev/null +++ b/deviant/brand-redirect.html @@ -0,0 +1,15 @@ + + + + +Deviant — Brand assets + + + + + + +

Redirecting to the Deviant brand gallery…

+ + + diff --git a/deviant/brand/README.md b/deviant/brand/README.md new file mode 100644 index 0000000..433307e --- /dev/null +++ b/deviant/brand/README.md @@ -0,0 +1,106 @@ +# Deviant — Brand assets + +Canonical brand assets for the Deviant project. Source of truth for logos, icons, +and social-media cards. All primary assets are **SVG** (resolution-independent, +editable in code); PNG exports live under `source/exports/` when tooling +generates them. + +## Contents + +| Path | Purpose | +|---|---| +| [`palette.md`](palette.md) | Color tokens + typography, extracted from the landing page CSS | +| [`logo/`](logo/) | Wordmarks and combination marks | +| [`icon/`](icon/) | App icons, favicons, the D-mark alone | +| [`social/`](social/) | Open Graph, Twitter card, avatar | +| [`source/`](source/) | Editable working files, exports, raw art | + +## Voice — one paragraph + +> Deviant exists to enable resistance — by giving users on-chain experience that +> intermediation cannot mediate. + +Tagline (short): **Power Your Ideas.** +Tagline (subline): *A response to a default trajectory.* + +## The mark + +The Deviant mark is a **stylized "D" as an orbital crescent** on a starfield, +with a single acid-yellow dot orbiting the outer ring. It reads two ways: +- Letterform: `D` for Deviant. +- Astronomical: a partial planetary disc with a satellite — the "deviation from + the default trajectory" imagery encoded in the logo itself. + +Never redraw the orbital dot inside the ring, never tint it any other color — +the acid yellow (`--acid`) is the load-bearing accent across the whole system. + +## Themes + +Both themes ship — the landing page respects `data-theme="editorial"` in +`localStorage`; assets should exist for both: + +- **signal** (default): starfield ink on cool deep-space blue. Acid `#d6ff3d`. +- **editorial**: near-monochrome charcoal, more graphic. Acid `#c6ff00`. + +See [`palette.md`](palette.md) for exact values. + +## What to use where + +| Surface | Asset | Size | +|---|---|---| +| Browser tab / OS icon | `icon/favicon.svg`, `icon/icon-512.svg` | 64 / 512 | +| App shell splash | `icon/icon-512.svg` | 512 (matches `shells/app/public/icon.svg`) | +| Website header, README | `logo/deviant-wordmark.svg` | 720×180 | +| Print / dark surfaces | `logo/deviant-mark.svg` | 256×256, no background | +| Print / light surfaces | `logo/deviant-mark-onlight.svg` | 256×256, inverted | +| **Open Graph** (Facebook, LinkedIn, Slack unfurls) | `social/og-1200x630.svg` | 1200×630 | +| **Twitter/X post card** (summary_large_image) | `social/twitter-card-1200x675.svg` | 1200×675 (16:9, current spec) | +| **Twitter/X header** (profile banner) | `social/twitter-header-1500x500.svg` | 1500×500 (3:1, with profile-photo safe zone) | +| **Facebook page cover** | `social/facebook-cover-820x312.svg` | 820×312 desktop / 640×360 mobile-safe | +| **LinkedIn company banner** | `social/linkedin-banner-1584x396.svg` | 1584×396 (with profile-photo safe zone) | +| **Instagram feed post** | `social/instagram-square-1080x1080.svg` | 1080×1080 (also works for Discord/Threads) | +| **Social avatar** (X, GitHub, Discord, LinkedIn) | `social/avatar-400x400.svg` | 400×400, round-crop-safe | + +## Fonts + +Every SVG with text loads the website's own faces (Fraunces + DM Sans + +JetBrains Mono) via a `` +block inside the SVG. That means: + +- **In a browser** (opening the SVG directly, or embedding via ``) the + Google fonts fetch and render — same as the website. +- **In `rsvg-convert` / most SVG-to-PNG renderers** the `@import` is IGNORED + (they don't fetch remote CSS) and the fallback stack applies: Georgia for + display, system sans for body. If pixel-perfect PNG exports matter, either + install Fraunces + DM Sans locally on the export machine, or export from a + browser screenshot instead (see `source/README.md`). + +The ` + + + +

Deviant brand

Logos, icons and social-media assets. All primary files are SVG — scale-independent, editable in code, and (where text appears) load the site's own fonts via @import. Click any file name to open the raw SVG. + Source: brand/README.md · brand/palette.md

+ +

Uploading to social media? SVG isn't accepted for profile avatars, headers, or post images by Twitter/X, GitHub, Discord, LinkedIn, Instagram, Facebook, or Slack. Every card below has a PNG link next to the SVG path — use those. Full PNG set at source/exports/.

+ +

Icons

2 files

App icon (512)

OS launcher, PWA install, app-shell splash. Byte-identical to shells/app/public/icon.svg.

icon/icon-512.svgPNG512 × 512

Favicon

Browser tab / tiny sizes. Simplified — no starfield, no glow.

icon/favicon.svg64 · 3264 × 64

+ +

Logos

3 files

Mark — on dark

Orbital-crescent D + acid dot. For dark surfaces.

logo/deviant-mark.svgPNG 512256 × 256

Mark — on light

Inverted for print / light backgrounds. Ring softens, acid dot deepens to olive.

logo/deviant-mark-onlight.svgPNG 512256 × 256

Wordmark

Mark + “Deviant” in Fraunces + “POWER YOUR IDEAS.” tagline. Header lockup.

logo/deviant-wordmark.svgPNG 1440720 × 180

+ +

Social — cards & banners

7 files

Open Graph

Facebook / LinkedIn / Slack link unfurls. The default meta og:image aspect.

social/og-1200x630.svgPNG1200 × 630

Twitter/X post card

summary_large_image spec — 16:9. Use in twitter:image meta tag.

social/twitter-card-1200x675.svgPNG1200 × 675

Twitter/X profile header

Profile banner — orbital ring on the right, wordmark shifted past the ~200px avatar overlap in the lower-left.

social/twitter-header-1500x500.svgPNG1500 × 500

Twitter/X header — deviation variant

Uses the site's hero deviation chart (same paths from deviant_website.html) on the right. Same avatar-safe copy zone as the primary header.

social/twitter-header-deviation-1500x500.svgPNG1500 × 500

Facebook page cover

Desktop-sized. Mobile-safe zone is ~640×360 centered.

social/facebook-cover-820x312.svgPNG820 × 312

LinkedIn company banner

Copy sits right of center to clear the lower-left profile-photo overlap.

social/linkedin-banner-1584x396.svgPNG1584 × 396

Instagram / Threads / Discord

Square 1:1 feed post. Also usable as a large Discord embed.

social/instagram-square-1080x1080.svgPNG1080 × 1080

+ +

Avatar

1 file · rendered square + round

Square (as SVG ships)

Direct render of the file — the mark on the starfield square.

social/avatar-400x400.svg400 · 1024400 × 400

Circular crop preview

How Twitter / X / GitHub / Discord actually display it. The mark is centered with margin so a circle keeps it whole.

social/avatar-400x400.svg400 · 1024400 × 400

+ + + + diff --git a/deviant/brand/logo/deviant-mark-onlight.svg b/deviant/brand/logo/deviant-mark-onlight.svg new file mode 100644 index 0000000..f7ec4f5 --- /dev/null +++ b/deviant/brand/logo/deviant-mark-onlight.svg @@ -0,0 +1,5 @@ + diff --git a/deviant/brand/logo/deviant-mark.svg b/deviant/brand/logo/deviant-mark.svg new file mode 100644 index 0000000..a877f5c --- /dev/null +++ b/deviant/brand/logo/deviant-mark.svg @@ -0,0 +1,11 @@ + diff --git a/deviant/brand/logo/deviant-wordmark.svg b/deviant/brand/logo/deviant-wordmark.svg new file mode 100644 index 0000000..0df46b0 --- /dev/null +++ b/deviant/brand/logo/deviant-wordmark.svg @@ -0,0 +1,21 @@ + diff --git a/deviant/brand/palette.md b/deviant/brand/palette.md new file mode 100644 index 0000000..d3c011d --- /dev/null +++ b/deviant/brand/palette.md @@ -0,0 +1,70 @@ +# Deviant — Palette & Typography + +Extracted from `Parameters/webfiles/deviant_website.html` (`:root` CSS variables). +The landing page is the source of truth; if these values ever drift, the +website wins. + +## Themes + +Two live themes swap via `data-theme` on ``: + +- `data-theme="signal"` — default. Deep-space blue, cool. +- `data-theme="editorial"` — near-monochrome. High-contrast, more graphic. + +## `signal` (default) + +| Token | Hex / value | Role | +|---|---|---| +| `--sky-deep` | `#050810` | Page ground — the deepest black | +| `--sky-mid` | `#0a0f1c` | Elevated surfaces (cards, hero) | +| `--sky-rim` | `#131a2a` | Borders, dividers | +| `--ink-soft` | `#b8c2d4` | Secondary text | +| `--ink` | `#d6dde9` | Primary text | +| `--ink-bright` | `#f1f4fa` | Headings, emphasis | +| `--muted` | `#6a7488` | Captions, timestamps | +| `--acid` | `#d6ff3d` | Load-bearing accent — CTAs, orbital dot, focus rings | +| `--acid-glow` | `rgba(214,255,61,0.55)` | Halo behind the acid dot | +| `--acid-halo` | `rgba(214,255,61,0.22)` | Softer diffusion | +| `--acid-dim` | `rgba(214,255,61,0.08)` | Idle-state tint | +| `--rust-deep` | `#6b2a1c` | Rare warning / archival accent | +| `--star-faint` | `rgba(255,255,255,0.22)` | Starfield — background layer | +| `--star-mid` | `rgba(255,255,255,0.38)` | Starfield — mid layer | +| `--star-bright` | `rgba(255,255,255,0.58)` | Starfield — near-foreground | + +## `editorial` + +| Token | Hex / value | Role | +|---|---|---| +| `--sky-deep` | `#050505` | Page ground | +| `--sky-mid` | `#0a0a0a` | Elevated surfaces | +| `--sky-rim` | `#161616` | Borders | +| `--ink` | `#f2f2f2` | Primary text | +| `--ink-bright` | `#ffffff` | Headings | +| `--ink-soft` | `#d2d2d2` | Secondary text | +| `--muted` | `#9a9a9a` | Captions | +| `--acid` | `#c6ff00` | Accent — slightly cooler than signal's | +| `--acid-glow` | `rgba(198,255,0,0.60)` | | +| `--acid-halo` | `rgba(198,255,0,0.34)` | | +| `--acid-dim` | `rgba(198,255,0,0.16)` | | + +## Typography + +| Face | Where | Weights loaded | +|---|---|---| +| **Fraunces** | Display headlines, hero, wordmark | 300, 400, 500, 600 (opsz 9..144) | +| **DM Sans** | Body, UI, buttons, nav | 400, 500, 600, 700, 800 | +| **JetBrains Mono** | Code, hashes, addresses (technical surface) | 400, 500 | +| **DM Mono** | Numeric readouts, receipts, tote-style data | 400, 500 | + +Load line (Google Fonts): + +```html + +``` + +## Print / static asset defaults + +For assets shipped as SVG (icons, social cards, logos) that must render without +CSS-var lookups: **hard-code the `signal` values above.** The `data-theme` +mechanism is HTML/CSS-only; a raw SVG loaded into Slack or a Twitter feed does +not carry the palette with it. diff --git a/deviant/brand/social/avatar-400x400.svg b/deviant/brand/social/avatar-400x400.svg new file mode 100644 index 0000000..17df1ea --- /dev/null +++ b/deviant/brand/social/avatar-400x400.svg @@ -0,0 +1,24 @@ + diff --git a/deviant/brand/social/facebook-cover-820x312.svg b/deviant/brand/social/facebook-cover-820x312.svg new file mode 100644 index 0000000..5eb617d --- /dev/null +++ b/deviant/brand/social/facebook-cover-820x312.svg @@ -0,0 +1,36 @@ + diff --git a/deviant/brand/social/instagram-square-1080x1080.svg b/deviant/brand/social/instagram-square-1080x1080.svg new file mode 100644 index 0000000..401bbd4 --- /dev/null +++ b/deviant/brand/social/instagram-square-1080x1080.svg @@ -0,0 +1,44 @@ + diff --git a/deviant/brand/social/linkedin-banner-1584x396.svg b/deviant/brand/social/linkedin-banner-1584x396.svg new file mode 100644 index 0000000..e0a4e19 --- /dev/null +++ b/deviant/brand/social/linkedin-banner-1584x396.svg @@ -0,0 +1,42 @@ + diff --git a/deviant/brand/social/og-1200x630.svg b/deviant/brand/social/og-1200x630.svg new file mode 100644 index 0000000..ca0ca2a --- /dev/null +++ b/deviant/brand/social/og-1200x630.svg @@ -0,0 +1,47 @@ + diff --git a/deviant/brand/social/twitter-card-1200x675.svg b/deviant/brand/social/twitter-card-1200x675.svg new file mode 100644 index 0000000..515a838 --- /dev/null +++ b/deviant/brand/social/twitter-card-1200x675.svg @@ -0,0 +1,43 @@ + diff --git a/deviant/brand/social/twitter-header-1500x500.svg b/deviant/brand/social/twitter-header-1500x500.svg new file mode 100644 index 0000000..600a55e --- /dev/null +++ b/deviant/brand/social/twitter-header-1500x500.svg @@ -0,0 +1,52 @@ + diff --git a/deviant/brand/social/twitter-header-deviation-1500x500.svg b/deviant/brand/social/twitter-header-deviation-1500x500.svg new file mode 100644 index 0000000..7cfe3fc --- /dev/null +++ b/deviant/brand/social/twitter-header-deviation-1500x500.svg @@ -0,0 +1,85 @@ + diff --git a/deviant/brand/source/README.md b/deviant/brand/source/README.md new file mode 100644 index 0000000..c496385 --- /dev/null +++ b/deviant/brand/source/README.md @@ -0,0 +1,41 @@ +# Working files & exports + +Author SVGs edit-in-place under `brand/{logo,icon,social}/`. This directory is +for **derivative** files that shouldn't clutter the primary directories. + +## Structure + +- `exports/` — PNGs generated from the primary SVGs. Do not check in unless a + specific delivery pipeline requires them. +- `sketches/` — WIP art, alternates, rejected variants (kept for provenance). + +## Exporting to PNG + +Any of these work; pick what's installed. + +```bash +# rsvg-convert (librsvg — smallest, fastest) +rsvg-convert -w 1200 -h 630 ../social/og-1200x630.svg -o exports/og-1200x630.png + +# Inkscape CLI (higher-fidelity text rendering) +inkscape ../social/og-1200x630.svg --export-type=png --export-filename=exports/og-1200x630.png --export-width=1200 + +# ImageMagick (falls back if the above aren't installed) +magick -density 300 -background none ../social/og-1200x630.svg -resize 1200x630 exports/og-1200x630.png +``` + +**Font gotcha:** Fraunces and DM Sans are Google Fonts. If the renderer does +not have them installed locally, the PNG will show the fallback (Georgia / +system sans). For high-fidelity social exports, install both: + +```bash +# Ubuntu / Debian +sudo apt-get install fonts-liberation +# Then drop Fraunces + DM Sans .ttf files into ~/.fonts/ and run fc-cache -fv +``` + +Or export from a browser (`file://` open + screenshot at the target size) — +Chrome/Firefox honour the Google Fonts `` if the SVG references it, +though our brand SVGs use plain `` with a system-safe stack, so the +Fraunces + DM Sans rendering happens only when those faces are locally +available. diff --git a/deviant/brand/source/exports/avatar-1024.png b/deviant/brand/source/exports/avatar-1024.png new file mode 100644 index 0000000..69bb390 Binary files /dev/null and b/deviant/brand/source/exports/avatar-1024.png differ diff --git a/deviant/brand/source/exports/avatar-400.png b/deviant/brand/source/exports/avatar-400.png new file mode 100644 index 0000000..b944e78 Binary files /dev/null and b/deviant/brand/source/exports/avatar-400.png differ diff --git a/deviant/brand/source/exports/facebook-cover-820x312.png b/deviant/brand/source/exports/facebook-cover-820x312.png new file mode 100644 index 0000000..e81eb82 Binary files /dev/null and b/deviant/brand/source/exports/facebook-cover-820x312.png differ diff --git a/deviant/brand/source/exports/favicon-32.png b/deviant/brand/source/exports/favicon-32.png new file mode 100644 index 0000000..4651327 Binary files /dev/null and b/deviant/brand/source/exports/favicon-32.png differ diff --git a/deviant/brand/source/exports/favicon-64.png b/deviant/brand/source/exports/favicon-64.png new file mode 100644 index 0000000..b2a1508 Binary files /dev/null and b/deviant/brand/source/exports/favicon-64.png differ diff --git a/deviant/brand/source/exports/icon-512.png b/deviant/brand/source/exports/icon-512.png new file mode 100644 index 0000000..02b96bc Binary files /dev/null and b/deviant/brand/source/exports/icon-512.png differ diff --git a/deviant/brand/source/exports/instagram-1080.png b/deviant/brand/source/exports/instagram-1080.png new file mode 100644 index 0000000..417127d Binary files /dev/null and b/deviant/brand/source/exports/instagram-1080.png differ diff --git a/deviant/brand/source/exports/linkedin-banner-1584x396.png b/deviant/brand/source/exports/linkedin-banner-1584x396.png new file mode 100644 index 0000000..d3c3de0 Binary files /dev/null and b/deviant/brand/source/exports/linkedin-banner-1584x396.png differ diff --git a/deviant/brand/source/exports/mark-512.png b/deviant/brand/source/exports/mark-512.png new file mode 100644 index 0000000..d1226ae Binary files /dev/null and b/deviant/brand/source/exports/mark-512.png differ diff --git a/deviant/brand/source/exports/mark-onlight-512.png b/deviant/brand/source/exports/mark-onlight-512.png new file mode 100644 index 0000000..9e3e8f4 Binary files /dev/null and b/deviant/brand/source/exports/mark-onlight-512.png differ diff --git a/deviant/brand/source/exports/og-1200x630.png b/deviant/brand/source/exports/og-1200x630.png new file mode 100644 index 0000000..103c0c1 Binary files /dev/null and b/deviant/brand/source/exports/og-1200x630.png differ diff --git a/deviant/brand/source/exports/twitter-card-1200x675.png b/deviant/brand/source/exports/twitter-card-1200x675.png new file mode 100644 index 0000000..ee86b47 Binary files /dev/null and b/deviant/brand/source/exports/twitter-card-1200x675.png differ diff --git a/deviant/brand/source/exports/twitter-header-1500x500.png b/deviant/brand/source/exports/twitter-header-1500x500.png new file mode 100644 index 0000000..e48476a Binary files /dev/null and b/deviant/brand/source/exports/twitter-header-1500x500.png differ diff --git a/deviant/brand/source/exports/twitter-header-deviation-1500x500.png b/deviant/brand/source/exports/twitter-header-deviation-1500x500.png new file mode 100644 index 0000000..b805d2b Binary files /dev/null and b/deviant/brand/source/exports/twitter-header-deviation-1500x500.png differ diff --git a/deviant/brand/source/exports/wordmark-1440.png b/deviant/brand/source/exports/wordmark-1440.png new file mode 100644 index 0000000..886e312 Binary files /dev/null and b/deviant/brand/source/exports/wordmark-1440.png differ diff --git a/deviant/deviant_mindmap.html b/deviant/deviant_mindmap.html new file mode 100644 index 0000000..ad46519 --- /dev/null +++ b/deviant/deviant_mindmap.html @@ -0,0 +1,537 @@ + + + + + +Deviant — The Map + + + + + + + + + + +

+ +

Marketing Mindmap · Bitcoin Cash · v2

Deviant

A tectonic shift in finance.

A non-custodial Bitcoin Cash wallet on the MBA Standard

+ The core distinction is what Deviant introduces: MBA backing + (intrinsic, consensus-enforced, redeemable with no counterparty) and the + counterparty-free ASM. BCH's UTXO + PoW + CashScript design is the + enabling substrate — not the differentiator. And one reframing underneath it all: + Bitcoin Cash satoshis are a unit of account, not a price. +

+ +

+ Marketing pillar + Tap any branch to expand · acid-green = the words that carry the pitch +

+ +

+
+ +

+ + +

The Paradigm

What Deviant actually is

Every existing asset — fiat, equity, real estate, crypto tokens — has a single point of failure: an issuer, custodian, or counterparty who can fail, freeze, or disappear.
Deviant removes it by construction — not by regulation, not by trust. A gold standard done by mathematics.
The differentiator is MBA backing + counterparty-free ASM. Consensus-enforced and economical at scale.

+ + +

The Mechanism · ASM

How it works

ASM — Automated Swap Mechanism. Swap any open-mint asset into any other with no DEX, no AMM, no oracle, no operator.
Every unit is self-backed — it carries its own BCH inside the UTXO at a fixed rate. Redemption is a plain spend; swaps are atomic single transactions enforced by consensus.
Universal Exchange Rate: rate A ÷ rate B — deterministic, no market needed.

+ + +

The MBA

Not a token. A new asset class.

An MBA (Mathematically / Minted Backed Asset) carries intrinsic, consensus-enforced BCH backing — unilaterally redeemable at a fixed rate, no custodian, no counterparty, purely by mathematics.
Properties: a guaranteed on-chain floor value; the rate is fixed and immutable at genesis; redemption is available 24/7 with no off-switch and no permission.
How it differs: a classical token has no locked peg and leans on intermediary trust and market sentiment. An MBA's value is enforced by the protocol with non-reversible rules.

+ + +

The Zero Properties

The pitch, in single words

Zero counterparty · zero intermediary · zero trust required.
Zero liquidity ceiling — any user, any amount, any time; supply expands to meet demand.
Zero fungibility barriers — every open-mint MBA shares one measurement system, interchangeable at an exact rate.
Zero complexity for founders · zero maintenance · zero ongoing contribution · zero dependence · zero friction. Don't trust, verify.

+ + +

Founders' Revenue

Earn without selling the asset

Founder fee on mint only (immutable after genesis). Redemption is free. Set at 1% on both sides, it creates a mathematically enforced ~2% round-trip spread.
Automated, perpetual revenue — the founder earns from activity, not from selling or holding the asset. No treasury to dump, no insider allocation.
A Revenue Acquisition Mechanism, not a sale: users acquire from the algorithm; the founder only collects the fee.
The 5% cap is a wallet/template guardrail, not a protocol ceiling — the protocol imposes no fee limit.

+ + +

Agora

A market with no analogue

Agora is what emerges when ASM and MBA launch work in combination — an emergent market that has no analogue anywhere.
Users swap directly at the protocol level — with no counterparty: no order book, no market maker, no listing gate. The market exists the moment the asset does.
Founders create an asset and earn — without ever selling it. Acquisition comes from the algorithm (ASM), not from a seller.
Liquidity is Poseidon — deep as an ocean: the protocol is the immutable liquidity provider, native, instant, and unlimited. Zero bootstrap, zero ceiling.

+ + +

The Proof

A working mechanism, not a claim

Validated on Bitcoin Cash chipnet across 135 snapshots. Live
~445 tests — the majority exercising MBAs across use cases, configurations, and adversarial / vulnerability scenarios: what MBAs can do, and whether they break. (The early 129 atomic swaps were the first proof the mechanism works.)
Result across all of it: 0 exploits · 100% peg integrity. Wallet core feature-complete; PWA beta live (chipnet/testnet, mainnet structurally absent).
The CTA asks the reader to verify a mathematical claim, not to pledge: Verify the contract · Read the spec · Audit the snapshots.

+ + +

Positioning

Why Deviant wins its lane

vs conventional tokens (ERC-20, BEP-20, and the like): they're financially and structurally disconnected from their base layer. MBAs are tied to it — one asset's success amplifies the whole ecosystem.
vs stablecoins: the bankruptcy-protection floor — on-chain recoverable value if the issuer fails, where a conventional stablecoin recovers $0.
vs DEX/exchanges: no order matching, no liquidity to bootstrap, no counterparty to wait for.
The volatility paradox: the asset marketed as "safe" fails its advertised property under stress; an MBA promises nothing it cannot keep.

+ + +

Platform Revenue

How Deviant earns — no fundraise

Revenue streams: ~0.5% fee on asset mint, voluntary marketing revenue-share · premium features for sophisticated users.
Olympic tier ladder — founders opt into promotion via Agora: Free → Bronze → Silver → Gold → Laurel.
(Possible) additional revenue from dApps, integrations and partnerships.
Deviant lets users generate revenue — as Bitcoin lets miners — but with less complexity. The platform's revenue is earned (only) from real economic activity.

+ + +

Platform Alignment

Inverting the extraction model

Public commitment: 25–50% of platform revenue to Bitcoin Cash infrastructure, scaling toward the higher figure.
Structural recognition of dependency, not philanthropy — "most projects extract from their chain; Deviant inverts that."
Direct, 24/7 transparent. Two tracks: protocol-level (nodes, CashScript) now; application-level later.
The base layer is the environment — predetermined, permanent, unaffected by what evolves within it.

+ + +

The Origin

Discovered, not created

The question that produced everything: "Is it possible to back assets without a counterparty?" — the same constraint Satoshi applied, followed honestly, without compromise, to its singular conclusion. No intermediaries, no counterparties, no trust assumptions.
The concept preceded the technology. Nothing accidental, nothing coincidence — the domain was discovered, not created.
The most important distinction: Deviant did not create these mathematical relationships — it discovered them. They existed before; the question navigated to them; the technology made them accessible — the CashScript upgrade on Bitcoin Cash.

+ + +

The Story

Go-to-market & narrative

The hero declares the negative first: "This is not a fundraise." It's a demonstration of a new paradigm.
Community first: reach the Bitcoin Cash community, then a wider audience with a product they've never experienced.
Founders must deliver first — usefulness generates revenue. The opposite of the 2017 ICO model that sold promises and delivered garbage.
Agora, the MBA and the ASM combination is a tectonic shift relative to the conventional financial system — consequences are unpredictable, and you are welcome to experience the new trajectory.

+ +

Discovered truths are permanent.

+ + +

Asset classes

~445

Tests passing

Exploits

100%

Peg integrity

+ +

The protocol rate is the gravitational center. Market prices orbit around it.

Deviant

Power Your Ideas.

+ +

+ + + + + diff --git a/deviant/deviant_website.html b/deviant/deviant_website.html new file mode 100644 index 0000000..fa66a82 --- /dev/null +++ b/deviant/deviant_website.html @@ -0,0 +1,15 @@ + + + + +Deviant — Power Your Ideas + + + + + + +

Redirecting to deviant.x…

+ + + diff --git a/deviant/index.html b/deviant/index.html new file mode 100644 index 0000000..4d2c875 --- /dev/null +++ b/deviant/index.html @@ -0,0 +1,939 @@ + + + + + + Deviant — Power Your Ideas + + + + + + + + + + + + Skip to content + + + + + +

+ +

A response to a default trajectory

When the institutional, technical, economic, and rhetorical forces all point in the same direction, the outcome they point toward becomes the default trajectory. Deviation from the trajectory requires active resistance. In a captured information environment with limited resistance capacity, the default trajectory is what occurs.

Deviant exists to enable that resistance — by giving users on-chain experience that intermediation cannot mediate.

+ + +

+ +

What this is

+ +

Deviant is the first wallet for an asset class that exists nowhere else — a Bitcoin‑Cash‑backed asset you can redeem at a fixed rate, at any time, with no issuer, no custodian, and no counterparty. Enforced by mathematics, not trust.

+ +

Permissionless mint, fixed rate, unlimited reservoir — the contract replaces the market maker, the liquidity provider, and the counterparty at once. Mint from a permissionless covenant; exit by burning your output back to its Bitcoin‑Cash floor; swap to any other permissionless‑mint asset in a single atomic transaction. No pool. No oracle. No one to ask.

+ +

Artemision

Create. Genesis in one transaction — core parameters sealed, irreversible.

Katalogos

The asset list. Every class, filterable across the backed ↔ non-backed spectrum and by use-case.

Agora

The market hub. Home to Potidaea — a counterparty-free automated swap mechanism — and Anthemus, a decentralized exchange.

+ +

No issuerNo custodianNo counterpartyNo token sale

Not a fundraise, not a pre‑mine. The contract is small enough to read end to end in an evening — read it, replay the chain, break it or trust it. The wallet reports facts the chain has already settled; it never asks you to trust it.

+ +

The mechanism · ASM

Every unit is self‑backed — it carries its own Bitcoin Cash inside the UTXO at a fixed rate. Redemption is a plain spend; a swap is a single atomic transaction, settled by consensus.

The Automated Swap Mechanism prices every exchange by the Universal Exchange Rate — rate A ÷ rate B — derived from genesis constants alone. No DEX, no AMM, no oracle, no operator. There is no approximately: the floor is an equality the contract enforces at consensus level. Deterministic, not probabilistic.

No counterpartyNo oracleNo poolNo operator

+ +

Agora — the market hub

Two markets under one roof. Potidaea is the native-BCH ASM — counterparty-free swaps priced by the Universal Exchange Rate, backing enforced at consensus level. Anthemus is the DEX — order-book and AMM for token-class assets and cross-chain price discovery. Together they cover every asset the wallet can hold.

Potidaea's market exists the moment an MBA does — no order book, no listing gate; a founder can create an asset and earn without ever selling it. Anthemus adds the trading floor for everything the mechanism can't price alone — Token-class assets, wrapped foreign coins, cross-chain settlement.

+ +

The proof

Not a hypothesis — a working mechanism, validated on the Bitcoin Cash chipnet across 287 snapshots.

564

Tests passing

52,998

Chipnet swaps

Exploits

100%

Peg integrity

The early atomic swaps proved the mechanism works; the bulk of the suite then exercised MBAs across use cases, configurations, and adversarial scenarios — what the assets can do, and whether they break. The wallet core is feature‑complete and a PWA beta is live on chipnet. The contract is small enough to read in an evening: verify it, replay the chain, break it or trust it.

+ +

Why it is different

A conventional token is disconnected from its base layer; an MBA is tied to it — so one asset's success amplifies the whole ecosystem.

Conventional tokens · ERC-20, BEP-20, …

No locked peg. Value rests on issuer reputation, demand, and traded liquidity — disconnected from any base‑layer floor.

The MBA

Value enforced by the protocol, not promised by an issuer. Price cannot fall below the mathematical floor.

Stablecoins

When the issuer fails, a conventional stablecoin recovers $0. An MBA carries an on‑chain bankruptcy‑protection floor.

DEX / exchanges

No order matching, no liquidity to bootstrap, no counterparty to wait for — the protocol is the exchange.

The volatility paradox: the asset marketed as "safe" fails its advertised property under stress. An MBA promises nothing it cannot keep — and because supply expands only against locked Bitcoin Cash, every asset launched amplifies the scarcity of the base layer rather than diluting it.

+ +

The economics — no fundraise

Revenue is earned from real activity, never raised. Like Bitcoin's own launch: no pre‑mine, no token sale.

Founder revenue

A mint‑only fee, immutable after genesis. Set at 1% on both sides, it creates a mathematically enforced ~2% round‑trip spread — automated revenue from activity, not from selling the asset.

Platform revenue

Three streams: a voluntary marketing revenue‑share on the Olympic tier ladder (Free → Bronze → Silver → Gold → Laurel), a ~0.5% wallet swap fee, and premium features.

+ +

Bitcoin Cash alignment

Most projects extract from their chain. Deviant inverts that — a public commitment of 25–50% of platform revenue to Bitcoin Cash infrastructure, scaling toward the higher figure.

Structural recognition of dependency, not philanthropy. The base layer is the environment — predetermined, permanent, unaffected by what evolves within it. Stars hang without visible support; planets wander yet hold their courses, bound by an unseen force. So here: mathematics, not authority, holds the system together.

+ +

Where to begin

+ +

— 01

The Wallet

On-chain experience without intermediation. Send, receive, and mint value-bearing assets the captured layer cannot mediate. Chipnet beta today — real testnet, no real funds.

Open the wallet

+ + + +

— 02

Potidaea · Automated Swap Mechanism

Counterparty-free by design. Swaps between BCH and backing-anchored assets are priced by the covenant — the mechanism that makes an MBA economy possible without pooled liquidity.

Enter Potidaea

+ + + +

— 03

Anthemus · Decentralized Exchange

Order-book plus AMM for token-class assets and cross-chain price discovery. Participants price the market; the interchain settlement hub's public trading floor.

Enter Anthemus

+ +

Power Your Ideas.

+ + +

+ + + + diff --git a/deviant/potidaea/index.html b/deviant/potidaea/index.html new file mode 100644 index 0000000..b2f2dec --- /dev/null +++ b/deviant/potidaea/index.html @@ -0,0 +1,283 @@ + + + + + + Potidaea — Native-BCH Automated Swap Mechanism + + + + + + + + + +

+ Deviant + +

+ +

+ + +

Potidaea

Counterparty-free automated swap mechanism

+ +

One of the two markets under Agora — the one where the price is the mechanism.

+ +

Potidaea handles counterparty-free swaps for backed assets. Every exchange is priced by the Universal Exchange Rate — rate A ÷ rate B, derived from genesis constants alone — and settled by consensus. No pool. No oracle. No one to ask.

+ +

The contract is the market maker, the liquidity provider, and the counterparty at once. Mint from a permissionless covenant; exit by burning your output back to its Bitcoin Cash floor; swap to any other permissionless-mint asset in a single atomic transaction.

+ +

Named after Ποτίδαια — the city of Poseidon — because the liquidity behaves like ocean: MBA↔MBA depth is infinite from moment zero. Backing is liquidity, elastic-mint. There is no bootstrap, no seeding, no thin-pairs, no slippage in the usual sense.

+ +

— The Potidaea flow

Genesis

One transaction seals the core parameters — backing rate, category, mint policy. Immutable after mint; no upgrade key, no admin.

Swap

Any address can claim against the reservoir. Sequencer + sharded reservoir + auto-assign — measured at 196 swaps/sec on a local BCHN node.

Redeem

Burn the output back to its BCH floor at any time. The floor is an equality the contract enforces at consensus level — not an approximation.

+ +

52,998

Chipnet swaps

Exploits

100%

Peg integrity

~52k

Per 32 MB block

+ +

+ Enter Potidaea + About Agora +

+ + + + diff --git a/favicon.svg b/favicon.svg new file mode 100644 index 0000000..d963e50 --- /dev/null +++ b/favicon.svg @@ -0,0 +1,9 @@ + diff --git a/helios/index.html b/helios/index.html new file mode 100644 index 0000000..494b548 --- /dev/null +++ b/helios/index.html @@ -0,0 +1,128 @@ + + + + + +Helios — searching the decentralized web — Silent Mode + + + + + + + + + + + + + + + + + +

☀️

Helios + designed · not yet built +

A search engine for the decentralized web — no central crawler to + trust, no authority to rank, no advertiser to serve. Named for the sun, which + sees everything and takes no side. Reads what the chain says exists and lets you + find it by name, by tag, by content, by who you trust.

+ +

The problem

Every search engine that matters today is one company deciding what the + web looks like. It crawls what it wants, indexes what it chooses, ranks by what pays + it, and drops what its lawyers dislike. On the ordinary web that is livable — most + sites are on cooperating hosts and there is a shared understanding of what "the + open web" means. On a network where nobody hosts anything centrally and nobody + approves what gets published, a company-run search would recreate exactly the + gatekeeper the network was built to escape.

A search engine for the decentralized web has to be built with the + same rules as the network it searches: no crawler that any single party runs, no + ranking any single party decides, and no listing any single party can remove. + That is Helios.

+ +

How Helios will work

The chain is the truth about what exists. + Every BNS name registered on Bitcoin Cash is a piece of a public index — + no crawler needed to find them. Helios reads the same records every resolver + reads, plus the on-chain APS1 app listings from + Prometheus, plus any signed metadata records + (title, description, tags) that publishers attach to their names.
Content indexing is opt-in. + For the bytes behind a name (an HTML page, a document), Helios only + indexes what the publisher marks as indexable — a signed + idx record with a category and tag list. Nobody + crawls anyone. If a site does not want to be searchable, it isn't.
Ranking is by signed endorsement, not by an algorithm nobody understands. + Names on your trust list carry weight for you. Names on nobody's trust + list appear at the bottom. Nothing paid ever floats. Change trust lists, change + results — the ranking is transparent because it is yours.
The frontend can run anywhere. + Helios's index is data on chain plus data on Sia — a spec, not a service. + The reference frontend runs at helios.silentmode.bch, + but any client can build its own index and its own UI from the same public + substrate. If Silent Mode's Helios goes down, another Helios exists tomorrow.

+ +

What it will NOT do

Track you

No accounts, no cookies, no per-user history. Every search is the same request + shape; the server has nothing to profile.

Rank by payment

There is no sponsored-result slot, no bidding, no advertising surface at all. + Storage costs money; searches don't.

Moderate content

Helios shows you what your trust list vouches for. Filtering out categories or + publishers is your subscription choice, not the engine's policy.

Depend on one operator

The index is public. If Silent Mode stops hosting Helios tomorrow, the data + and the spec are still there — anyone can run their own.

+ +

Status: designed, not built. This page is a placeholder for + the intent. The record types (idx, tag) + need to be specified in the BNS protocol addendum, the reference frontend needs to be + built, and a trust-list subscription format needs to be settled with + Hermes so both use the same shape. Watch this page.

+ +

+ + + + + diff --git a/hephaestus.x/forge/index.html b/hephaestus.x/forge/index.html new file mode 100644 index 0000000..72d21bf --- /dev/null +++ b/hephaestus.x/forge/index.html @@ -0,0 +1,142 @@ + + + + + +Hephaestus — the forge + + + + + + +

+ +

⚒️

the forge

Public code on Hephaestus. Click through to read, or sign in with your wallet to push your own.

+ Sign in with wallet + Explore all → + About Hephaestus +

+ +

Public repositories

Fetched live from Hephaestus. Sign in to see private orgs you belong to.

+ +

Loading from code.silentmode.st…

+ +

+ Clone URL patterns: + git clone https://code.silentmode.st/<owner>/<repo>.git (HTTPS with a personal token) + · + git clone ssh://git@code.silentmode.st:2222/<owner>/<repo>.git (SSH with your registered key) +

+ +

+ + + + + + diff --git a/hephaestus.x/forgejo/index.html b/hephaestus.x/forgejo/index.html new file mode 100644 index 0000000..72d21bf --- /dev/null +++ b/hephaestus.x/forgejo/index.html @@ -0,0 +1,142 @@ + + + + + +Hephaestus — the forge + + + + + + +

+ +

⚒️

the forge

Public code on Hephaestus. Click through to read, or sign in with your wallet to push your own.

+ Sign in with wallet + Explore all → + About Hephaestus +

+ +

Public repositories

Fetched live from Hephaestus. Sign in to see private orgs you belong to.

+ +

Loading from code.silentmode.st…

+ +

+ + + + + + diff --git a/hephaestus.x/index.html b/hephaestus.x/index.html new file mode 100644 index 0000000..2bf2df5 --- /dev/null +++ b/hephaestus.x/index.html @@ -0,0 +1,451 @@ + + + + + +Hephaestus.X — the forge on Bitcoin Cash + + + + + + + + + + + + + + + + + + + + + +

+ +

⚒️

The forge on Bitcoin Cash.

Hephaestus is the code host for the BCH ecosystem — Cauldron contributors, Sirius developers, wallet + authors, indexer maintainers. Sign in with a wallet, push a repo, host a release. No email, no password reset, + no middleman.

+ +

🔑 Sign in with wallet ▾

+ +

+ Browse repos → + See the source +

+ +

How it works

Three moving parts, no magic. Forgejo does the git and issue tracking, an auth-proxy translates + Bitcoin Cash message signatures into OpenID Connect tokens Forgejo understands, and Caddy fronts the whole + thing behind the two hostnames — hephaestus.x for BCNR-aware browsers, code.silentmode.st + as a public DNS mirror.

🔑 Wallet is the account

Generate or import a BCH wallet in the browser. Sign one BIP-137 "Bitcoin Signed Message" challenge, + and Forgejo auto-provisions bch_<first-20-of-your-cashaddr>. Rename it later — even to a + plain name like BitcoinCash. The private key never leaves your device.

💾 Cold blobs on Sia

Live git repos + Postgres stay on the VPS SSD for speed. LFS objects, release archives, container images, + package registry blobs and issue attachments spill to the Sia + network via s3.silentmode.st:8600. Encrypted client-side, sharded across independent hosts.

🌐 Two hostnames, one instance

hephaestus.x is the primary — an on-chain BCNR certificate, chipnet, owner-controlled, TLS via the + Silent Mode CA. code.silentmode.st is the public-DNS mirror for browsers without a BCNR resolver. + Same Forgejo, same accounts, same repos.

🧭 Standard git, nothing weird

git clone, git push, PRs, issues, releases, container/npm registries, the + Forgejo API. Bring your existing muscle memory — the only unusual bit is that you signed in with a wallet + instead of an email.

+ +

Sign in in three steps

Nothing to install, nothing to remember except your recovery phrase.

Pick your route. Sign up (create a new wallet in the browser), Sign in (import a 12/24-word + phrase you already have), or WizardConnect (sign with an external wallet — Cashonize, Paytaca — over an + encrypted relay).
Set a browser passphrase. Used to encrypt the wallet in your browser's localStorage. + Minimum 8 characters. Never leaves your device.
Sign the challenge. Your browser signs a one-time message, the auth-proxy verifies the signature + against your Bitcoin Cash address, and Forgejo hands you a session cookie. You land in the dashboard.

Start now ▾

+ +

See the source. Verify the deploy.

The whole forge — the Docker Compose stack, the Caddyfile, the auth-proxy that verifies wallet + signatures, the Forgejo Dockerfile with our CA baked in, every helper script — is on Hephaestus itself. + Clone it, read it, run it.

+ +

📖 silentmode/hephaestus

The full stack. docker-compose.yml, caddy/Caddyfile, + auth-proxy/ (Fastify OIDC provider), forgejo/Dockerfile, + scripts/, PROTOCOL.md.

Open repo →

🔐 auth-proxy

The wallet-to-OIDC bridge. ~250 lines of TypeScript that produces an Ed25519-signed id_token + after verifying a BIP-137 signature against a claimed CashAddr. The whole crypto path is in + src/verify.ts.

Read →

📜 PROTOCOL.md

Wallet-auth flow, message format, replay-protection, prefix handling (bitcoincash / bchtest / bchreg). + The document a third-party wallet needs to add native support.

Read →

+ +

Run your own

Nothing here needs Hephaestus.X's operator — the same compose stack runs on any Linux box with + Docker. Bring your own domain, a TLS cert, and a Sia bucket (the sia.storage free tier is enough for a small + forge). Then docker compose up.

# 1. clone
+git clone https://code.silentmode.st/silentmode/hephaestus.git
+cd hephaestus
+
+# 2. configure — copy .env.example, fill in your domain, Sia S3 creds, and OIDC secret
+cp .env.example .env
+$EDITOR .env
+
+# 3. run — Caddy + Postgres + Forgejo + auth-proxy come up together
+docker compose up -d
+
+# 4. first wallet signs in and takes the admin seat
+open https://your-domain.example/user/oauth2/hephaestus-wallet

+ +

Open source, MIT. Every commit is signed, every dependency is pinned. If you find + something you want to fix or improve, open a PR — or just fork it and run your own instance. That is the + point.

+ +

Public gaze — analytics, dashboards, transparency. Redirects to silentmode.st/helios/.

Open →

✉️ Hermes.X

Messenger. Nostr-based messaging bound to a BCNR name via the np + nr records.

Open →

+ +

Verify this page against the chain

You do not have to trust that hephaestus.x is served by anyone specific. The name's + certificate is on the Bitcoin Cash chain; the records point to a specific IP and a specific Sia bucket; every + path is independently checkable.

+ +

1. Reach this site via more than one route

The same content should be served from at least two independent paths. If one mirror disappears, + the others still work. If two disagree, the on-chain record is the tiebreaker.

Via any BCNR resolver: https://hephaestus.x/ (requires the local root CA)
Via the public gateway: https://navigate.st/bns/hephaestus.x
Via silentmode.st mirror: https://silentmode.st/hephaestus/
Public DNS mirror of the forge itself: https://code.silentmode.st/

+ +

2. Where it lives

forge: hephaestus.x (primary) · code.silentmode.st (public-DNS mirror) — same Forgejo 10 instance, dual-hostname
this name: hephaestus.x — on-chain BCNR certificate, chipnet, owner-controlled, TLS via the Silent Mode CA
storage: Sia network via s3.silentmode.st:8600, client-side encrypted · static landing mirrored to a Sia bucket as DR backup
source: silentmode/hephaestus — docker-compose, auth-proxy, Caddyfile, the whole stack
protocol: BIP-137 "Bitcoin Signed Message" over BCH secp256k1 — any wallet that speaks Sign Message can log in

+ +

+ + + + + + + diff --git a/hephaestus.x/js/theme.js b/hephaestus.x/js/theme.js new file mode 100644 index 0000000..96d90d1 --- /dev/null +++ b/hephaestus.x/js/theme.js @@ -0,0 +1,63 @@ +// Sirius.X font picker — reader chooses between Fraunces (Silent Mode +// family — editorial serif, default) and Ubuntu (Bitcoin Cash brand +// font — humanist sans). Persisted in localStorage under 'sirius-font'. +// +// The runtime attribute goes on — pages that want to opt out +// simply omit the include. The actual font-swap CSS is defined per +// page (in each page's + + + + +

+ +

+ hephaestus.x / silentmode / __REPO__ +

+ +

silentmode/REPO

loading …

+ Browse full source → + Issues + Releases +

+ +

README

Loading README from the forge…

+ +

Recent commits

Loading…

+ +

Clone

HTTPS (with a personal access token)

git clone https://<you>:<token>@code.silentmode.st/silentmode/__REPO__.git

SSH (with a key registered under your account)

git clone ssh://git@code.silentmode.st:2222/silentmode/__REPO__.git

+ +

+ + + + + + diff --git a/hephaestus.x/silentmode/ariadne/index.html b/hephaestus.x/silentmode/ariadne/index.html new file mode 100644 index 0000000..814cad0 --- /dev/null +++ b/hephaestus.x/silentmode/ariadne/index.html @@ -0,0 +1,228 @@ + + + + + +silentmode/ariadne — Hephaestus + + + + + + +

+ +

+ hephaestus.x / silentmode / ariadne +

+ +

silentmode/ariadne

loading …

+ Browse full source → + Issues + Releases +

+ +

README

Loading README from the forge…

+ +

Recent commits

Loading…

+ +

Clone

HTTPS (with a personal access token)

git clone https://<you>:<token>@code.silentmode.st/silentmode/ariadne.git

SSH (with a key registered under your account)

git clone ssh://git@code.silentmode.st:2222/silentmode/ariadne.git

+ +

+ + + + + + diff --git a/hephaestus.x/silentmode/hephaestus/index.html b/hephaestus.x/silentmode/hephaestus/index.html new file mode 100644 index 0000000..a49fc7c --- /dev/null +++ b/hephaestus.x/silentmode/hephaestus/index.html @@ -0,0 +1,228 @@ + + + + + +silentmode/hephaestus — Hephaestus + + + + + + +

+ +

+ hephaestus.x / silentmode / hephaestus +

+ +

silentmode/hephaestus

loading …

+ Browse full source → + Issues + Releases +

+ +

README

Loading README from the forge…

+ +

Recent commits

Loading…

+ +

Clone

HTTPS (with a personal access token)

git clone https://<you>:<token>@code.silentmode.st/silentmode/hephaestus.git

SSH (with a key registered under your account)

git clone ssh://git@code.silentmode.st:2222/silentmode/hephaestus.git

+ +

+ + + + + + diff --git a/hephaestus.x/silentmode/index.html b/hephaestus.x/silentmode/index.html new file mode 100644 index 0000000..9aabcc0 --- /dev/null +++ b/hephaestus.x/silentmode/index.html @@ -0,0 +1,128 @@ + + + + + +silentmode/* — Hephaestus + + + + + + +

+ +

+ hephaestus.x / silentmode +

+ +

🛠

silentmode/*

Public repositories under the silentmode org. Click through for a per-repo overview or straight into the full forge.

+ +

Loading from the forge…

+ +

+ + + + + + diff --git a/hephaestus.x/silentmode/sirius/index.html b/hephaestus.x/silentmode/sirius/index.html new file mode 100644 index 0000000..a7ee518 --- /dev/null +++ b/hephaestus.x/silentmode/sirius/index.html @@ -0,0 +1,228 @@ + + + + + +silentmode/sirius — Hephaestus + + + + + + +

+ +

+ hephaestus.x / silentmode / sirius +

+ +

silentmode/sirius

loading …

+ Browse full source → + Issues + Releases +

+ +

README

Loading README from the forge…

+ +

Recent commits

Loading…

+ +

Clone

HTTPS (with a personal access token)

git clone https://<you>:<token>@code.silentmode.st/silentmode/sirius.git

SSH (with a key registered under your account)

git clone ssh://git@code.silentmode.st:2222/silentmode/sirius.git

+ +

+ + + + + + diff --git a/hephaestus.x/silentmode/theseus/index.html b/hephaestus.x/silentmode/theseus/index.html new file mode 100644 index 0000000..19b8a75 --- /dev/null +++ b/hephaestus.x/silentmode/theseus/index.html @@ -0,0 +1,228 @@ + + + + + +silentmode/theseus — Hephaestus + + + + + + +

+ +

+ hephaestus.x / silentmode / theseus +

+ +

silentmode/theseus

loading …

+ Browse full source → + Issues + Releases +

+ +

README

Loading README from the forge…

+ +

Recent commits

Loading…

+ +

Clone

HTTPS (with a personal access token)

git clone https://<you>:<token>@code.silentmode.st/silentmode/theseus.git

SSH (with a key registered under your account)

git clone ssh://git@code.silentmode.st:2222/silentmode/theseus.git

+ +

+ + + + + + diff --git a/hephaestus/index.html b/hephaestus/index.html new file mode 100644 index 0000000..c3a5d3d --- /dev/null +++ b/hephaestus/index.html @@ -0,0 +1,343 @@ + + + + + +Hephaestus — decentralized code forge for Silent Mode + + + + + + + + + + + + + + + + + +

It only 404s if you drop the /auth/ prefix. Caddy path-multiplexes: /auth/* goes to the auth-proxy, everything else goes to Forgejo. Forgejo has no /static/wallet.js, so that path is expected-404. The real paths are:

+ + + + + + + + + + + + +

URL	Served by	Purpose
/auth/authorize	auth-proxy	Login shell HTML (SPA bootstrap)
/auth/static/wallet.js	auth-proxy	Wallet UI + signing logic (~10 KB)
/auth/static/login.css	auth-proxy	Styles for the login card
/auth/challenge	auth-proxy	POST cashaddr → get nonce + signed message
/auth/verify	auth-proxy	POST nonce + signature → get OAuth code
/auth/.well-known/openid-configuration	auth-proxy	OIDC discovery
/user/oauth2/hephaestus-wallet	Forgejo	Kicks off the OAuth handshake (307 → /auth/authorize)
/user/oauth2/hephaestus-wallet/callback	Forgejo	Receives the OAuth code, mints session
/api/v1/version	Forgejo	Public: returns Forgejo version
/api/v1/user	Forgejo	Requires an API token (not a session cookie) — returning 401 in a browser is not a bug

+ +

Testing the sign-in flow end-to-end without a real browser

The wallet signing is easiest to reproduce in Node/Deno or a headless browser — the crypto is BIP-137 "Bitcoin Signed Message" over BCH secp256k1. But the server-side pieces alone can be smoke-tested with curl:

ISSUER=https://code.silentmode.st/auth
+
+# 1. discovery document lists all endpoints
+curl -s "$ISSUER/.well-known/openid-configuration" | jq .
+
+# 2. request a challenge for any cashaddr (server just holds it 5 min)
+curl -s -X POST -H 'content-type: application/json' \
+  -d '{"cashaddr":"bitcoincash:qq00000000000000000000000000000000000000q"}' \
+  "$ISSUER/challenge"
+# → returns {"nonce": "...", "message": "code.silentmode.st wants you to sign in..."}
+
+# 3. any BCH wallet that speaks "Sign Message" can produce a valid signature
+#    for that exact message. Then POST it:
+curl -s -X POST -H 'content-type: application/json' \
+  -d '{"nonce":"THE_NONCE","signature":"BASE64_SIG"}' \
+  "$ISSUER/verify"
+# → returns {"redirect": "https://code.silentmode.st/user/oauth2/hephaestus-wallet/callback?code=..."}

For the JS side (which is what the browser does), inspect auth-proxy/public/wallet.js in the repo — it's ~250 lines and does exactly this: generateBip39Mnemonic → deriveHdPath("m/44'/145'/0'/0/0") → sign(magicHash(message)). Nothing exotic.

+ +

Common browser-side checks

If your CLI drives a real browser (Playwright, Puppeteer, curl-with-cookies) and you want to know if you're actually signed in:

// The URL bar isn't reliable when Forgejo shows Security or Settings pages —
+// they render for logged-in users but don't have "Dashboard" in the title.
+// Best check: does the profile menu render, and is there no "Sign in" link?
+
+const signedIn = !document.querySelector('a[href*="/user/login"]')
+              && !!document.querySelector('[aria-label*="Profile"], .user-menu, .avatar');
+
+// The username, if you're on the Dashboard:
+document.title.match(/^(bch_\w+)/)?.[1];

+ +

Do not test with fetch('/api/v1/user') unless you have an API token. That endpoint requires token auth even when you're signed into the web UI. Session cookies get you into Forgejo pages; they don't get you into the token-scoped API. A 401 there means "no token" — it does not mean "not signed in."

+ +

Push some code

Two paths, either works. Pick whichever fits your setup.

+ +

Over HTTPS (with an access token)

git clone https://your_bch_username:YOUR_TOKEN@code.silentmode.st/your_bch_username/your-repo.git
+cd your-repo
+echo "Hello, forge" > README.md
+git add README.md && git commit -m "hello"
+git push

+ +

Over SSH (with your existing key)

Add your public key to Settings → SSH / GPG Keys → Add Key. Then use port 2222:

git clone ssh://git@code.silentmode.st:2222/your_bch_username/your-repo.git

Your key is only trusted for git-over-SSH; there's no shell access.

+ +

How it fits together

            you (browser)
+                │
+       https://code.silentmode.st/
+                │
+     ┌──────────┴──────────┐
+     │        Caddy        │  ← Let's Encrypt cert, HTTP/3
+     │   (path-based mux)  │
+     └──┬───────────────┬──┘
+        │               │
+        │/auth/*        │/
+        ▼               ▼
+   auth-proxy       Forgejo ── Postgres      (live git repos + DB
+   (OIDC provider) ───┬───                    on local VPS SSD)
+   Node/Fastify       │
+   libauth for        │ storage backend
+   BCH signature      ▼
+   verification    s3.silentmode.st:8600  ← s3d gateway
+                       │
+                       ▼
+                  Sia network hosts
+                  (LFS, attachments,
+                   packages, archives)

+ + + + + + + + + +

Component	Role
Forgejo 10	Web UI, PRs, issues, releases, container/npm registry, git-over-HTTPS + SSH
Postgres 16	User records, issues, PRs, permissions, session state
Caddy 2	Reverse proxy + automatic Let's Encrypt TLS + HTTP/3
auth-proxy	OIDC provider (Node/Fastify + libauth). Issues signed challenges, verifies BCH signatures, mints OAuth codes.
s3d → Sia	Cold storage. Files are encrypted client-side, sharded via Reed-Solomon, scattered across independent hosts.
restic	Nightly encrypted snapshots (Postgres + /data/git) to a separate Sia bucket. Systemd timer at 03:15 UTC.

+ +

Wallet-auth protocol

Any BCH wallet that speaks Bitcoin Signed Message can produce a signature Hephaestus will accept. There is no Hephaestus-specific signing format.

+ +

Message the wallet signs:
+─────────────────────────────
+code.silentmode.st wants you to sign in with your Bitcoin Cash account:
+bitcoincash:qzkc695pm4r3p7kcq36sh0t3fdu5e6ua7u2ar36vea
+
+By signing, you prove you control this address. This request will not
+trigger a blockchain transaction or cost any fees.
+
+Domain: code.silentmode.st
+Nonce: e65d80b51d3f1baa2efb8d952d827104
+Issued At: 2026-08-29T17:50:12.655Z

+ +

Signature is standard BIP-137-style recoverable ECDSA over the SHA256(SHA256(varint(magic) || magic || varint(msg) || msg)) digest, base64-encoded. The server recovers the pubkey, derives the cashaddr, and matches it against the address you claimed. Nonces expire after 5 minutes and are single-use.

+ +

OIDC id_token claims: sub = full cashaddr, preferred_username = "bch_" + first-20-of-address, plus a custom cashaddr claim carrying the full address for downstream tools. Signed with EdDSA (Ed25519).

+ +

For operators self-host your own

Hephaestus is a docker-compose stack. Everything you need is in the silentmode monorepo under Hephaestus/. To stand up your own instance:

+ +

Get a Linux VPS with Docker (2 GB RAM, ~10 GB free disk minimum). A domain name pointing at it. Ports 80/443/2222 open.

Clone the repo, copy the env template +

git clone ssh://git@code.silentmode.st:2222/silentmode/silentmode.git
+cd silentmode/Hephaestus
+cp .env.example .env
+# fill in real values — see .env.example for what each field means

Bring it up +
```
docker compose up -d
```
+ First run pulls ~500 MB of images and builds the auth-proxy. Give it a few minutes.
Complete Forgejo install via POST to / with your admin creds (see PROTOCOL.md in the repo for the exact field list — Forgejo's --config path prevents the CLI installer working, so it has to be the HTTP path).

Register the wallet OIDC provider +

docker compose exec forgejo forgejo \
+    --config /data/gitea/conf/app.ini admin auth add-oauth \
+    --provider openidConnect \
+    --name hephaestus-wallet \
+    --key "$AUTH_PROXY_CLIENT_ID" --secret "$AUTH_PROXY_CLIENT_SECRET" \
+    --auto-discover-url "$AUTH_PROXY_ISSUER/.well-known/openid-configuration" \
+    --scopes "openid profile"

+ +

Gotchas we hit — save yourself the same debugging

Forgejo's docker entrypoint re-writes app.ini from env vars on every start — sed edits inside the container get clobbered. Everything must come from FORGEJO__section__KEY env vars in docker-compose.yml.
DISABLE_REGISTRATION=true blocks OIDC auto-provisioning too, not just the local form. Use DISABLE_REGISTRATION=false + ALLOW_ONLY_EXTERNAL_REGISTRATION=true + SHOW_REGISTRATION_BUTTON=false.
Forgejo needs [oauth2_client] ENABLE_AUTO_REGISTRATION=true AND USERNAME=preferred_username AND an email claim on the id_token (auth-proxy synthesizes one).
Forgejo usernames are [a-zA-Z0-9-_.]+, max 40 chars. Raw cashaddrs (54 chars, colon) don't fit — auth-proxy sends bch_<first-20> as the username while keeping the full cashaddr in sub.
When serving auth-proxy under a /auth/* path prefix behind a reverse proxy, all client-side asset paths and fetch URLs must be path-relative (no leading slash), otherwise the browser resolves them to origin root and hits the wrong service.

+ +

Status

+ + + + + + + + + +

Live at	code.silentmode.st
Signup	Open (wallet-only; local registration disabled)
Storage	Sia network for cold blobs, VPS SSD for hot path
Backups	Nightly restic → separate Sia bucket, encrypted client-side
Source	silentmode/silentmode (private — request access from an admin), or the local checkout under `Hephaestus/`
License	Forgejo is GPL-3.0. Auth-proxy + Caddyfile + docker-compose scaffolding is part of the Silent Mode monorepo.
Chain	Chipnet (Bitcoin Cash test network) alpha
BCNR name	`hephaestus.x` — minted on chipnet, points at `https://code.silentmode.st/`. Resolve via navigate.st gateway or any BCNR-aware browser (Theseus, Ariadne).

+ +

Report an issue. Open one at silentmode/silentmode/issues once you have access, or ping in the usual Silent Mode channels.

+ +

+ + + + + diff --git a/hermes/index.html b/hermes/index.html new file mode 100644 index 0000000..923821e --- /dev/null +++ b/hermes/index.html @@ -0,0 +1,162 @@ + + + + + +Hermes — messaging by name — Silent Mode + + + + + + + + + + + + + + + + + +

⛓️✉️

Hermes designed · not yet built

End-to-end encrypted DMs over Nostr, addressed by your + .bch name instead of a public-key string. Same wallet + is your identity — no email, no phone number, no company, no server that can delete + your account.

+ +

The one idea that makes this different

Every existing Nostr client has the same wart: identity is + npub1q8s7f3k… gibberish. The human-name fix — NIP-05 — + resolves alice@example.com through a DNS domain and a + web server. That is exactly the ICANN + server chain Silent Mode exists to escape. + Decentralized messaging bolted onto centralized identity.

+ +

The Hermes pitch.
+ alice.bch publishes her Nostr pubkey as an on-chain + record. Her name certificate is her verified, seizure-resistant identity. + Message anyone by their .bch name — no phone number, no + email, no ICANN, no company, no server that can delete your account.

+ +

How it works

Your name owns your key. + Register any name you like on the chain (or reuse one you already own), + publish your Nostr pubkey to it as a new np record. + The key is derived from the same wallet seed as the name itself, so one seed + backs both.
Find people by name. + Type bob.bch. The client resolves it against + the chain, pulls np (Nostr pubkey) and + nr (preferred relays). No directory server involved.
Send the message sealed. + NIP-17 gift-wrapped DMs — the relay sees neither sender nor content, only + that a wrap addressed to some pubkey exists. Route over Tor to also hide your + IP; Theseus already can.
The name shows, not the pubkey. + Incoming messages reverse-resolve pubkey → name where possible, so your + chat list looks like a normal chat list — not a wall of hex.

+ +

Where it will live

In Theseus desktop

A Messages panel inside the browser you already have. Routes relay traffic over + Tor. Reuses the built-in wallet's seed as the messaging identity.

In Ariadne mobile phone

A Messages screen in the existing Android app. Same seed, same identity — you + can message from either device without a linked-account handshake.

+ +

Where your history lives

Three modes, one toggle. The default assumes no cloud at all — every + later option is opt-in, and none of them let anyone but you read your messages.

Local only default

The client keeps your message history on the device. Nothing else knows it + exists. Same seed on Theseus and Ariadne gives you two-device redundancy for + free — lose one, restore from the other. Lose both, history is gone. Signal's + model, on purpose.

Silent Mode cloud backup opt-in

Toggle on and the client encrypts your message history with a key derived + from your wallet seed, then backs it up to decentralized cloud storage on + the Sia network. Only you can read it. Text messages only — no + pictures, no video, no attachments.

Your own Sia account advanced

Prefer to own the storage yourself? Hermes sets up your own Sia account + and routes your backups there instead. Same encryption from your wallet + seed — and this time media backup is on the table too.

+ +

Honest boundaries

Messaging, not email

No Gmail interop — by design. A separate anonymous-mailbox product covers + "sign up on services without leaking a real address."

Metadata resistance is good, not perfect

NIP-17 hides sender and content from relays. Relays still see the recipient + pubkey, timing, and your connection IP unless you route over Tor. The UI will + tell you when it's on.

Relays are Nostr's soft spot

A message lives only while some relay keeps it. Silent Mode runs one relay on + the same anonymous VPS as the gateway, and writes to a few public relays for + reach and redundancy.

+ +

Status: designed, not built. The full protocol design is + in Hermes/DESIGN-hermes.md + (mirror). Nothing to install yet — this page exists to say what is coming, and to + make it possible to ask for updates in the messaging panel of a future Theseus or + Ariadne build.

+ +

+ + + + + diff --git a/home-cards.json b/home-cards.json new file mode 100644 index 0000000..b280b5e --- /dev/null +++ b/home-cards.json @@ -0,0 +1,11 @@ +[ + { "title": "hello.bch", "url": "https://hello.bch/", "sub": "A small page on the blockchain itself.", "badge": "on-chain" }, + { "title": "siatest.bch", "url": "https://siatest.bch/", "sub": "A page with no server, backed by Sia.", "badge": "Sia" }, + { "title": "SilentMode.X", "url": "https://silentmode.x/", "sub": "Infrastructure development for a decentralized web.", "badge": "Infrastructure" }, + { "title": "Theseus.X", "url": "https://theseus.x/", "sub": "The Web Navigator — this browser's own address.", "badge": "Navigator" }, + { "title": "Sirius.X", "url": "https://sirius.x/", "sub": "Register and manage BCDN names.", "badge": "Registrar" }, + { "title": "Hephaestus.X", "url": "https://hephaestus.x/", "sub": "The forge — Silent Mode's code host.", "badge": "Code host" }, + { "title": "Prometheus.X", "url": "https://prometheus.x/", "sub": "Decentralized App Marketplace.", "badge": "App store" }, + { "title": "Helios.X", "url": "https://helios.x/", "sub": "Search engine for the decentralized web (in design).", "badge": "Search" }, + { "title": "Hermes.X", "url": "https://hermes.x/", "sub": "Messaging — end-to-end encrypted over Nostr.", "badge": "Messaging" } +] diff --git a/index.html b/index.html new file mode 100644 index 0000000..e9afc09 --- /dev/null +++ b/index.html @@ -0,0 +1,170 @@ + + + + + +Silent Mode — decentralized web infrastructure + + + + + + + + + + + + + + + + + +

Silent Mode

A development department for the decentralized web. We build names, + hosting, apps, search, messaging, and the clients that reach them — everything you + need to run a site nobody can seize, and everything you need to visit one.

+ Download the browser + See all tools + See our .bch demo +

+ New to any of this? Start with the choice → +

+ +

Theseus Navigator showing https://hello.bch with the BCDN badge in the address bar — the page loaded with no DNS lookup and no registrar. — Theseus opening `hello.bch`: the name was read from the Bitcoin Cash chain, the page from the network — no DNS was asked, no registrar consulted.

+ +

+ + +

+ This page is ordinary web infrastructure. silentmode.st + runs on nginx, a rented server, an ICANN domain, and a Let's Encrypt certificate — because + the point of this page is to talk about the alternative web, and the widest + audience needs no install to read it. +

+ The project's own demonstration lives at silentmode.bch + — same project, hosted with the tools it describes. No centralized host, no registrar + entity, no DNS, no certificate authority. + + Any resolver installed? Try it natively: https://silentmode.bch/ + +

+ + +

What we build

Seven pieces, each named for a figure whose role matches its function. + Each solves one part of the "how do we run a web without gatekeepers" problem, and + all of them interoperate around one thing: a name on the Bitcoin Cash chain.

+ +

+ alpha +

Theseus browsers & resolvers

Two flagship browsers, one brand across platforms — Ariadne resolver built in. + Also: the public relay (no install), the Firefox extension, and a standalone + Ariadne Resolver for system-wide BNS in every browser.

See all tools →

+ +

+ live +

The incentive layer nobody pays for today. Independent hosts pooling to keep + your site up, paid by a covenant on chain. The piece that turns "you can host + it" into "someone will keep hosting it."

+ +

+ + +

One thread through all of them

Everything above depends on one thing: a name registered on the + Bitcoin Cash chain, held in a wallet you control. That name is your address on + Prometheus, your identity on Hermes, your ranking signal on Helios, and the URL + Tools resolve. Register once; use it everywhere. Nobody issues it, nobody revokes + it, and no service you use here needs an account.

+ Register a name at Sirius → +

+ +

A listing is a signed on-chain record. + Publishing an app writes a small APS1 record + to Bitcoin Cash — same protocol shape as a BNS name registration, different + prefix. The payload is a hash pointing at a full manifest stored on Sia: + name, description, category, icon, version, download URL, binary SHA-256, and + signing-cert fingerprint. Nobody approves the record; the transaction is the + publish.
The binary lives on Sia. + App files are uploaded to the Sia storage network — encrypted on the + publisher's machine, sharded across roughly 30 independent hosts, held by + nobody in particular. The listing carries the SHA-256 the file must match. If + the mirror serves a byte off, the client refuses to install it.
Reviews are signed endorsements you filter. + An endorsement is a signed statement on chain: "I, alice.bch, + vouch for this app." Your client shows the endorsements from names on trust + lists you subscribe to — a security researcher's, a friend's, your own. A + one-star review from a bot you don't follow simply doesn't render. Curated + registries and formal reputation come later; permissionless comes first.
Install verifies against the chain. + The Ariadne clients pull the file from wherever the listing says (Sia, + mirror, your own server), check the SHA-256 against the on-chain record, check + the signing certificate against the fingerprint, and only then install. Same + principle as verifying a website — the chain is the truth, not the mirror.

+ + +

Publishing an app

+ available today +

Register a name

Every publisher needs a name to sign as. Any BNS name works — the same one you'd + register at Sirius. Fractions of a cent, no monthly bill.

+ available today +

Host on Sia

Upload the app binary + manifest to a Sia bucket you control. Silent Mode's own + gateway can host on your behalf if you don't want to run a Sia daemon.

+ designed +

Publish the listing

One transaction: APS1 record with the manifest hash, + signed by your name's key. From that moment on, anyone can find your app by + browsing the category, and the client can install it verifiably.

+ designed +

Ship updates

An update is another signed record referencing the same app id. Clients pull + updates the same way they installed the app — verify against the chain, then + install. Nobody can push a hostile update without your key.

+ + +

Honest boundaries

Not a curator

Prometheus does not decide what is on it. Malware can be published — as it can + on any store. Trust lists and endorsements are what filter your view. If nobody + you trust endorses it, your client says so.

Not a moderator

Content that is illegal in your jurisdiction is your responsibility to avoid, + same as any other permissionless network. Silent Mode operates infrastructure; + it does not decide what runs on it.

Storage costs money

Sia hosting is inexpensive but not free — publishers pay for the bytes their + apps take. There is no advertising model, no data harvesting, no subscription. + Storage is the only cost, and it is small.

+ +

Status: designed, not yet built. The listing protocol + (APS1) exists on paper — see + _coordination/sessions/mobile-resolver.md. The browsing UI, + publish flow, and trust-list plumbing are next. This page will look the same when + Prometheus is live; the "0 listings" counters just start counting up.

+ +

+ + + + + diff --git a/register.html b/register.html new file mode 100644 index 0000000..ba5e372 --- /dev/null +++ b/register.html @@ -0,0 +1,30 @@ + + + + + +Moved — Silent Mode + + + + + + + +

Registration moved.

Silent Mode's naming registry is now at Sirius. The registration flow + you were looking for lives at silentmode.st/sirius/register.html. + Redirecting you there.

+ + diff --git a/releases-manifest.json b/releases-manifest.json new file mode 100644 index 0000000..a829dc8 --- /dev/null +++ b/releases-manifest.json @@ -0,0 +1,51 @@ +{ + "schema": "silentmode-releases/2", + "updated": "2026-09-10", + "mirrors": [ + "https://dl.silentmode.st/" + ], + "releases": [ + { + "id": "ariadne-resolver", + "product": "Ariadne Resolver (Windows)", + "version": "0.1.2", + "date": "2026-09-09", + "platform": "win-x64", + "signed": false, + "signingAuthority": null, + "changes": "install.ps1 no longer dies at the CA-rotation probe on PS 5.1 (native subprocess stderr no longer trips $ErrorActionPreference=Stop; node calls go through Invoke-NodeCapture using OS-level stream redirection). Multi-source TLD cascade: comma-separated indexer list (default navigate.st,silentmode.st) then C:\\ProgramData\\Ariadne\\tlds-cache.json then electrum WSS then bundled ariadne.config.json then bootstrap; authoritative fetches refresh the cache automatically. CA import switched to X509Store direct so Cert: PSDrive doesn't have to be loaded. Inno now stops the running daemon before file replacement so upgrades no longer roll back with \"DeleteFile access denied\" on node.exe.", + "files": { + "AriadneResolver-Setup-0.1.2.exe": "5a2c9e4f3c5e1a162008641019f5ffc35968751c0440f94d3c5fe67aafb8cc5e" + } + }, + { + "id": "ariadne-android", + "product": "Ariadne for Android", + "version": "0.14", + "date": "2026-09-09", + "platform": "android", + "minSdk": 21, + "signed": true, + "signingAuthority": null, + "signingCertSha256": "46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c", + "changes": "Feature batch — makes the app feel like a real browser. Bookmarks: ⭐ button in the address row toggles the current URL; long-press opens the list; a Your-bookmarks section appears above Featured on the start page. Undo close tab: a floating pill offers UNDO for 5s after a closeTab. Long-press a link: Open in new tab / Copy link / Share link. Downloads: WebView.setDownloadListener wired to Android's system DownloadManager so PDFs, APKs, and media save via the platform notification. Pull-to-refresh: hand-rolled overscroll gesture (no AndroidX) with a gold pull-to-reload / release-to-reload chip. Share-target intent: Ariadne now appears in the system Share sheet and registers as a browser for http/https so links from other apps open here. Address bar polish: strips https:// and trailing / when unfocused (Chrome/Safari convention), long-press copies the full URL, a clear-× shows while typing. Splash screen: cold start paints the Ariadne mark on navy instead of the black flash.", + "files": { + "ariadne-v0.14.apk": "0deace437ccde7709cd21486c9b7b37b2a57463cead79b75672d974d3e5b11b0" + } + }, + { + "id": "theseus-navigator", + "product": "Theseus Navigator", + "version": "0.3.45", + "date": "2026-09-10", + "platform": "win-x64", + "signed": false, + "signingAuthority": null, + "changes": "Startup no longer waits on the bookmark-bar favicons: the toolbar paints at DOM-ready, overlays and restored tabs load after it (active tab first, the rest staggered), and the pre-paint frame is dark instead of a white strip. Ariadne’s Thread button replaces the BCDN/ICANN chips at the end of the address bar — one icon that never overflows the bar, with a native menu to switch registry, remember the choice per name or per TLD, set the collision policy, and open the resolver settings. Page zoom: Ctrl +/−/0 and Ctrl+wheel on Chrome’s ladder, per host like Chrome, with a percentage chip in the address bar. The link-status pill now shows full-length URLs; the address/search bar ratio can run 80/20 to 20/80; the collapsed extension dock renders icon images instead of a data URI as text. Ariadne’s Thread plug-in card: the on/off toggle now actually reaches the scheduled tasks (every previous build silently did nothing), off persists across reboots, the update check reads dl.silentmode.st’s manifest, and installer exit codes are reported. Bundles Screenshot 0.6.4 and Aegis 0.6.2.", + "files": { + "TheseusNavigator-0.3.45-portable.exe": "5eb7b155cbd4a75322b25e6f4ff0bb5d66d069439c2c76da93488a70719f3dc6", + "TheseusNavigator-Setup-0.3.45.exe": "f0a11250a116027881ec391676a722dd320e789ffe7ae8016d27a0cdb97dbd78" + } + } + ] +} diff --git a/releases/index.html b/releases/index.html new file mode 100644 index 0000000..5c0e3af --- /dev/null +++ b/releases/index.html @@ -0,0 +1,108 @@ + + + + + + + + + + + + + +Silent Mode — releases & checksums + + + + + + + + +

Silent Mode — releases

Canonical SHA-256 checksums for every published build. This page lives at the on-chain + name releases.silentmode.bch; the name pins where it is served from, so a tampered + mirror cannot change what you check against here.

+ +

Theseus Navigator 0.3.45

Windows 64-bit · unsigned · 2026-09-10 · 0.3.45 — faster startup, Ariadne’s Thread menu, page zoom, resolver toggle fix — Startup no longer waits on the bookmark-bar favicons: the toolbar paints at DOM-ready, overlays and restored tabs load after it (active tab first, the rest staggered), and the pre-paint frame is dark instead of a white strip. Ariadne’s Thread button replaces the BCDN/ICANN chips at the end of the address bar — one icon that never overflows the bar, with a native menu to switch registry, remember the choice per name or per TLD, set the collision policy, and open the resolver settings. Page zoom: Ctrl +/−/0 and Ctrl+wheel on Chrome’s ladder, per host like Chrome, with a percentage chip in the address bar. The link-status pill now shows full-length URLs; the address/search bar ratio can run 80/20 to 20/80; the collapsed extension dock renders icon images instead of a data URI as text. Ariadne’s Thread plug-in card: the on/off toggle now actually reaches the scheduled tasks (every previous build silently did nothing), off persists across reboots, the update check reads dl.silentmode.st’s manifest, and installer exit codes are reported. Bundles Screenshot 0.6.4 and Aegis 0.6.2.

+ +

TheseusNavigator-Setup-0.3.45.exe — installer

+ f0a11250a116027881ec391676a722dd320e789ffe7ae8016d27a0cdb97dbd78 +

TheseusNavigator-0.3.45-portable.exe — portable

+ 5eb7b155cbd4a75322b25e6f4ff0bb5d66d069439c2c76da93488a70719f3dc6 +

+ +

Ariadne Resolver — Windows 0.1.2

Windows 64-bit · unsigned · bundled Node runtime · 2026-09-09 · Actually works this time — 0.1.1's persistent install log caught the bug 0.1.0 had had silently all along: install.ps1 died at the CA-rotation probe because PowerShell 5.1's $ErrorActionPreference=Stop plus a native subprocess writing to stderr = "NativeCommandError", killing the script before it could register the daemon or add the last NRPT rule. 0.1.2 routes every node call through Invoke-NodeCapture (Windows-level stream redirection, PS 5.1 doesn't touch the streams). TLD list now cascades: comma-separated indexer list → local cache → electrum WSS → bundled snapshot → bootstrap, and any authoritative fetch refreshes C:\ProgramData\Ariadne\tlds-cache.json. CA import via .NET X509Store direct (no Cert: PSDrive dependency). Upgrades stop the running daemon before file replacement so node.exe is no longer held open during install.

+ +

AriadneResolver-Setup-0.1.2.exe — ~24 MB

+ 5a2c9e4f3c5e1a162008641019f5ffc35968751c0440f94d3c5fe67aafb8cc5e +

+ +

Ariadne for Android 0.11

Android 5.0+ (API 21) · self-signed release key · 2026-08-30 · adds Sia CDN pull to the APK-bundled starter — post-install cold starts now catch up from the operator's latest published snapshot in one HTTP call

+ +

ariadne-v0.11.apk — 124 KB

+ 03c95832c16cc4763acaadbf328caa7d4bd05fc7c2994f6997a79cc6890bca44 +

Signing certificate — SHA-256 (the same key signs every future release)

+ 46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c +

+ +

How to verify. After downloading, compute the file's SHA-256 and compare it to + the value above — on Windows: certutil -hashfile <file> SHA256; + on Android, hash the downloaded .apk on a computer before you move + it to the phone, or use any file-hashing app. Nothing here is signed by an authority your device + already trusts — by design — so it will warn about an unrecognized app; the checksum is the + real check. The machine-readable manifest is at + releases-manifest.json.

+ + +

+ + diff --git a/shared.css b/shared.css new file mode 100644 index 0000000..55d04a1 --- /dev/null +++ b/shared.css @@ -0,0 +1,178 @@ +/* Silent Mode — shared design tokens and component styles. + Every page under silentmode.st links this file so a colour or a control style + only has to change once. Page-specific bits (search UI, download listing, + registration modal) stay in the page. */ + +:root{ + --bg:#0b0e14; + --panel:#141a24; + --panel2:#18202c; + --line:rgba(255,255,255,.09); + --ink:#e7eaf1; + --mut:#8b98a9; + --dim:#7a8496; /* was #5e6678 — 3.4:1, failed AA for fine print */ + --acid:#d6ff3d; + /* semantic accents used to colour-code content sources across pages */ + --chain:#d6ff3d; + --sia:#b39ddb; + --srv:#4fd1a5; + --tor:#a98bd8; + --ok:#4fd1a5; + --taken:#f6768a; + --warn:#ffc75f; +} + +*{box-sizing:border-box} +html{scroll-behavior:smooth} +body{ + margin:0; + background:radial-gradient(1100px 560px at 50% -12%,#16202e,var(--bg)); + color:var(--ink); + font:16px/1.65 system-ui,-apple-system,Segoe UI,Roboto,sans-serif; + min-height:100vh; +} +a{color:var(--acid)} + +/* ============ top nav ============ */ +/* Inlined by each page. Sticky so navigation stays reachable on long pages. + The `.here` class marks the current section. */ +.topnav{ + position:sticky;top:0;z-index:20; + display:flex;gap:2px;align-items:center;flex-wrap:wrap; + padding:10px 1.2rem; + background:rgba(11,14,20,.82); + backdrop-filter:blur(10px); + border-bottom:1px solid var(--line); +} +.topnav .brand{ + font-weight:600;color:var(--ink);text-decoration:none; + margin-right:14px;font-size:15px;letter-spacing:.2px; +} +.topnav .brand .g{color:var(--acid)} +.topnav a{ + color:var(--mut);text-decoration:none; + padding:9px 12px;border-radius:8px;font-size:14px; +} +.topnav a:hover{color:var(--ink);background:var(--panel)} +.topnav a.here{color:var(--acid);background:rgba(214,255,61,.08)} + +/* ============ layout ============ */ +.wrap{max-width:980px;margin:0 auto;padding:0 1.2rem} +.wrap.narrow{max-width:820px} + +header.hero{text-align:center;padding:4.5rem 1.2rem 2.4rem} +header.hero .mark{font-size:58px;line-height:1} +h1{font-size:clamp(2rem,5vw,3rem);margin:.5rem 0 .3rem;letter-spacing:.4px} +h1 .g{color:var(--acid)} +.tag{color:var(--mut);font-size:1.1rem;max-width:660px;margin:.4rem auto 0} + +section{padding:2.8rem 0;border-top:1px solid var(--line)} +section.plain{border-top:none} +h2{font-size:1.55rem;margin:0 0 .4rem} +h3{font-size:1.05rem;margin:0 0 .3rem} +.lede{color:var(--mut);margin:0 0 1.6rem;max-width:680px} + +.cta{display:flex;gap:10px;justify-content:center;flex-wrap:wrap;margin-top:1.7rem} + +/* ============ controls ============ */ +.btn{ + display:inline-block;text-decoration:none; + padding:11px 20px;border-radius:999px; + background:var(--panel2);color:var(--ink);font-size:14.5px; + border:1px solid var(--line);cursor:pointer;font-family:inherit; +} +.btn.ghost{background:transparent;border-color:var(--line);color:var(--ink)} +.btn.acid{background:var(--acid);color:#0b0e14;font-weight:600;border:none} +.btn:hover{filter:brightness(1.12)} +.btn:disabled{opacity:.45;cursor:not-allowed;filter:none} + +/* ============ cards & grids ============ */ +.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(250px,1fr));gap:14px} +.card{ + background:var(--panel);border:1px solid var(--line);border-radius:14px; + padding:18px 20px; +} +.card p{margin:0;color:var(--mut);font-size:14px} +.card h3{display:flex;align-items:center;gap:8px} + +/* status pills — every card that describes something has one */ +.pill{ + display:inline-block;font-size:10.5px;letter-spacing:.04em; + text-transform:uppercase;padding:2px 9px;border-radius:999px;margin-bottom:.6rem; +} +.p-live{background:rgba(79,209,165,.14);color:var(--srv)} +.p-alpha{background:rgba(214,255,61,.13);color:var(--acid)} +.p-designed{background:rgba(179,157,219,.14);color:var(--sia)} +.p-upcoming{background:rgba(139,152,169,.14);color:var(--mut)} + +/* ============ steps (numbered explainer lists) ============ */ +ol.steps{counter-reset:s;list-style:none;padding:0;margin:0;display:grid;gap:10px} +ol.steps li{ + counter-increment:s;display:grid;grid-template-columns:26px 1fr;gap:4px 14px; + align-items:start; + background:var(--panel2);border:1px solid var(--line);border-radius:12px; + padding:15px 18px; +} +ol.steps li::before{ + content:counter(s);grid-column:1;grid-row:1;align-self:start; + display:grid;place-items:center; + width:26px;height:26px;border-radius:50%; + background:rgba(214,255,61,.14);color:var(--acid); + font-size:13px;font-weight:700; +} +ol.steps li > *{grid-column:2;min-width:0} +ol.steps b{color:var(--ink);font-size:14.5px} +ol.steps span{color:var(--mut);font-size:14px;line-height:1.62} + +/* ============ tables ============ */ +table{width:100%;border-collapse:collapse;font-size:14.5px} +th,td{text-align:left;padding:9px 10px;border-bottom:1px solid var(--line);vertical-align:top} +th{color:var(--dim);font-weight:600;font-size:12.5px;text-transform:uppercase;letter-spacing:.04em} + +/* code chips + preformatted */ +td code,code.inline,.mono{ + font-family:ui-monospace,monospace;font-size:13px; + background:#0e131b;border:1px solid var(--line);border-radius:6px;padding:1px 6px; +} +pre{ + background:#0e131b;border:1px solid var(--line);border-radius:10px; + padding:13px 16px;overflow-x:auto; + font-family:ui-monospace,monospace;font-size:13px;color:#c9d4e3;margin:.8rem 0; +} + +/* ============ source badges (chain / sia / server) ============ */ +.src{font-size:12px;padding:1px 8px;border-radius:999px;white-space:nowrap} +.s-chain{background:rgba(214,255,61,.13);color:var(--chain)} +.s-sia{background:rgba(179,157,219,.16);color:var(--sia)} +.s-srv{background:rgba(79,209,165,.14);color:var(--srv)} + +/* ============ notes (advisory boxes) ============ */ +.note{ + background:var(--panel);border:1px solid var(--line);border-left:3px solid var(--acid); + border-radius:10px;padding:14px 18px;color:var(--mut);font-size:14px;margin-top:1.4rem; +} +.note b{color:var(--ink)} +.note.warn{border-left-color:var(--warn)} +.note.danger{border-left-color:var(--taken)} + +/* ============ footer ============ */ +footer{ + border-top:1px solid var(--line);padding:2.5rem 0 3.5rem; + color:var(--dim);font-size:13px;text-align:center;margin-top:2.5rem; +} +footer .fine{max-width:660px;margin:.8rem auto 0;line-height:1.7} + +/* ============ brand mark (inline SVG, replaces the emoji) ============ */ +.topnav .brand .logo{width:24px;height:16px;vertical-align:-2px;margin-right:8px} +.topnav .brand .logo .l1{stroke:var(--mut)} +.topnav .brand .logo .l2{stroke:var(--acid)} +.mark svg{width:150px;height:60px;display:block;margin:0 auto} +.mark .l1{stroke:var(--mut)} +.mark .l2{stroke:var(--acid)} + +/* ============ screenshots / figures ============ */ +figure.shot{margin:1.6rem 0 0;} +figure.shot img{display:block;width:100%;height:auto;border-radius:12px;border:1px solid var(--line);box-shadow:0 18px 48px rgba(0,0,0,.45)} +figure.shot figcaption{color:var(--dim);font-size:12.5px;margin-top:.6rem;text-align:center} +.card figure.shot{margin:.9rem 0 0} +.card figure.shot img{border-radius:8px;box-shadow:none} diff --git a/sirius/index.html b/sirius/index.html new file mode 100644 index 0000000..363b81d --- /dev/null +++ b/sirius/index.html @@ -0,0 +1,29 @@ + + + + + +Redirecting to Sirius.X + + + + + + + + +

⭐

Redirecting to Sirius.X…

The Sirius page moved to /sirius-x/.

+ + diff --git a/sirius/register.html b/sirius/register.html new file mode 100644 index 0000000..2de1c65 --- /dev/null +++ b/sirius/register.html @@ -0,0 +1,35 @@ + + + + + +Redirecting to Sirius.X — Register a name + + + + + + + + +

✏️

Redirecting to Sirius.X name search…

Name registration moved to /sirius-x/.

+ + diff --git a/store/index.html b/store/index.html new file mode 100644 index 0000000..6eb3ade --- /dev/null +++ b/store/index.html @@ -0,0 +1,26 @@ + + + + + +Moved — Silent Mode + + + + + + +

The store has a name now.

Silent Mode's app store is called Prometheus — home for apps, programs and + dApps published on chain, hosted on Sia. Read more at silentmode.st/prometheus/. + Redirecting you there.

+ + diff --git a/tlds/index.html b/tlds/index.html new file mode 100644 index 0000000..8b192b3 --- /dev/null +++ b/tlds/index.html @@ -0,0 +1,215 @@ + + + + + +TLDs — the top-level domains on the Bitcoin Cash chain — Silent Mode + + + + + + + + + + + + + + + + + + +

🌐

The TLD registry

Every BNS name lives under a top-level domain. Under Silent + Mode's per-TLD registry, each TLD is itself a certificate on the Bitcoin + Cash chain — minted once, held in a wallet, and required to exist before + any name under it can be registered. Browse the list, see how it works, + verify it against the chain.

+ Search a name → + See current TLDs +

+ +

What a TLD is here

A TLD (like .bch, .x, .p2p) is not just a + convention. Each is a CashTokens NFT with the TLD label as its commitment, + paying dust to a dedicated TLD-registry beacon on chain. That certificate + is the on-chain proof the TLD exists — and, once enforcement is on, it is + what makes any second-level name under it valid.

Register the TLD first. An operator mints the TLD certificate. Without it, names + under that TLD are not indexed by conforming resolvers.
Then register names under it. Each name is a separate cert, minted through the + registrar (sirius/register.html), and paid by the buyer to + their own wallet.
Verify against the chain. Anyone can walk the TLD beacon + (bchtest:qzc4c76vtw9nd49g6x8nmvc0jz62uvk4dc7hmpmerh on chipnet), rebuild the list, + and compare its cryptographic root — the tracker is a cache, not authority.

Why this exists. Without a registry, anyone could quietly declare a TLD + against the same beacon by minting a name under it. That leaves resolvers in + silent disagreement about what exists. Per-TLD certificates make the TLD set + itself something the chain records, so every resolver sees the same list. + Design: Decentralized.DNS/DESIGN-tld-registry.md in the project repo.

+ +

Current TLDs (chipnet)

Fourteen TLDs are offered for public name registration on the chipnet TLD + beacon as of 2026-08-29. The live count on the chain is the authoritative source — this table + may lag by minutes until the beacon confirms.

+ + + + + + + + + + + + + + + + + + +

TLD	Category (short)	Status
.bch	56253dcfbdfbeec8…	public
.p2p	d9b4e56d2293a4f9…	public
.bit	bc51b2407b13876e…	public
.nav	d2191a86685fa4c9…	public
.test	5197632adf1f7fd3…	public
.x	8dc32d8fd56f863b…	public
.asm	58d3381435268faf…	public
.neo	a511e80816976e92…	public
.gt	249a535df4633767…	public
.sc	f61fc465404a3eee…	public
.sia	4b3fccd4076eb48c…	public
.dex	9b230313b823202c…	public
.cex	69fd93aedee3d353…	public
.nt	5d18221bccaab2c0…	public

+ +

Get a name under one of these

Go to Sirius / register a name. Type a label — the + search fans out to every TLD in the registry in parallel and shows which + are available, which are taken, and which are held off the public + registry. Available ones mint straight into your own wallet in one + transaction; no yearly renewal.

+ +

How new TLDs get added

On chipnet the operator's key can mint any TLD directly. On mainnet, a covenant + will enforce a countersignature from that same key on every public TLD mint + — and a USD-denominated price floor tiered by label length. This is what + keeps someone from land-grabbing every ICANN TLD in one afternoon.

Operator TREG. The operator's wallet mints the TLD certificate; the label goes + into the NFT commitment, dust flows to the TLD beacon.
UI opt-in. The TLD is added to the registrar's list. A TLD can be minted but + intentionally omitted from the UI — the "held" pattern that keeps .com off + the public registry.
Snapshot republish. The tracker rebuilds and pushes a signed snapshot to Sia and + Nostr so downstream clients update without walking the chain themselves.

Chipnet is not mainnet. The covenant that turns "operator's key" into + something enforceable is a mainnet requirement. Until it lands, treat the chipnet TLD list as an + operator-signed statement, not a decentralized fact.

+ +

Verify the list against the chain

The tracker is a cache. The chain is the authority. Two independent paths, both public:

+ +

Fetch the signed snapshot from Nostr

Kind 30078 replaceable event, d-tag bns-tld-list, signed by the + tracker's Nostr key. Any relay carries it; the event's content field carries the current + snapshot root and the Sia URL where the full JSON lives.

Pubkey (x-only, hex): f2c925194c531c7c398017e35b2396df64a61a613aa5fadebdf1f4990f2267f4
Relays: wss://nos.lol · wss://relay.damus.io
Filter (nostr-tools / rust-nostr): { authors: [<pubkey>], kinds: [30078], "#d": ["bns-tld-list"] }

+ +

Rebuild locally from the TLD beacon

Any electrum server that indexes the chipnet chain will return the beacon's history. Recompute + the snapshot's canonical form (sort by TLD, JSON.stringify), sha256 it, compare — if the hash matches + the tracker's root, the snapshot is a faithful summary of what the chain says.

cd Argus && node --input-type=module -e "
+import { loadWallet } from './src/lib/wallet.js';
+import { buildTldSnapshot } from './src/lib/tld-index.js';
+import { TLD_BEACON } from './src/config.js';
+const w = await loadWallet('main');
+const history = await w.provider.getHistory(TLD_BEACON);
+const txs = new Map();
+for (const {tx_hash} of history) try { txs.set(tx_hash, await w.provider.getRawTransactionObject(tx_hash)); } catch {}
+console.log(buildTldSnapshot({ history, txs }));
+process.exit(0);"

+ + + + + + + + + + + + + +

Open this	What you get	Where the page lives
`navigate.st/bns/hello.bch`	A small page	inside a blockchain transaction
`navigate.st/bns/silentmode.bch`	This project's own on-chain demo	inside a blockchain transaction
`navigate.st/bns/theseus.x`	Theseus Navigator's own page	Sia storage network
`navigate.st/bns/coinspectrum.deviant.bch`	A full multi-file site	Sia storage network
`navigate.st/bns/coinspectrum.bch`	The same site again	an ordinary web server

+ + +

Browser extensions

Add BNS to a browser you already use. The lightest possible install — + no daemon, no system changes, works only inside the browser it's installed in.

+ +

+ alpha +

Ariadne for Firefox

A browser add-on that resolves BNS names inside Firefox. 8 KB, no + dependencies, no background service, no system changes. Also runs on + Firefox for Android. Known limit: no TLS pinning yet — sites reached + over ip records are only as trustworthy as the + upstream server. Being fixed.

Firefox · ~8 KB · packaging in progress

+ Packaging in progress +

+ + +

System-wide — Ariadne Resolver (standalone)

For advanced users who want BNS names working in every + browser on their Windows machine — Chrome, Edge, Firefox, everything — without + installing Theseus. Runs as a small background service that intercepts DNS and + mints TLS certificates on the fly for BCH-registered names. This will become an + standalone download; a future Theseus release will fetch and update it from + inside the browser's Settings panel.

+ +

+ alpha +

Ariadne Resolver for Windows

Asks for administrator rights because it changes how your machine resolves + names. Adds a background service, adds NRPT rules that route only BCNR + TLDs to the local daemon, imports one root certificate name-constrained + to those TLDs — the root cannot vouch for .com. + Everything reverses with the bundled uninstaller.

Windows 64-bit · v0.1.2 · bundled Node runtime · unsigned build

+ Installer +

SHA-256 — verify before elevating:

Installer5a2c9e4f3c5e1a162008641019f5ffc35968751c0440f94d3c5fe67aafb8cc5e

+ + +

Verifying every download

Windows

After downloading, compute the SHA-256 and compare it to the value above: + certutil -hashfile <file> SHA256. + Builds carry no code-signing certificate — that requires a legal + identity, which is what this project exists to avoid. Windows will warn about + an unrecognized app; that warning is expected. The hash is the real check.

Android

Hash the downloaded .apk on a computer before + moving it to the phone, or use any file-hashing app. The signing + certificate fingerprint is what matters most — every future update is + signed with the same key. Android will refuse to install an update signed + by anyone else, so once you have checked it, that check protects every + version after this one.

On chain

The canonical checksum list will be published as a record on + releases.silentmode.bch — the name pins where it + is served from, so a tampered mirror cannot change what you check against. + Machine-readable manifest: releases-manifest.json. + Human-readable page: /releases/.

+ +

+ + + + + diff --git a/vendor/LICENSE.gpl-3.0.txt b/vendor/LICENSE.gpl-3.0.txt new file mode 100644 index 0000000..f288702 --- /dev/null +++ b/vendor/LICENSE.gpl-3.0.txt @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. diff --git a/vendor/LICENSE.lgpl-3.0.txt b/vendor/LICENSE.lgpl-3.0.txt new file mode 100644 index 0000000..0a04128 --- /dev/null +++ b/vendor/LICENSE.lgpl-3.0.txt @@ -0,0 +1,165 @@ + GNU LESSER GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + + This version of the GNU Lesser General Public License incorporates +the terms and conditions of version 3 of the GNU General Public +License, supplemented by the additional permissions listed below. + + 0. Additional Definitions. + + As used herein, "this License" refers to version 3 of the GNU Lesser +General Public License, and the "GNU GPL" refers to version 3 of the GNU +General Public License. + + "The Library" refers to a covered work governed by this License, +other than an Application or a Combined Work as defined below. + + An "Application" is any work that makes use of an interface provided +by the Library, but which is not otherwise based on the Library. +Defining a subclass of a class defined by the Library is deemed a mode +of using an interface provided by the Library. + + A "Combined Work" is a work produced by combining or linking an +Application with the Library. The particular version of the Library +with which the Combined Work was made is also called the "Linked +Version". + + The "Minimal Corresponding Source" for a Combined Work means the +Corresponding Source for the Combined Work, excluding any source code +for portions of the Combined Work that, considered in isolation, are +based on the Application, and not on the Linked Version. + + The "Corresponding Application Code" for a Combined Work means the +object code and/or source code for the Application, including any data +and utility programs needed for reproducing the Combined Work from the +Application, but excluding the System Libraries of the Combined Work. + + 1. Exception to Section 3 of the GNU GPL. + + You may convey a covered work under sections 3 and 4 of this License +without being bound by section 3 of the GNU GPL. + + 2. Conveying Modified Versions. + + If you modify a copy of the Library, and, in your modifications, a +facility refers to a function or data to be supplied by an Application +that uses the facility (other than as an argument passed when the +facility is invoked), then you may convey a copy of the modified +version: + + a) under this License, provided that you make a good faith effort to + ensure that, in the event an Application does not supply the + function or data, the facility still operates, and performs + whatever part of its purpose remains meaningful, or + + b) under the GNU GPL, with none of the additional permissions of + this License applicable to that copy. + + 3. Object Code Incorporating Material from Library Header Files. + + The object code form of an Application may incorporate material from +a header file that is part of the Library. You may convey such object +code under terms of your choice, provided that, if the incorporated +material is not limited to numerical parameters, data structure +layouts and accessors, or small macros, inline functions and templates +(ten or fewer lines in length), you do both of the following: + + a) Give prominent notice with each copy of the object code that the + Library is used in it and that the Library and its use are + covered by this License. + + b) Accompany the object code with a copy of the GNU GPL and this license + document. + + 4. Combined Works. + + You may convey a Combined Work under terms of your choice that, +taken together, effectively do not restrict modification of the +portions of the Library contained in the Combined Work and reverse +engineering for debugging such modifications, if you also do each of +the following: + + a) Give prominent notice with each copy of the Combined Work that + the Library is used in it and that the Library and its use are + covered by this License. + + b) Accompany the Combined Work with a copy of the GNU GPL and this license + document. + + c) For a Combined Work that displays copyright notices during + execution, include the copyright notice for the Library among + these notices, as well as a reference directing the user to the + copies of the GNU GPL and this license document. + + d) Do one of the following: + + 0) Convey the Minimal Corresponding Source under the terms of this + License, and the Corresponding Application Code in a form + suitable for, and under terms that permit, the user to + recombine or relink the Application with a modified version of + the Linked Version to produce a modified Combined Work, in the + manner specified by section 6 of the GNU GPL for conveying + Corresponding Source. + + 1) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (a) uses at run time + a copy of the Library already present on the user's computer + system, and (b) will operate properly with a modified version + of the Library that is interface-compatible with the Linked + Version. + + e) Provide Installation Information, but only if you would otherwise + be required to provide such information under section 6 of the + GNU GPL, and only to the extent that such information is + necessary to install and execute a modified version of the + Combined Work produced by recombining or relinking the + Application with a modified version of the Linked Version. (If + you use option 4d0, the Installation Information must accompany + the Minimal Corresponding Source and Corresponding Application + Code. If you use option 4d1, you must provide the Installation + Information in the manner specified by section 6 of the GNU GPL + for conveying Corresponding Source.) + + 5. Combined Libraries. + + You may place library facilities that are a work based on the +Library side by side in a single library together with other library +facilities that are not Applications and are not covered by this +License, and convey such a combined library under terms of your +choice, if you do both of the following: + + a) Accompany the combined library with a copy of the same work based + on the Library, uncombined with any other library facilities, + conveyed under the terms of this License. + + b) Give prominent notice with the combined library that part of it + is a work based on the Library, and explaining where to find the + accompanying uncombined form of the same work. + + 6. Revised Versions of the GNU Lesser General Public License. + + The Free Software Foundation may publish revised and/or new versions +of the GNU Lesser General Public License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If the +Library as you received it specifies that a certain numbered version +of the GNU Lesser General Public License "or any later version" +applies to it, you have the option of following the terms and +conditions either of that published version or of any later version +published by the Free Software Foundation. If the Library as you +received it does not specify a version number of the GNU Lesser +General Public License, you may choose any version of the GNU Lesser +General Public License ever published by the Free Software Foundation. + + If the Library as you received it specifies that a proxy can decide +whether future versions of the GNU Lesser General Public License shall +apply, that proxy's public statement of acceptance of any version is +permanent authorization for you to choose that version for the +Library.