Docs update concerning consensus
This commit is contained in:
@@ -87,8 +87,8 @@ P2NS P2P Proxy is a Node.js-based application designed to bridge peer-to-peer (P
|
||||
|
||||
### 2. Domain Resolution
|
||||
|
||||
- Domains are resolved to content hashes using a voting mechanism stored in `dnsPass`.
|
||||
- The system retrieves claims (`claim:<domain>:<claimant>`) and votes (`vote:<domain>:<claimant>:<voter>`) to determine the most-voted hash for a domain.
|
||||
- Domains are resolved via the same consensus sidecar read path as the main P2NS node (`getConsensusState` through the shared core modules).
|
||||
- Claims and votes are stored in `dnsPass` (Autopass KV); resolution reads the replicated Autobase apply view, not a local KV scan.
|
||||
- Domain resolution is cached for performance (TTL configurable via `CACHE_TTL`).
|
||||
- Auto-voting occurs at debounced intervals (configurable via `AUTO_VOTE_DEBOUNCE`) to maintain consensus.
|
||||
|
||||
@@ -117,7 +117,7 @@ P2NS P2P Proxy is a Node.js-based application designed to bridge peer-to-peer (P
|
||||
The proxy server is a standalone component that:
|
||||
- Connects to the same P2NS network as the main system
|
||||
- Uses the same Hyperswarm topic and Corestore structure
|
||||
- Resolves domains using the same consensus mechanism
|
||||
- Resolves domains using the same Autobase consensus sidecar as the main P2NS system (no standalone KV-scan fallback)
|
||||
- Can run independently or alongside the main P2NS instance
|
||||
- Does not require the main P2NS system to be running
|
||||
|
||||
|
||||
Reference in New Issue
Block a user