@optimystic/db-p2p 0.22.0 → 0.24.1

package/readme.md

@@ -1,668 +1,668 @@
-# Optimystic DB-P2P
-
-A distributed peer-to-peer database system that provides concrete implementations of the Optimystic database abstractions using pluggable storage backends and libp2p networking. This package transforms the interfaces and abstractions from `@optimystic/db-core` into a fully operational distributed database system.
-
-> **Storage is pluggable.** `db-p2p` owns the distributed layer (repo/cluster/coordination) and the storage *interfaces* (`IRawStorage`, `IBlockStorage`, `IKVStore`) plus an in-memory backend. Concrete persistent backends live in separate packages — filesystem persistence is [`@optimystic/db-p2p-storage-fs`](../db-p2p-storage-fs); see also `-storage-ns` (NativeScript/SQLite), `-storage-rn` (React Native/LevelDB), and `-storage-web` (IndexedDB).
-
-## Overview
-
-The `@optimystic/db-core` package provides abstractions and interfaces for database operations—immutable blocks, versioned transactions, repository interfaces, and collection data structures. However, it doesn't provide concrete implementations for storage or distribution. `db-p2p` provides concrete implementations of the core abstractions using:
-
-- **Versioned block storage** (`StorageRepo` / `BlockStorage`) layered over a pluggable `IRawStorage` backend — an in-memory backend ships here; filesystem persistence lives in `@optimystic/db-p2p-storage-fs`
-- **libp2p networking** for decentralized peer-to-peer communication
-- **Distributed consensus** using 2-phase commit protocols for consistency
-- **Fault-tolerant coordination** with automatic recovery and data restoration
-
-The result is a fully operational distributed database system that implements the interfaces defined in the core abstractions to provide a complete distributed database system.
-
-## Architecture Overview
-
-The system provides three distinct communication interfaces, each serving different roles in the distributed architecture:
-
-```mermaid
-graph TD
-    subgraph "External Client Process"
-        A[Application Code]
-        B[RepoClient]
-        A --> B
-    end
-    
-    subgraph "Coordinator Node Process<br/>(Orchestrates Transactions)"
-        C[RepoService]
-        D[CoordinatorRepo]
-        E[ClusterClient]
-        F[StorageRepo]
-        subgraph "Local Storage"
-            F1[BlockStorage]
-            F2[IRawStorage backend]
-            F3[Backend store]
-        end
-        C --> D
-        D --> E
-        D --> F
-        F --> F1
-        F1 --> F2
-        F2 --> F3
-    end
-    
-    subgraph "Cluster Peer 1 Process<br/>(Participates in Consensus)"
-        G1[ClusterService]
-        H1[ClusterMember]
-        I1[StorageRepo]
-        subgraph "Local Storage 1"
-            I1A[BlockStorage]
-            I1B[IRawStorage backend]
-            I1C[Backend store]
-        end
-        G1 --> H1
-        H1 --> I1
-        I1 --> I1A
-        I1A --> I1B
-        I1B --> I1C
-    end
-    
-    subgraph "Cluster Peer 2 Process<br/>(Participates in Consensus)"
-        G2[ClusterService]
-        H2[ClusterMember]
-        I2[StorageRepo]
-        subgraph "Local Storage 2"
-            I2A[BlockStorage]
-            I2B[IRawStorage backend]
-            I2C[Backend store]
-        end
-        G2 --> H2
-        H2 --> I2
-        I2 --> I2A
-        I2A --> I2B
-        I2B --> I2C
-    end
-    
-    subgraph "Cluster Peer N Process<br/>(Participates in Consensus)"
-        G3[ClusterService]
-        H3[ClusterMember]
-        I3[StorageRepo]
-        subgraph "Local Storage N"
-            I3A[BlockStorage]
-            I3B[IRawStorage backend]
-            I3C[Backend store]
-        end
-        G3 --> H3
-        H3 --> I3
-        I3 --> I3A
-        I3A --> I3B
-        I3B --> I3C
-    end
-    
-    %% Network communication
-    B -.->|"/optimystic/&lt;network&gt;/repo/1.0.0"| C
-    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G1
-    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G2
-    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G3
-```
-
-### Repo Layer: External Client Interface
-
-The repo layer provides the interface for external clients to communicate with the distributed database:
-
-- **RepoClient**: Allows external clients to connect to any coordinator node
-- **RepoService**: Handles incoming requests from external clients
-- **CoordinatorRepo**: Orchestrates distributed transactions by coordinating with cluster peers
-- **Network transparency**: Same `IRepo` interface whether local or distributed
-
-### Cluster Layer: Peer-to-Peer Coordination Interface
-
-The cluster layer provides the interface for coordinators to communicate with other peers in the cluster:
-
-- **ClusterClient**: Allows coordinators to send consensus requests to cluster peers
-- **ClusterService**: Handles incoming consensus requests from coordinators
-- **ClusterMember**: Implements 2-phase commit protocol for distributed consensus
-- **Byzantine fault tolerance**: Ensures consistency even with peer failures
-
-### Storage Layer: Persistent Data Implementation
-
-The storage layer implements the core database abstractions over a pluggable raw-storage backend:
-
-- **StorageRepo**: Implements the `IRepo` interface on top of `BlockStorage` — backend-agnostic
-- **BlockStorage**: Provides versioned block storage with conflict resolution, reading/writing through an injected `IRawStorage`
-- **`IRawStorage`**: The raw persistence interface. An in-memory backend ships in this package; the filesystem backend (`FileRawStorage`) lives in `@optimystic/db-p2p-storage-fs`
-- **Data restoration**: Pluggable restoration for missing data from network peers
-
-## Detailed Component Architecture
-
-### Repo Layer Components
-
-#### `RepoClient`
-Allows external clients to connect to coordinator nodes:
-
-```typescript
-class RepoClient extends ProtocolClient implements IRepo {
-  static create(peerId: PeerId, peerNetwork: IPeerNetwork): RepoClient
-  // Implements same IRepo interface as local storage
-}
-```
-
-**Key Features:**
-- Network-transparent database operations for external clients
-- Automatic protocol handling and message serialization
-- Error handling for network failures and timeouts
-- Connection pooling and optimization
-
-#### `RepoService`
-Handles incoming repository protocol messages from external clients:
-
-```typescript
-class RepoService implements Startable {
-  // Protocol: /optimystic/<network>/repo/1.0.0 (see docs/repo.md § Protocol id conventions)
-  // Transport: Length-prefixed JSON over libp2p streams
-  async start(): Promise<void>
-  async stop(): Promise<void>
-}
-```
-
-**Key Features:**
-- Registers and handles the repository protocol
-- Routes operations from external clients to coordinator implementation
-- Manages concurrent connections and stream processing
-- Provides comprehensive error handling and logging
-
-#### `CoordinatorRepo`
-Orchestrates distributed transactions by coordinating with cluster peers:
-
-```typescript
-class CoordinatorRepo implements IRepo {
-  constructor(
-    keyNetwork: IKeyNetwork,
-    createClusterClient: (peerId: PeerId) => ClusterClient,
-    storageRepo: IRepo
-  )
-}
-```
-
-**Key Features:**
-- Manages distributed transactions using cluster consensus
-- Integrates with key network for peer discovery
-- Uses cluster layer to coordinate with other peers
-- Maintains local storage directly while coordinating remote operations
-
-### Cluster Layer Components
-
-#### `ClusterClient`
-Allows coordinators to send consensus requests to cluster peers:
-
-```typescript
-class ClusterClient extends ProtocolClient implements ICluster {
-  async update(record: ClusterRecord): Promise<ClusterRecord>
-}
-```
-
-**Key Features:**
-- Network communication for consensus operations
-- Handles cluster record updates and responses
-- Manages timeouts and retries for consensus requests
-
-#### `ClusterService`
-Handles incoming consensus requests from coordinators:
-
-```typescript
-class ClusterService implements Startable {
-  // Protocol: /optimystic/<network>/cluster/1.0.0 (built from protocolPrefix)
-  // Handles ClusterRecord updates for consensus
-}
-```
-
-**Key Features:**
-- Registers and handles the cluster consensus protocol
-- Routes consensus requests to local cluster member
-- Manages concurrent consensus operations
-
-#### `ClusterMember`
-Implements 2-phase commit protocol for distributed consensus:
-
-```typescript
-class ClusterMember implements ICluster {
-  async update(record: ClusterRecord): Promise<ClusterRecord>
-  // Handles: Promise collection → Majority consensus → Commit execution
-}
-```
-
-**Key Features:**
-- Complete 2-phase commit protocol implementation
-- Conflict detection and resolution
-- Cryptographic signature verification
-- Automatic timeout and cleanup management
-- Uses storage layer to execute operations when consensus is reached
-
-### Storage Layer Components
-
-#### `StorageRepo`
-Implements the `IRepo` interface over `BlockStorage` — independent of any particular storage backend:
-
-```typescript
-class StorageRepo implements IRepo {
-  async get(blockGets: BlockGets): Promise<GetBlockResults>
-  async pend(request: PendRequest): Promise<PendResult>  
-  async commit(request: CommitRequest): Promise<CommitResult>
-  async cancel(actionRef: ActionBlocks): Promise<void>
-}
-```
-
-**Key Features:**
-- Concrete implementation of core database abstractions
-- Orchestrates transactions across multiple blocks
-- Handles revision conflicts and missing transaction detection
-- Provides atomic commit operations with proper locking
-
-#### `BlockStorage`
-Provides versioned block storage with conflict resolution, reading and writing through an injected `IRawStorage` backend:
-
-```typescript
-class BlockStorage implements IBlockStorage {
-  constructor(blockId: BlockId, storage: IRawStorage, /* … */)
-  async getBlock(rev?: number): Promise<{ block: IBlock, actionRev: ActionRev }>
-  async savePendingAction(actionId: ActionId, transform: Transform): Promise<void>
-  async promotePendingAction(actionId: ActionId): Promise<void>
-  async ensureRevision(rev: number): Promise<void>
-}
-```
-
-**Key Features:**
-- Maintains complete revision history for each block
-- Reconstructs blocks by applying transforms to base versions
-- Integrates with restoration callbacks for missing data
-- Uses latches for thread-safe concurrent access
-
-#### `IRawStorage` backends
-`BlockStorage` persists through the `IRawStorage` interface, so the backing store is pluggable:
-
-- **In-memory** (`MemoryRawStorage`) — ships in this package; used for tests and ephemeral nodes.
-- **Filesystem** (`FileRawStorage`) — lives in the separate [`@optimystic/db-p2p-storage-fs`](../db-p2p-storage-fs) package; JSON files with atomic writes, organized per block:
-
-```typescript
-// Filesystem backend layout (@optimystic/db-p2p-storage-fs)
-{basePath}/
-├── {blockId}/
-│   ├── meta.json                # Block metadata and revision ranges
-│   ├── revs/{rev}.json          # Revision → ActionId mappings
-│   ├── pend/{actionId}.json     # Pending actions
-│   ├── actions/{actionId}.json  # Committed actions
-│   └── blocks/{actionId}.json   # Materialized blocks
-```
-
-- **Other backends** — SQLite (`-storage-ns`), LevelDB (`-storage-rn`), IndexedDB (`-storage-web`), each in its own package.
-
-## Integration Patterns
-
-### Relationship to `@optimystic/db-core`
-
-The `db-p2p` package provides concrete implementations of the core database abstractions:
-
-```typescript
-// Core provides interfaces and abstractions
-import { IRepo, IBlock, Transform, IBlockStorage } from '@optimystic/db-core';
-
-// P2P provides concrete implementations
-class StorageRepo implements IRepo { /* backend-agnostic versioned repo */ }
-class BlockStorage implements IBlockStorage { /* versioned block storage over IRawStorage */ }
-class RepoClient implements IRepo { /* network-transparent repo */ }
-class CoordinatorRepo implements IRepo { /* distributed consensus repo */ }
-```
-
-**Implementation Points:**
-- **Storage Layer**: Implements the core storage interfaces over a pluggable `IRawStorage` backend (in-memory here; filesystem in `@optimystic/db-p2p-storage-fs`)
-- **Network Layer**: Implements peer-to-peer communication using libp2p
-- **Consensus Layer**: Adds distributed consensus while maintaining core interfaces
-- **API Compatibility**: Same interfaces as core abstractions for seamless integration
-
-### Libp2p Integration
-
-The package integrates deeply with libp2p for networking:
-
-```typescript
-// Node creation with integrated services
-const node = await createLibp2pNode({
-  services: {
-    repo: repoService({ protocolPrefix: '/optimystic/<network>' }),
-    cluster: clusterService({ protocolPrefix: '/optimystic/<network>' })
-  }
-});
-
-// Key network integration — use the node's OWN key network, do not construct a second one.
-// `createLibp2pNode` returns an `OptimysticNode`, which declares this handle (and
-// `coordinatedRepo`, `storageRepo`, `blockChangeNotifier`, `reputation`, `peerPrivateKey`).
-// The attached instance carries the node's resolved cluster size and its network-namespaced
-// protocol prefix; a separately constructed one selects a different-width cohort and has the
-// "does this peer serve my network?" filter switched off.
-const keyNetwork = node.keyNetwork;
-```
-
-**Integration Features:**
-- **Protocol Management**: Registers custom protocols for repo and cluster operations
-- **Stream Handling**: Uses libp2p streams for reliable message transport
-- **Peer Discovery**: Integrates with libp2p DHT for peer discovery
-- **Security**: Leverages libp2p's cryptographic peer identity
-
-**Inbound stream authorization (optional).** The `repo`, `cluster`, `sync` and `block-transfer`
-protocols are open to any peer that can connect. An embedder whose database is private supplies one
-node-level, fail-closed predicate, consulted once per inbound stream before any decoding or execution:
-
-```typescript
-const node = await createLibp2pNode({
-  networkName: 'my-net',
-  bootstrapNodes: [],
-  // remotePeerId is the dialing peer's PeerId.toString(); only a literal `true` allows.
-  // false / throw / rejection / timeout all deny and abort the stream.
-  authorizeInboundStream: (remotePeerId, protocol) => memberSet.has(remotePeerId)
-});
-```
-
-Omitting it is the default and leaves behavior unchanged. See
-[internals](../../docs/internals.md) § Inbound Stream Authorization for the full contract.
-
-**Announcing a different address than you bind (optional).** A node behind a NAT, port forward,
-reverse proxy or DNS front binds one address but is reachable at another. `announceAddrs` advertises
-the reachable address *instead of* whatever the transports report; `appendAnnounceAddrs` advertises
-it *in addition to* them:
-
-```typescript
-const node = await createLibp2pNode({
-  networkName: 'my-net',
-  bootstrapNodes: ['...'],
-  listenAddrs: ['/ip4/0.0.0.0/tcp/4001'],       // what the process binds
-  announceAddrs: ['/dns4/mynode.example.com/tcp/4001']  // what peers are told
-});
-```
-
-`announceAddrs` replaces the advertised set **entirely** — observed and relayed addresses are
-dropped from it, and `appendAnnounceAddrs` is ignored while it is non-empty. Use
-`appendAnnounceAddrs` alone when the automatically discovered addresses are still worth advertising.
-Both are straight passthroughs to libp2p's `addresses.announce` / `addresses.appendAnnounce`; an
-empty array means "unset".
-
-## Usage Examples
-
-### Setting Up a Coordinator Node
-
-`createLibp2pNode` assembles the whole stack and **starts** the node: it builds the storage layer,
-the consensus coordinator and the key network from one resolved config, and hands them back on the
-returned `OptimysticNode`. Read them off the node — do not construct your own, or the two copies
-disagree about the same key's cohort.
-
-```typescript
-import { createLibp2pNode } from '@optimystic/db-p2p';
-import { FileRawStorage } from '@optimystic/db-p2p-storage-fs';
-
-// Create (and start) a libp2p node. The repo and cluster protocol services are registered by the
-// factory itself — there is no `services` option to pass them in.
-const node = await createLibp2pNode({
-  networkName: 'my-net',
-  bootstrapNodes: ['...'],
-  // In-memory when omitted; a raw-storage backend makes it durable
-  storage: new FileRawStorage('/var/lib/optimystic'),
-});
-
-// The handles the node already owns (see `OptimysticNodeAttachments`)
-const storageRepo = node.storageRepo;          // Local block storage
-const coordinatedRepo = node.coordinatedRepo;  // Cluster-consensus writes and reads
-const keyNetwork = node.keyNetwork;            // Peer/coordinator discovery
-
-// ... use them, then:
-await node.stop();
-```
-
-`createLibp2pNode` is all-or-nothing: the node is started early and then wired, so if any wiring step
-fails the factory stops the node before rejecting and surfaces the original error. A rejection
-therefore never leaves a running node behind — which matters because the caller gets no handle to
-stop one. Retrying on the same port is safe.
-
-Constructing a `StorageRepo`, `CoordinatorRepo` or `Libp2pKeyPeerNetwork` yourself is only for a
-host assembling a stack *without* `createLibp2pNode`. A standalone `CoordinatorRepo` or
-`Libp2pKeyPeerNetwork` must be told its cluster size; pass `DEFAULT_CLUSTER_SIZE` (exported from
-this package) to match what an unconfigured node resolves to.
-
-### External Client Operations
-
-```typescript
-// External clients connect to coordinator nodes
-const client = RepoClient.create(coordinatorPeerId, peerNetwork);
-
-// Operations work the same as core database interfaces
-const blocks = await client.get({
-  blockIds: ['block1', 'block2'],
-  context: { rev: 10 }
-});
-
-// But automatically coordinate across the cluster
-const pendResult = await client.pend({
-  actionId: 'tx1',
-  transforms: { block1: [/* operations */] },
-  rev: 11
-});
-
-const commitResult = await client.commit({
-  actionId: 'tx1',
-  blockIds: ['block1'],
-  rev: 11
-});
-```
-
-### How Coordination Works
-
-```mermaid
-sequenceDiagram
-    participant Client as External Client
-    participant RC as RepoClient
-    participant CR as CoordinatorRepo
-    participant CC as ClusterClient
-    participant CS as ClusterService
-    participant CM as ClusterMember
-    participant SR as StorageRepo
-    
-    Client->>RC: pend(transaction)
-    RC->>CR: pend(transaction)
-    CR->>CC: consensus request
-    CC->>CS: cluster protocol
-    CS->>CM: update(ClusterRecord)
-    CM->>CM: 2-phase commit
-    CM->>SR: execute operation
-    SR-->>CM: result
-    CM-->>CS: consensus result
-    CS-->>CC: response
-    CC-->>CR: consensus complete
-    CR-->>RC: transaction result
-    RC-->>Client: pend result
-```
-
-## Documentation
-
-For detailed information about specific components:
-
-- **[Storage System](./docs/storage.md)**: Versioned block storage and persistence
-- **[Repo Interface](./docs/repo.md)**: Distributed database operations
-- **[Cluster Consensus](./docs/cluster.md)**: 2-phase commit and distributed consensus
-
-## Block Restoration & Arachnode Integration
-
-The db-p2p package includes **dynamic Arachnode ring discovery** for automatic block restoration across storage tiers.
-
-### How Block Restoration Works
-
-When a node is missing a block or revision, the restoration system:
-
-1. **Determines storage rings** - Nodes self-select ring depth based on capacity
-2. **Discovers peers via FRET** - Ring membership propagates via existing neighbor exchange
-3. **Queries rings intelligently** - Tries transaction ring first, then inner storage rings
-4. **Filters by partition** - Only queries peers responsible for the block's keyspace
-
-### Ring Selection
-
-Nodes calculate their appropriate ring depth using:
-
-```
-ringDepth = ceil(-log2(available_capacity / estimated_demand))
-```
-
-**Examples:**
-- 100% coverage → Ring 0 (full keyspace)
-- 50% coverage → Ring 1 (2 partitions)  
-- 1% coverage → Ring 7 (128 partitions)
-
-### Architecture
-
-```
-FRET (Pure DHT)
-  - Generic metadata transport
-  - Peer discovery & routing
-  
-ArachnodeFretAdapter (Plugin Layer)
-  - Arachnode-specific semantics
-  - Ring discovery methods
-  
-Restoration Components
-  - RingSelector: Capacity-based ring selection
-  - RestorationCoordinator: Multi-ring queries
-  - StorageMonitor: Capacity tracking
-  - SyncService/Client: Block request protocol
-```
-
-### Configuration
-
-```typescript
-const node = await createLibp2pNode({
-    port: 9000,
-    networkName: 'mynet',
-    bootstrapNodes: ['...'],
-    clusterSize: 10,  // Cluster size for peer discovery
-    arachnode: {
-        enableRingZulu: true  // Default: enabled
-    }
-});
-```
-
-#### Solo / bootstrap / mobile nodes (no remote peers)
-
-A node can operate fully on its own — no bootstrap peers, no listen addresses, no
-connectivity to other peers. This is the common shape for a mobile app on first
-launch or for a local-only sanity test.
-
-```typescript
-const soloNode = await createLibp2pNode({
-    networkName: 'mynet',
-    bootstrapNodes: [],           // no bootstrap
-    listenAddrs: [],              // no incoming connections
-    transports: [webSockets()],   // transports still required
-    clusterSize: 1,
-});
-```
-
-In solo mode:
-
-- The node is its own coordinator. `CoordinatorRepo` short-circuits to local
-  storage when the cluster size is ≤ 1, so `pend`/`commit` do not require
-  cluster consensus and do not attempt to dial self.
-- Block restoration is skipped when the only discovered peer is self.
-  `RestorationCoordinator` will return `undefined` immediately rather than
-  attempt to dial self (which would hang on a node with no listen addrs).
-- If an operation fails for some other reason, `findCoordinator` surfaces a
-  distinguishable `FindCoordinatorError` with `code ===
-  FIND_COORDINATOR_ERROR_CODES.SELF_COORDINATION_EXHAUSTED` rather than the
-  generic "all candidates excluded". The aggregate error thrown by
-  `NetworkTransactor` preserves the ORIGINAL first-attempt cause so callers can
-  diagnose the real problem.
-
-Once remote peers become reachable, the node transitions out of solo mode
-automatically as FRET discovers them. Persisted network state (HWM, FRET
-table) carries across restarts when an `options.persistence` is supplied.
-
-#### Custom transports (including React Native)
-
-By default, `createLibp2pNode()` uses TCP + circuit-relay transport.
-
-To use non-default transports, pass `transports` (and typically `listenAddrs`):
-
-```typescript
-import { webSockets } from '@libp2p/websockets';
-import { circuitRelayTransport } from '@libp2p/circuit-relay-v2';
-import { createLibp2pNode } from '@optimystic/db-p2p';
-
-const node = await createLibp2pNode({
-    networkName: 'mynet',
-    bootstrapNodes: ['/dns4/relay.example.com/tcp/443/wss/p2p/12D3...'],
-    transports: [webSockets(), circuitRelayTransport()],
-    listenAddrs: [],  // client-only; no incoming connections
-});
-```
-
-#### React Native
-
-For React Native, import from `@optimystic/db-p2p/rn` instead of the root entrypoint.
-The `/rn` entrypoint does **not** import `@libp2p/tcp`, so Metro/Hermes won't try to
-bundle Node-only native modules. It requires `options.transports` explicitly:
-
-```typescript
-import { webSockets } from '@libp2p/websockets';
-import { circuitRelayTransport } from '@libp2p/circuit-relay-v2';
-import { createLibp2pNode } from '@optimystic/db-p2p/rn';
-
-const node = await createLibp2pNode({
-    networkName: 'mynet',
-    bootstrapNodes: ['/dns4/relay.example.com/tcp/443/wss/p2p/12D3...'],
-    transports: [webSockets(), circuitRelayTransport()],
-});
-```
-
-RN environments (Hermes) need polyfills for globals that libp2p and its
-dependencies expect. Install these early (e.g. in your app's entry file
-before any other imports).
-
-**Global polyfills** (patch `globalThis` before any library code):
-
-| API | Required by | Notes |
-|-----|-------------|-------|
-| `crypto.getRandomValues()` | @noble/hashes, @libp2p/crypto | RN 0.76+ New Architecture provides natively; fallback via e.g. `react-native-get-random-values` |
-| `crypto.subtle.digest()` | multiformats/hashes/sha2-browser | Async SHA-256/SHA-512 — implement via @noble/hashes |
-| `structuredClone()` | @optimystic/db-core | JSON round-trip is sufficient |
-| `Promise.withResolvers()` | @libp2p/utils, @chainsafe/libp2p-yamux, it-queue | ES2024 — simple shim |
-| `AbortSignal.prototype.throwIfAborted()` | libp2p, @libp2p/circuit-relay-v2, it-pushable | DOM spec addition — simple shim |
-| Timer `.ref()` / `.unref()` | @optimystic/db-p2p, undici | Wrap Hermes numeric timer IDs in objects with no-op `.ref()`/`.unref()` methods; patch `clearTimeout`/`clearInterval` to unwrap |
-| `Event`, `CustomEvent`, `EventTarget` | libp2p, @libp2p/interface | Custom shim or npm `event-target-polyfill` |
-| `Intl.PluralRules` | moat-maker | English-only ordinal/cardinal shim is sufficient |
-
-**Node.js built-in module shims** (via Metro `extraNodeModules` or bundler aliases):
-
-| Module | Required by | Recommended shim |
-|--------|-------------|------------------|
-| `os` / `node:os` | @libp2p/utils | Custom shim: `networkInterfaces()` → `{}`, `platform()` → `Platform.OS` |
-| `crypto` / `node:crypto` | multiformats/hashes/sha2 | Custom shim: `createHash()` via @noble/hashes |
-| `stream` / `node:stream` | libp2p | `readable-stream` (npm) |
-| `buffer` / `node:buffer` | libp2p, multiformats | `buffer` (npm) |
-
-**Built-in (no polyfill needed):**
-- `TextEncoder` — built-in to Hermes
-- `TextDecoder` — built-in to Expo SDK 52+ (UTF-8 only)
-- `BigInt` — built-in to Hermes since RN 0.70
-
-See the [Sereus reference-app-rn](https://github.com/gotchoices/sereus/tree/master/packages/reference-app-rn/polyfills) for working polyfill implementations.
-
-### Ring Transitions
-
-Nodes automatically transition between rings based on capacity thresholds:
-- **Move OUT** (to more granular ring) when > 85% capacity used
-- **Move IN** (to broader ring) when < 40% capacity used
-
-## Related Packages
-
-- **[@optimystic/db-core](../db-core)**: Core database interfaces and local operations
-- **[@optimystic/db-p2p-storage-fs](../db-p2p-storage-fs)**: Filesystem `IRawStorage` backend (Node)
-- **[@optimystic/db-p2p-storage-ns](../db-p2p-storage-ns)**: NativeScript SQLite storage backend
-- **[@optimystic/db-p2p-storage-rn](../db-p2p-storage-rn)**: React Native LevelDB storage backend
-- **[@optimystic/db-p2p-storage-web](../db-p2p-storage-web)**: Browser IndexedDB storage backend
-- **[@optimystic/db-quereus](../db-quereus)**: Query engine and data access patterns
-- **[p2p-fret](../fret)**: DHT implementation for peer discovery
-
-### Internal Architecture
-
-For developers and AI agents working on internals, see [Internals Guide](../../docs/internals.md) for:
-- Data flow diagrams (read/write/commit paths)
-- Mutation contracts (which functions mutate vs clone)
-- Key invariants and common pitfalls
-- Type glossary and debugging tips
+# Optimystic DB-P2P
+
+A distributed peer-to-peer database system that provides concrete implementations of the Optimystic database abstractions using pluggable storage backends and libp2p networking. This package transforms the interfaces and abstractions from `@optimystic/db-core` into a fully operational distributed database system.
+
+> **Storage is pluggable.** `db-p2p` owns the distributed layer (repo/cluster/coordination) and the storage *interfaces* (`IRawStorage`, `IBlockStorage`, `IKVStore`) plus an in-memory backend. Concrete persistent backends live in separate packages — filesystem persistence is [`@optimystic/db-p2p-storage-fs`](../db-p2p-storage-fs); see also `-storage-ns` (NativeScript/SQLite), `-storage-rn` (React Native/LevelDB), and `-storage-web` (IndexedDB).
+
+## Overview
+
+The `@optimystic/db-core` package provides abstractions and interfaces for database operations—immutable blocks, versioned transactions, repository interfaces, and collection data structures. However, it doesn't provide concrete implementations for storage or distribution. `db-p2p` provides concrete implementations of the core abstractions using:
+
+- **Versioned block storage** (`StorageRepo` / `BlockStorage`) layered over a pluggable `IRawStorage` backend — an in-memory backend ships here; filesystem persistence lives in `@optimystic/db-p2p-storage-fs`
+- **libp2p networking** for decentralized peer-to-peer communication
+- **Distributed consensus** using 2-phase commit protocols for consistency
+- **Fault-tolerant coordination** with automatic recovery and data restoration
+
+The result is a fully operational distributed database system that implements the interfaces defined in the core abstractions to provide a complete distributed database system.
+
+## Architecture Overview
+
+The system provides three distinct communication interfaces, each serving different roles in the distributed architecture:
+
+```mermaid
+graph TD
+    subgraph "External Client Process"
+        A[Application Code]
+        B[RepoClient]
+        A --> B
+    end
+    
+    subgraph "Coordinator Node Process<br/>(Orchestrates Transactions)"
+        C[RepoService]
+        D[CoordinatorRepo]
+        E[ClusterClient]
+        F[StorageRepo]
+        subgraph "Local Storage"
+            F1[BlockStorage]
+            F2[IRawStorage backend]
+            F3[Backend store]
+        end
+        C --> D
+        D --> E
+        D --> F
+        F --> F1
+        F1 --> F2
+        F2 --> F3
+    end
+    
+    subgraph "Cluster Peer 1 Process<br/>(Participates in Consensus)"
+        G1[ClusterService]
+        H1[ClusterMember]
+        I1[StorageRepo]
+        subgraph "Local Storage 1"
+            I1A[BlockStorage]
+            I1B[IRawStorage backend]
+            I1C[Backend store]
+        end
+        G1 --> H1
+        H1 --> I1
+        I1 --> I1A
+        I1A --> I1B
+        I1B --> I1C
+    end
+    
+    subgraph "Cluster Peer 2 Process<br/>(Participates in Consensus)"
+        G2[ClusterService]
+        H2[ClusterMember]
+        I2[StorageRepo]
+        subgraph "Local Storage 2"
+            I2A[BlockStorage]
+            I2B[IRawStorage backend]
+            I2C[Backend store]
+        end
+        G2 --> H2
+        H2 --> I2
+        I2 --> I2A
+        I2A --> I2B
+        I2B --> I2C
+    end
+    
+    subgraph "Cluster Peer N Process<br/>(Participates in Consensus)"
+        G3[ClusterService]
+        H3[ClusterMember]
+        I3[StorageRepo]
+        subgraph "Local Storage N"
+            I3A[BlockStorage]
+            I3B[IRawStorage backend]
+            I3C[Backend store]
+        end
+        G3 --> H3
+        H3 --> I3
+        I3 --> I3A
+        I3A --> I3B
+        I3B --> I3C
+    end
+    
+    %% Network communication
+    B -.->|"/optimystic/&lt;network&gt;/repo/1.0.0"| C
+    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G1
+    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G2
+    E -.->|"/optimystic/&lt;network&gt;/cluster/1.0.0"| G3
+```
+
+### Repo Layer: External Client Interface
+
+The repo layer provides the interface for external clients to communicate with the distributed database:
+
+- **RepoClient**: Allows external clients to connect to any coordinator node
+- **RepoService**: Handles incoming requests from external clients
+- **CoordinatorRepo**: Orchestrates distributed transactions by coordinating with cluster peers
+- **Network transparency**: Same `IRepo` interface whether local or distributed
+
+### Cluster Layer: Peer-to-Peer Coordination Interface
+
+The cluster layer provides the interface for coordinators to communicate with other peers in the cluster:
+
+- **ClusterClient**: Allows coordinators to send consensus requests to cluster peers
+- **ClusterService**: Handles incoming consensus requests from coordinators
+- **ClusterMember**: Implements 2-phase commit protocol for distributed consensus
+- **Byzantine fault tolerance**: Ensures consistency even with peer failures
+
+### Storage Layer: Persistent Data Implementation
+
+The storage layer implements the core database abstractions over a pluggable raw-storage backend:
+
+- **StorageRepo**: Implements the `IRepo` interface on top of `BlockStorage` — backend-agnostic
+- **BlockStorage**: Provides versioned block storage with conflict resolution, reading/writing through an injected `IRawStorage`
+- **`IRawStorage`**: The raw persistence interface. An in-memory backend ships in this package; the filesystem backend (`FileRawStorage`) lives in `@optimystic/db-p2p-storage-fs`
+- **Data restoration**: Pluggable restoration for missing data from network peers
+
+## Detailed Component Architecture
+
+### Repo Layer Components
+
+#### `RepoClient`
+Allows external clients to connect to coordinator nodes:
+
+```typescript
+class RepoClient extends ProtocolClient implements IRepo {
+  static create(peerId: PeerId, peerNetwork: IPeerNetwork): RepoClient
+  // Implements same IRepo interface as local storage
+}
+```
+
+**Key Features:**
+- Network-transparent database operations for external clients
+- Automatic protocol handling and message serialization
+- Error handling for network failures and timeouts
+- Connection pooling and optimization
+
+#### `RepoService`
+Handles incoming repository protocol messages from external clients:
+
+```typescript
+class RepoService implements Startable {
+  // Protocol: /optimystic/<network>/repo/1.0.0 (see docs/repo.md § Protocol id conventions)
+  // Transport: Length-prefixed JSON over libp2p streams
+  async start(): Promise<void>
+  async stop(): Promise<void>
+}
+```
+
+**Key Features:**
+- Registers and handles the repository protocol
+- Routes operations from external clients to coordinator implementation
+- Manages concurrent connections and stream processing
+- Provides comprehensive error handling and logging
+
+#### `CoordinatorRepo`
+Orchestrates distributed transactions by coordinating with cluster peers:
+
+```typescript
+class CoordinatorRepo implements IRepo {
+  constructor(
+    keyNetwork: IKeyNetwork,
+    createClusterClient: (peerId: PeerId) => ClusterClient,
+    storageRepo: IRepo
+  )
+}
+```
+
+**Key Features:**
+- Manages distributed transactions using cluster consensus
+- Integrates with key network for peer discovery
+- Uses cluster layer to coordinate with other peers
+- Maintains local storage directly while coordinating remote operations
+
+### Cluster Layer Components
+
+#### `ClusterClient`
+Allows coordinators to send consensus requests to cluster peers:
+
+```typescript
+class ClusterClient extends ProtocolClient implements ICluster {
+  async update(record: ClusterRecord): Promise<ClusterRecord>
+}
+```
+
+**Key Features:**
+- Network communication for consensus operations
+- Handles cluster record updates and responses
+- Manages timeouts and retries for consensus requests
+
+#### `ClusterService`
+Handles incoming consensus requests from coordinators:
+
+```typescript
+class ClusterService implements Startable {
+  // Protocol: /optimystic/<network>/cluster/1.0.0 (built from protocolPrefix)
+  // Handles ClusterRecord updates for consensus
+}
+```
+
+**Key Features:**
+- Registers and handles the cluster consensus protocol
+- Routes consensus requests to local cluster member
+- Manages concurrent consensus operations
+
+#### `ClusterMember`
+Implements 2-phase commit protocol for distributed consensus:
+
+```typescript
+class ClusterMember implements ICluster {
+  async update(record: ClusterRecord): Promise<ClusterRecord>
+  // Handles: Promise collection → Majority consensus → Commit execution
+}
+```
+
+**Key Features:**
+- Complete 2-phase commit protocol implementation
+- Conflict detection and resolution
+- Cryptographic signature verification
+- Automatic timeout and cleanup management
+- Uses storage layer to execute operations when consensus is reached
+
+### Storage Layer Components
+
+#### `StorageRepo`
+Implements the `IRepo` interface over `BlockStorage` — independent of any particular storage backend:
+
+```typescript
+class StorageRepo implements IRepo {
+  async get(blockGets: BlockGets): Promise<GetBlockResults>
+  async pend(request: PendRequest): Promise<PendResult>  
+  async commit(request: CommitRequest): Promise<CommitResult>
+  async cancel(actionRef: ActionBlocks): Promise<void>
+}
+```
+
+**Key Features:**
+- Concrete implementation of core database abstractions
+- Orchestrates transactions across multiple blocks
+- Handles revision conflicts and missing transaction detection
+- Provides atomic commit operations with proper locking
+
+#### `BlockStorage`
+Provides versioned block storage with conflict resolution, reading and writing through an injected `IRawStorage` backend:
+
+```typescript
+class BlockStorage implements IBlockStorage {
+  constructor(blockId: BlockId, storage: IRawStorage, /* … */)
+  async getBlock(rev?: number): Promise<{ block: IBlock, actionRev: ActionRev }>
+  async savePendingAction(actionId: ActionId, transform: Transform): Promise<void>
+  async promotePendingAction(actionId: ActionId): Promise<void>
+  async ensureRevision(rev: number): Promise<void>
+}
+```
+
+**Key Features:**
+- Maintains complete revision history for each block
+- Reconstructs blocks by applying transforms to base versions
+- Integrates with restoration callbacks for missing data
+- Uses latches for thread-safe concurrent access
+
+#### `IRawStorage` backends
+`BlockStorage` persists through the `IRawStorage` interface, so the backing store is pluggable:
+
+- **In-memory** (`MemoryRawStorage`) — ships in this package; used for tests and ephemeral nodes.
+- **Filesystem** (`FileRawStorage`) — lives in the separate [`@optimystic/db-p2p-storage-fs`](../db-p2p-storage-fs) package; JSON files with atomic writes, organized per block:
+
+```typescript
+// Filesystem backend layout (@optimystic/db-p2p-storage-fs)
+{basePath}/
+├── {blockId}/
+│   ├── meta.json                # Block metadata and revision ranges
+│   ├── revs/{rev}.json          # Revision → ActionId mappings
+│   ├── pend/{actionId}.json     # Pending actions
+│   ├── actions/{actionId}.json  # Committed actions
+│   └── blocks/{actionId}.json   # Materialized blocks
+```
+
+- **Other backends** — SQLite (`-storage-ns`), LevelDB (`-storage-rn`), IndexedDB (`-storage-web`), each in its own package.
+
+## Integration Patterns
+
+### Relationship to `@optimystic/db-core`
+
+The `db-p2p` package provides concrete implementations of the core database abstractions:
+
+```typescript
+// Core provides interfaces and abstractions
+import { IRepo, IBlock, Transform, IBlockStorage } from '@optimystic/db-core';
+
+// P2P provides concrete implementations
+class StorageRepo implements IRepo { /* backend-agnostic versioned repo */ }
+class BlockStorage implements IBlockStorage { /* versioned block storage over IRawStorage */ }
+class RepoClient implements IRepo { /* network-transparent repo */ }
+class CoordinatorRepo implements IRepo { /* distributed consensus repo */ }
+```
+
+**Implementation Points:**
+- **Storage Layer**: Implements the core storage interfaces over a pluggable `IRawStorage` backend (in-memory here; filesystem in `@optimystic/db-p2p-storage-fs`)
+- **Network Layer**: Implements peer-to-peer communication using libp2p
+- **Consensus Layer**: Adds distributed consensus while maintaining core interfaces
+- **API Compatibility**: Same interfaces as core abstractions for seamless integration
+
+### Libp2p Integration
+
+The package integrates deeply with libp2p for networking:
+
+```typescript
+// Node creation with integrated services
+const node = await createLibp2pNode({
+  services: {
+    repo: repoService({ protocolPrefix: '/optimystic/<network>' }),
+    cluster: clusterService({ protocolPrefix: '/optimystic/<network>' })
+  }
+});
+
+// Key network integration — use the node's OWN key network, do not construct a second one.
+// `createLibp2pNode` returns an `OptimysticNode`, which declares this handle (and
+// `coordinatedRepo`, `storageRepo`, `blockChangeNotifier`, `reputation`, `peerPrivateKey`).
+// The attached instance carries the node's resolved cluster size and its network-namespaced
+// protocol prefix; a separately constructed one selects a different-width cohort and has the
+// "does this peer serve my network?" filter switched off.
+const keyNetwork = node.keyNetwork;
+```
+
+**Integration Features:**
+- **Protocol Management**: Registers custom protocols for repo and cluster operations
+- **Stream Handling**: Uses libp2p streams for reliable message transport
+- **Peer Discovery**: Integrates with libp2p DHT for peer discovery
+- **Security**: Leverages libp2p's cryptographic peer identity
+
+**Inbound stream authorization (optional).** The `repo`, `cluster`, `sync` and `block-transfer`
+protocols are open to any peer that can connect. An embedder whose database is private supplies one
+node-level, fail-closed predicate, consulted once per inbound stream before any decoding or execution:
+
+```typescript
+const node = await createLibp2pNode({
+  networkName: 'my-net',
+  bootstrapNodes: [],
+  // remotePeerId is the dialing peer's PeerId.toString(); only a literal `true` allows.
+  // false / throw / rejection / timeout all deny and abort the stream.
+  authorizeInboundStream: (remotePeerId, protocol) => memberSet.has(remotePeerId)
+});
+```
+
+Omitting it is the default and leaves behavior unchanged. See
+[internals](../../docs/internals.md) § Inbound Stream Authorization for the full contract.
+
+**Announcing a different address than you bind (optional).** A node behind a NAT, port forward,
+reverse proxy or DNS front binds one address but is reachable at another. `announceAddrs` advertises
+the reachable address *instead of* whatever the transports report; `appendAnnounceAddrs` advertises
+it *in addition to* them:
+
+```typescript
+const node = await createLibp2pNode({
+  networkName: 'my-net',
+  bootstrapNodes: ['...'],
+  listenAddrs: ['/ip4/0.0.0.0/tcp/4001'],       // what the process binds
+  announceAddrs: ['/dns4/mynode.example.com/tcp/4001']  // what peers are told
+});
+```
+
+`announceAddrs` replaces the advertised set **entirely** — observed and relayed addresses are
+dropped from it, and `appendAnnounceAddrs` is ignored while it is non-empty. Use
+`appendAnnounceAddrs` alone when the automatically discovered addresses are still worth advertising.
+Both are straight passthroughs to libp2p's `addresses.announce` / `addresses.appendAnnounce`; an
+empty array means "unset".
+
+## Usage Examples
+
+### Setting Up a Coordinator Node
+
+`createLibp2pNode` assembles the whole stack and **starts** the node: it builds the storage layer,
+the consensus coordinator and the key network from one resolved config, and hands them back on the
+returned `OptimysticNode`. Read them off the node — do not construct your own, or the two copies
+disagree about the same key's cohort.
+
+```typescript
+import { createLibp2pNode } from '@optimystic/db-p2p';
+import { FileRawStorage } from '@optimystic/db-p2p-storage-fs';
+
+// Create (and start) a libp2p node. The repo and cluster protocol services are registered by the
+// factory itself — there is no `services` option to pass them in.
+const node = await createLibp2pNode({
+  networkName: 'my-net',
+  bootstrapNodes: ['...'],
+  // In-memory when omitted; a raw-storage backend makes it durable
+  storage: new FileRawStorage('/var/lib/optimystic'),
+});
+
+// The handles the node already owns (see `OptimysticNodeAttachments`)
+const storageRepo = node.storageRepo;          // Local block storage
+const coordinatedRepo = node.coordinatedRepo;  // Cluster-consensus writes and reads
+const keyNetwork = node.keyNetwork;            // Peer/coordinator discovery
+
+// ... use them, then:
+await node.stop();
+```
+
+`createLibp2pNode` is all-or-nothing: the node is started early and then wired, so if any wiring step
+fails the factory stops the node before rejecting and surfaces the original error. A rejection
+therefore never leaves a running node behind — which matters because the caller gets no handle to
+stop one. Retrying on the same port is safe.
+
+Constructing a `StorageRepo`, `CoordinatorRepo` or `Libp2pKeyPeerNetwork` yourself is only for a
+host assembling a stack *without* `createLibp2pNode`. A standalone `CoordinatorRepo` or
+`Libp2pKeyPeerNetwork` must be told its cluster size; pass `DEFAULT_CLUSTER_SIZE` (exported from
+this package) to match what an unconfigured node resolves to.
+
+### External Client Operations
+
+```typescript
+// External clients connect to coordinator nodes
+const client = RepoClient.create(coordinatorPeerId, peerNetwork);
+
+// Operations work the same as core database interfaces
+const blocks = await client.get({
+  blockIds: ['block1', 'block2'],
+  context: { rev: 10 }
+});
+
+// But automatically coordinate across the cluster
+const pendResult = await client.pend({
+  actionId: 'tx1',
+  transforms: { block1: [/* operations */] },
+  rev: 11
+});
+
+const commitResult = await client.commit({
+  actionId: 'tx1',
+  blockIds: ['block1'],
+  rev: 11
+});
+```
+
+### How Coordination Works
+
+```mermaid
+sequenceDiagram
+    participant Client as External Client
+    participant RC as RepoClient
+    participant CR as CoordinatorRepo
+    participant CC as ClusterClient
+    participant CS as ClusterService
+    participant CM as ClusterMember
+    participant SR as StorageRepo
+    
+    Client->>RC: pend(transaction)
+    RC->>CR: pend(transaction)
+    CR->>CC: consensus request
+    CC->>CS: cluster protocol
+    CS->>CM: update(ClusterRecord)
+    CM->>CM: 2-phase commit
+    CM->>SR: execute operation
+    SR-->>CM: result
+    CM-->>CS: consensus result
+    CS-->>CC: response
+    CC-->>CR: consensus complete
+    CR-->>RC: transaction result
+    RC-->>Client: pend result
+```
+
+## Documentation
+
+For detailed information about specific components:
+
+- **[Storage System](./docs/storage.md)**: Versioned block storage and persistence
+- **[Repo Interface](./docs/repo.md)**: Distributed database operations
+- **[Cluster Consensus](./docs/cluster.md)**: 2-phase commit and distributed consensus
+
+## Block Restoration & Arachnode Integration
+
+The db-p2p package includes **dynamic Arachnode ring discovery** for automatic block restoration across storage tiers.
+
+### How Block Restoration Works
+
+When a node is missing a block or revision, the restoration system:
+
+1. **Determines storage rings** - Nodes self-select ring depth based on capacity
+2. **Discovers peers via FRET** - Ring membership propagates via existing neighbor exchange
+3. **Queries rings intelligently** - Tries transaction ring first, then inner storage rings
+4. **Filters by partition** - Only queries peers responsible for the block's keyspace
+
+### Ring Selection
+
+Nodes calculate their appropriate ring depth using:
+
+```
+ringDepth = ceil(-log2(available_capacity / estimated_demand))
+```
+
+**Examples:**
+- 100% coverage → Ring 0 (full keyspace)
+- 50% coverage → Ring 1 (2 partitions)  
+- 1% coverage → Ring 7 (128 partitions)
+
+### Architecture
+
+```
+FRET (Pure DHT)
+  - Generic metadata transport
+  - Peer discovery & routing
+  
+ArachnodeFretAdapter (Plugin Layer)
+  - Arachnode-specific semantics
+  - Ring discovery methods
+  
+Restoration Components
+  - RingSelector: Capacity-based ring selection
+  - RestorationCoordinator: Multi-ring queries
+  - StorageMonitor: Capacity tracking
+  - SyncService/Client: Block request protocol
+```
+
+### Configuration
+
+```typescript
+const node = await createLibp2pNode({
+    port: 9000,
+    networkName: 'mynet',
+    bootstrapNodes: ['...'],
+    clusterSize: 10,  // Cluster size for peer discovery
+    arachnode: {
+        enableRingZulu: true  // Default: enabled
+    }
+});
+```
+
+#### Solo / bootstrap / mobile nodes (no remote peers)
+
+A node can operate fully on its own — no bootstrap peers, no listen addresses, no
+connectivity to other peers. This is the common shape for a mobile app on first
+launch or for a local-only sanity test.
+
+```typescript
+const soloNode = await createLibp2pNode({
+    networkName: 'mynet',
+    bootstrapNodes: [],           // no bootstrap
+    listenAddrs: [],              // no incoming connections
+    transports: [webSockets()],   // transports still required
+    clusterSize: 1,
+});
+```
+
+In solo mode:
+
+- The node is its own coordinator. `CoordinatorRepo` short-circuits to local
+  storage when the cluster size is ≤ 1, so `pend`/`commit` do not require
+  cluster consensus and do not attempt to dial self.
+- Block restoration is skipped when the only discovered peer is self.
+  `RestorationCoordinator` will return `undefined` immediately rather than
+  attempt to dial self (which would hang on a node with no listen addrs).
+- If an operation fails for some other reason, `findCoordinator` surfaces a
+  distinguishable `FindCoordinatorError` with `code ===
+  FIND_COORDINATOR_ERROR_CODES.SELF_COORDINATION_EXHAUSTED` rather than the
+  generic "all candidates excluded". The aggregate error thrown by
+  `NetworkTransactor` preserves the ORIGINAL first-attempt cause so callers can
+  diagnose the real problem.
+
+Once remote peers become reachable, the node transitions out of solo mode
+automatically as FRET discovers them. Persisted network state (HWM, FRET
+table) carries across restarts when an `options.persistence` is supplied.
+
+#### Custom transports (including React Native)
+
+By default, `createLibp2pNode()` uses TCP + circuit-relay transport.
+
+To use non-default transports, pass `transports` (and typically `listenAddrs`):
+
+```typescript
+import { webSockets } from '@libp2p/websockets';
+import { circuitRelayTransport } from '@libp2p/circuit-relay-v2';
+import { createLibp2pNode } from '@optimystic/db-p2p';
+
+const node = await createLibp2pNode({
+    networkName: 'mynet',
+    bootstrapNodes: ['/dns4/relay.example.com/tcp/443/wss/p2p/12D3...'],
+    transports: [webSockets(), circuitRelayTransport()],
+    listenAddrs: [],  // client-only; no incoming connections
+});
+```
+
+#### React Native
+
+For React Native, import from `@optimystic/db-p2p/rn` instead of the root entrypoint.
+The `/rn` entrypoint does **not** import `@libp2p/tcp`, so Metro/Hermes won't try to
+bundle Node-only native modules. It requires `options.transports` explicitly:
+
+```typescript
+import { webSockets } from '@libp2p/websockets';
+import { circuitRelayTransport } from '@libp2p/circuit-relay-v2';
+import { createLibp2pNode } from '@optimystic/db-p2p/rn';
+
+const node = await createLibp2pNode({
+    networkName: 'mynet',
+    bootstrapNodes: ['/dns4/relay.example.com/tcp/443/wss/p2p/12D3...'],
+    transports: [webSockets(), circuitRelayTransport()],
+});
+```
+
+RN environments (Hermes) need polyfills for globals that libp2p and its
+dependencies expect. Install these early (e.g. in your app's entry file
+before any other imports).
+
+**Global polyfills** (patch `globalThis` before any library code):
+
+| API | Required by | Notes |
+|-----|-------------|-------|
+| `crypto.getRandomValues()` | @noble/hashes, @libp2p/crypto | RN 0.76+ New Architecture provides natively; fallback via e.g. `react-native-get-random-values` |
+| `crypto.subtle.digest()` | multiformats/hashes/sha2-browser | Async SHA-256/SHA-512 — implement via @noble/hashes |
+| `structuredClone()` | @optimystic/db-core | JSON round-trip is sufficient |
+| `Promise.withResolvers()` | @libp2p/utils, @chainsafe/libp2p-yamux, it-queue | ES2024 — simple shim |
+| `AbortSignal.prototype.throwIfAborted()` | libp2p, @libp2p/circuit-relay-v2, it-pushable | DOM spec addition — simple shim |
+| Timer `.ref()` / `.unref()` | @optimystic/db-p2p, undici | Wrap Hermes numeric timer IDs in objects with no-op `.ref()`/`.unref()` methods; patch `clearTimeout`/`clearInterval` to unwrap |
+| `Event`, `CustomEvent`, `EventTarget` | libp2p, @libp2p/interface | Custom shim or npm `event-target-polyfill` |
+| `Intl.PluralRules` | moat-maker | English-only ordinal/cardinal shim is sufficient |
+
+**Node.js built-in module shims** (via Metro `extraNodeModules` or bundler aliases):
+
+| Module | Required by | Recommended shim |
+|--------|-------------|------------------|
+| `os` / `node:os` | @libp2p/utils | Custom shim: `networkInterfaces()` → `{}`, `platform()` → `Platform.OS` |
+| `crypto` / `node:crypto` | multiformats/hashes/sha2 | Custom shim: `createHash()` via @noble/hashes |
+| `stream` / `node:stream` | libp2p | `readable-stream` (npm) |
+| `buffer` / `node:buffer` | libp2p, multiformats | `buffer` (npm) |
+
+**Built-in (no polyfill needed):**
+- `TextEncoder` — built-in to Hermes
+- `TextDecoder` — built-in to Expo SDK 52+ (UTF-8 only)
+- `BigInt` — built-in to Hermes since RN 0.70
+
+See the [Sereus reference-app-rn](https://github.com/gotchoices/sereus/tree/master/packages/reference-app-rn/polyfills) for working polyfill implementations.
+
+### Ring Transitions
+
+Nodes automatically transition between rings based on capacity thresholds:
+- **Move OUT** (to more granular ring) when > 85% capacity used
+- **Move IN** (to broader ring) when < 40% capacity used
+
+## Related Packages
+
+- **[@optimystic/db-core](../db-core)**: Core database interfaces and local operations
+- **[@optimystic/db-p2p-storage-fs](../db-p2p-storage-fs)**: Filesystem `IRawStorage` backend (Node)
+- **[@optimystic/db-p2p-storage-ns](../db-p2p-storage-ns)**: NativeScript SQLite storage backend
+- **[@optimystic/db-p2p-storage-rn](../db-p2p-storage-rn)**: React Native LevelDB storage backend
+- **[@optimystic/db-p2p-storage-web](../db-p2p-storage-web)**: Browser IndexedDB storage backend
+- **[@optimystic/db-quereus](../db-quereus)**: Query engine and data access patterns
+- **[p2p-fret](../fret)**: DHT implementation for peer discovery
+
+### Internal Architecture
+
+For developers and AI agents working on internals, see [Internals Guide](../../docs/internals.md) for:
+- Data flow diagrams (read/write/commit paths)
+- Mutation contracts (which functions mutate vs clone)
+- Key invariants and common pitfalls
+- Type glossary and debugging tips