aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFuwn <[email protected]>2026-02-27 09:43:29 -0800
committerFuwn <[email protected]>2026-02-27 09:43:29 -0800
commitd1a0e8774953cb7a72d8f65a42074d5af08f1212 (patch)
tree66bcc81f3d82289894f78e1341f866882f63174b
parentdocs: add mode selection guidance for mirror resolver and thin (diff)
downloadplutia-test-d1a0e8774953cb7a72d8f65a42074d5af08f1212.tar.xz
plutia-test-d1a0e8774953cb7a72d8f65a42074d5af08f1212.zip
docs: refine mode selection wording for clarity
-rw-r--r--README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/README.md b/README.md
index 65864ac..dd73eca 100644
--- a/README.md
+++ b/README.md
@@ -224,7 +224,9 @@ services:
|---|---|---|---|---|---|---|---|
| `mirror` | ~1.17 KB/op (~100 GB at current PLC head) | High sustained | Continuous full replay + polling | Full chain verification at ingest (`verify=full`), deterministic state, signed checkpoints | Yes | Yes | Independent mirrors, auditors, proof-serving infrastructure |
| `resolver` | ~0.8 KB/op (~60–70 GB at current PLC head) | Medium to high sustained | Continuous replay + polling, state-only storage | Full verification supported; stores resolved state without full block archive | No | No | Operators who want full verification with lower storage overhead |
-| `thin` | ~475 bytes per cached DID (scales with active usage, not global PLC size) | Low idle, bursty on requests | No global replay; fetches and verifies per DID on demand | Full chain verification per requested DID (signature + prev-link), cache-backed | No | No | Edge deployments, small VPS instances, low-disk resolvers |
+| `thin` | ~475 bytes per cached DID (scales with active usage, not global PLC size) | Low idle, bursty on requests | No global replay; fetches and verifies per DID on demand | Performs full signature and prev-link verification for each requested DID chain before caching. | No | No | Edge deployments, small VPS instances, low-disk resolvers |
+
+Disk usage scales linearly with total PLC operation count.
### Mirror Mode
@@ -240,6 +242,7 @@ services:
- Supports full verification policies while reducing storage versus mirror mode.
- Maintains current resolved state for all ingested DIDs.
- Offers a balanced operational profile for most self-hosted operators.
+- Resolver mode does not support checkpoint inclusion proofs because it does not retain historical block references required for Merkle inclusion verification.
### Thin Mode