pithos/hosted/package.json

{
  "name": "pithos-hosted",
  "version": "0.1.0",
  "private": true,
  "description": "Pithos on Silent Mode: one s3d per person, on their own Sia account, behind a gateway that adds sign-in, per-folder access and client-side encryption.",
  "license": "MPL-2.0",
  "type": "module",
  "main": "main.js",
  "scripts": {
    "start": "node main.js --config /etc/pithos-hosted.json",
    "test": "node --test test/*.test.js"
  },
  "engines": {
    "node": ">=20"
  },
  "dependencies": {
    "@bitauth/libauth": "3.1.0-next.8"
  }
}
Pithos: run your drives on Silent Mode with your own Sia account s3d binds one Sia account per process, so the server runs one s3d per person (pithos-hosted), started on demand and flushed and stopped when idle. Only the connected s3d data folder moves between PC and server; the Sia recovery phrase never leaves the PC and nothing is re-uploaded to Sia. Because the server holds the connection key, local Pithos encrypts names and contents before they leave the machine, with keys from the Theseus vault (or a local key file elsewhere). What s3d cannot do on its own, the gateway now enforces: public folders, expiring share links and S3 keys for other people limited to one folder with read, add-only or edit rights. Files those reach are stored readable, since visitors have no key, and go back to encrypted when the rule is removed. Sign-up needs a BNS name signature, a deposit or an invite, with a per-IP limit. 2026-10-04 01:33:20 +02:00			`{`
			`"name": "pithos-hosted",`
			`"version": "0.1.0",`
			`"private": true,`
			`"description": "Pithos on Silent Mode: one s3d per person, on their own Sia account, behind a gateway that adds sign-in, per-folder access and client-side encryption.",`
			`"license": "MPL-2.0",`
			`"type": "module",`
			`"main": "main.js",`
			`"scripts": {`
pithos-hosted: tests for signatures, rules and the sign-up gate The gateway is the only thing standing between a shared key and the rest of an owner's drive, so its SigV4 check, grant decisions and the BNS/deposit proofs get tests that need no s3d to run. 2026-10-04 01:34:25 +02:00			`"start": "node main.js --config /etc/pithos-hosted.json",`
			`"test": "node --test test/*.test.js"`
Pithos: run your drives on Silent Mode with your own Sia account s3d binds one Sia account per process, so the server runs one s3d per person (pithos-hosted), started on demand and flushed and stopped when idle. Only the connected s3d data folder moves between PC and server; the Sia recovery phrase never leaves the PC and nothing is re-uploaded to Sia. Because the server holds the connection key, local Pithos encrypts names and contents before they leave the machine, with keys from the Theseus vault (or a local key file elsewhere). What s3d cannot do on its own, the gateway now enforces: public folders, expiring share links and S3 keys for other people limited to one folder with read, add-only or edit rights. Files those reach are stored readable, since visitors have no key, and go back to encrypted when the rule is removed. Sign-up needs a BNS name signature, a deposit or an invite, with a per-IP limit. 2026-10-04 01:33:20 +02:00			`},`
			`"engines": {`
			`"node": ">=20"`
			`},`
			`"dependencies": {`
			`"@bitauth/libauth": "3.1.0-next.8"`
			`}`
			`}`