/**
* The pages Prometheus.X renders.
*
* Each export is `(req?) => {title, description, body}`. The server is the one
* that wraps them in the layout — these just return the inner content.
*
* The copy was lifted from site/prometheus/index.html (the ICANN teaser) and
* split by concern so each page is one topic a reader opened on purpose. The
* single-scroll version lives at silentmode.st/prometheus and will stay there
* as the SEO-friendly mirror.
*/
import { renderCategoriesGrid, countsByCategory } from './pages-browse.js';
import { countActive } from './db.js';
/**
* The "Browse by category" section used on the home page. Lives here so the
* home page's inline template reads cleanly, but delegates the actual grid to
* pages-browse.js so a single row of counts drives both surfaces.
*/
function renderHomeBrowseSection() {
const total = countActive();
return `
Browse by category
On a conventional store, one company decides which shelf an app
belongs on. Here the publisher labels their own listing, and your trust list
decides whether to show it. The categories below are the initial shape; a new
one gets proposed by publishing a listing against it.
No live listings yet.
The on-chain publication protocol (APS1) is in
progress; in the meantime the site, the scanner, the publisher-signed
listing endpoint and the publishers' walkthrough are up. First real
listings appear in this grid as they publish.
` : ''}
`;
}
/* ------------------------------- home ------------------------------- */
export function home() {
// Schema.org on home — gives Google a WebSite + SearchAction result card for
// "prometheus.x" queries, plus Organization for the knowledge panel.
const websiteLd = JSON.stringify({
'@context': 'https://schema.org',
'@type': 'WebSite',
name: 'Prometheus.X',
alternateName: ['Prometheus', 'Decentralized App Store'],
url: 'https://prometheus.x/',
description: 'The decentralized app store. Apps, programs, dApps and libraries signed on the Bitcoin Cash chain and hosted on the decentralized web.',
});
const orgLd = JSON.stringify({
'@context': 'https://schema.org',
'@type': 'Organization',
name: 'Prometheus',
url: 'https://prometheus.x/',
sameAs: ['https://silentmode.st/prometheus', 'https://code.silentmode.st/silentmode/prometheus'],
description: 'A permissionless app store: listings on the Bitcoin Cash chain, binaries on the decentralized web, endorsements by signature. Anyone can publish; nobody can gatekeep.',
});
return {
title: 'The decentralized app store',
description:
'Prometheus.X — the decentralized app store. Web3 browsers, BCH wallets, mobile and desktop apps, dApps and libraries. Listings on the Bitcoin Cash chain, binaries on the decentralized web, endorsements by signature. Anyone can publish; nobody can gatekeep.',
here: '/',
headExtra:
`\n` +
``,
body: `
Prometheus.X
The decentralized app store. A home for apps, programs,
dApps, and libraries — listed and settled on the Bitcoin Cash chain,
hosted on the decentralized web, endorsed by signature. Anyone can
publish. Nobody can gatekeep.
Named for the one who gave fire to humans and did not ask the gods first.
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. 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.
Scan reports are signed and attached.Prometheus runs an automated malware scan on every binary it hosts
and publishes the signed report alongside the listing. The chain still
goes up; the report tells your client whether to warn.
Install verifies against the chain.Clients pull the file, check the SHA-256 against the on-chain
record, check the signing certificate against the fingerprint, and only
then install. The chain is the truth, not the mirror.
`,
};
}
/* ------------------------------- publish ---------------------------- */
export function publish() {
return {
title: "Publishers' walkthrough",
description:
'The end-to-end flow of publishing an app on Prometheus: name, hosting, manifest, listing, verification, updates, withdrawal, and endorsements.',
here: '/publish',
body: `
Publishers' walkthrough
Pick a name, host the binary, write the manifest, sign the listing,
verify it resolves, ship an update when it's time. Here's the whole shape.
Publishing an app on Prometheus is a sequence of signed records
pointing at files stored where you keep them. The whole thing — identity,
hosting, the listing itself — is yours; nothing here grants anyone else
permission to pull your app down, raise your price, or take a cut of what
people pay you for it.
Steps are tagged available today or
designed so it is clear what you can do
now and what is waiting on the APS1 record format landing.
What you need before you start
available today
A BNS name
Any name registered through Sirius works. The
name is what signs the listing, so it is also what readers trust the
listing by. Fractions of a cent to register, no monthly bill.
available today
Somewhere to put the binary
Prometheus can host for you — upload here and we put it on Sia, signed
and scanned. If you'd rather self-host on your own URL, the listing just
records the URL and the hash and will fetch from wherever you say.
available today
A signing key
The private key for the BNS name. If the name is in a wallet you already
use for Bitcoin Cash, that key already exists; publishing re-uses it.
available today
A pinch of BCH
One listing is one transaction. The transaction fee is cents, denominated
in sats. During the free wave, that is the only cost. Later, a flat
listing fee covers the Sia storage.
The walkthrough
1. Register a name — or use one you already own.The listing is signed by the name's key. A reader who follows your
name will see your listing with the publisher chip set to that name; a
reader who does not will see it marked unsigned by anyone they trust.
One name can carry any number of listings, so a studio with three games
publishes under one identity.
2. Upload the binary (or point us at your URL).Prometheus runs a malware scan on upload. If it passes, the file
goes into a Sia bucket Silent Mode controls, the signed scan report is
prepared, and the manifest fields are prefilled. If you'd rather host
the file yourself, give us the URL and the expected SHA-256; the manifest
records both, the scan still runs against whatever the URL serves, and
the client refuses to install a byte-mismatched download.
3. Fill in the manifest.Name, description, category, version, icon, download URL,
sha256, and the signing-cert fingerprint when
the binary itself is signed (it should be, if the platform supports it).
Icons are referenced by URL, not embedded. A 2 KB manifest with a 500 KB
icon beside it is the right shape; a 500 KB manifest is not.
4. Sign the APS1 record with your BNS key.One transaction. The on-chain record carries the manifest hash,
the category label, and the signature from your name's key. From the
moment the transaction confirms, every client that follows the chain can
see your listing — no approval queue, no editorial review, no publisher
dashboard waiting for a human on the other end.
5. Verify it resolves.Open one of the Ariadne clients and look for your listing in the
category you labelled it under. The client should pull the manifest from
Sia, show the fields you wrote, surface the scan report, and offer the
download. Clicking install should fetch the binary, check the SHA-256,
check the signing certificate, and only then run.
6. Ship updates with another signed record.A new version is another APS1 transaction referencing the same app
id, signed by the same key, pointing at a new manifest hash. Clients
already following the app see the update offered the next time they
check. Nobody can push a hostile update unless they have your key.
7. Withdraw a listing when it is time.A withdrawal is a signed record that marks the app id as retired.
Clients hide the listing from browse and refuse to install it, though
anyone with the manifest hash and the binary can still side-load it —
the chain is a signal, not a lock.
A note on endorsements
A listing is one signed record. An endorsement is another — a short
on-chain statement from any name saying "I vouch for this app." Readers whose
trust list includes the endorser's name will see your listing marked as
endorsed by them; readers who do not follow that name will not. Endorsements
are not reviews, and the client does not aggregate them into a star rating.
They are statements: who said what, when, signed.
You can endorse too. Any name can publish an endorsement
of any listing, and most publishers end up endorsing a handful of apps they
use themselves. The trust graph that emerges is the directory's real curation
layer; the categories are just filing.
What this costs
Per listing
One Bitcoin Cash transaction. Fractions of a cent at current rates. Paid
once, lives on chain.
Per update
Another transaction. Same shape, same cost. There is no "update bundle"
discount because there is no central party to collect one.
Per month of hosting
Free during the opening wave while Prometheus underwrites the storage.
Afterwards, a flat per-listing fee (planned around $1 at current rates)
covers Sia storage for the typical binary. Your own HTTPS host costs
what it costs you.
Per download
Zero to the directory. The reader pulls the binary from wherever the
manifest points; Prometheus never meters the traffic.
Where this stands today. Names, Sia hosting and
BCH signing exist and are in use. The APS1 record
format and the client-side browse/install flow are being wired. This page
describes the end state; the first live listings will go up as soon as the
submit path lands on this site and the Ariadne clients learn to read it.
`,
};
}
/* ------------------------------- browse ----------------------------- */
export function browse() {
const total = countActive();
const totalLabel = total === 0
? `No listings yet — the eight categories are set and ready to receive publications.`
: `${total} ${total === 1 ? 'listing' : 'listings'} across ${Object.values(countsByCategory()).filter((n) => n > 0).length} ${Object.values(countsByCategory()).filter((n) => n > 0).length === 1 ? 'category' : 'categories'}.`;
return {
title: 'Browse',
description:
'Browse apps and programs published on Prometheus by category. Signed listings on the Bitcoin Cash chain; scan reports attached; your trust list filters.',
here: '/browse',
body: `
Browse
Signed listings on chain, scan reports attached, your trust list
decides what to render.
${totalLabel}
${renderCategoriesGrid({ verbose: false })}
`,
};
}
/* ------------------------------- submit ----------------------------- */
export function submit() {
return {
title: 'Submit an app',
description:
'Upload an app to Prometheus. We scan it, generate the manifest, you sign with your BNS key and the listing goes live.',
here: '/submit',
body: `
Submit an app
Upload → fill manifest → sign with your wallet → publish.
Your key stays with you.
The server scans with ClamAV + VirusTotal (where configured),
computes the SHA-256, and attaches a signed scan report to your listing.
Only clean uploads can proceed.
Upload accepted
·
·
2 · Describe your listing
Every field is signed in step 3, so take a minute — editing
the signed payload is a new signature, not a quick fix.
3 · Sign with your BNS key
The message below carries every field from step 2 in canonical
form. Sign it with the BCH key for the address that owns
your name on chipnet.
Any BIP-137 wallet works (Electron Cash, Deviant, Cashonize, Theseus's Aegis).
Message to sign
Theseus wallet detected.
Aegis is injected on this page. Sign without pasting.
Or paste a BIP-137 signature
Base64, 88 characters. From any wallet's "sign message" dialog.
4 · Publish
POSTs the signed listing to /api/listing.
The server re-verifies the signature against the on-chain owner of your BNS
name and stores the row. The listing is live on browse the moment the POST
returns 201.
`,
};
}
/* ------------------------------- boundaries ------------------------- */
export function boundaries() {
return {
title: 'Boundaries',
description:
'What Prometheus does and does not do. Not a curator. Not a moderator. Storage costs money. Readers decide; the chain carries signed records.',
here: '/boundaries',
body: `
Boundaries
What this directory is not, and why.
A permissionless app directory earns the right to call itself
permissionless by being honest about what that costs. Here is the shape of
the trade.
What Prometheus is not
Not a curator
Prometheus does not decide what is on it. Malware can be published — as
it can on any store. The scan report tells your client to warn; the
trust lists you subscribe to filter the 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.
Not a payment processor
Payments in an app go publisher-to-reader. The listing may carry a BCH
receive address or a wallet-connect URL; Prometheus never routes a
transaction. There is no refund desk because there is no middleman to
issue a refund.
Not an identity provider
The only identity on Prometheus is the BNS name a listing is signed by.
Readers decide which names count via their own trust lists. There is no
Prometheus account, no "verified publisher" badge, no sign-in flow for
readers.
What Silent Mode does control
The scan report
Our ClamAV + VirusTotal pipeline runs on every binary we host. The
signed report is attached to the listing. We cannot stop a listing from
being on chain; we can tell readers what we found.
Which binaries we host
Silent Mode's Sia bucket. Operators can refuse to host something and
require the publisher to self-host at their own URL. The listing still
exists; the scan report says we did not host it.
The default sort
What the Browse page shows first is a choice. We publish the sort order
and let clients override it. The chain holds the data; the directory is
one lens.
The publish mode
Three modes exist (append-only, scan-first-blocking, human-review).
Operators pick which one is active per category. The current mode is
always visible on this page; a change is announced before it takes
effect.
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. During the
opening wave Silent Mode absorbs it; afterwards it is a flat per-listing
fee paid in BCH.
`,
};
}
/* ------------------------------- 404 -------------------------------- */
export function notFound(req) {
return {
title: 'Not here',
description: 'The requested page does not exist on Prometheus.',
here: '',
body: `