BREAKING: All nodes must upgrade together. Legacy p2ns.core-request string messages are rejected; invite/consensus control plane uses protomux-rpc (invite.request, invite.ack, invite.relay*, consensus.*). Shared Corestore namespaces are the default for plugin DBs and drives; USE_SHARED_CORESTORE_NAMESPACES=false is debug-only. Admin plugin actions with params are validated before run. EXPERIMENTAL: End-to-end RPC invite path reuses existing handlers via adapters; invite wire still ships on the invite channel. Multi-peer invite/relay integration tests are not in CI yet (core-rpc-smoke only). SDK & channels: - channel-rpc.js, sdk.channels.rpc (register/request/event) - core-rpc.js for p2ns.core; action-params + plugin route validation - sdk.db.getCore/reopen, sdk.state.getPeerChannelSnapshot, sdk.metrics.getHolepunchStats (schema v1) Runtime: - p2ns.js: RPC-first core invite/consensus; Hyperswarm firewall/reconnect - channel-manager: required protomux-rpc per peer - db-shared-namespace-migration; drive-manager shared namespaces - proxy-server: invite.request RPC for joiners Plugins: file.drop, global.profile, peer.directory, domain.consensus, peer.visualize, example.plugin (RPC demo); peer.directory UI polish Also: CI/smoke scripts, diagnostics hardening, plugin config schema validation, admin action param modal, docs/RFCS, package-lock + engines.node >= 18
1.1 KiB
1.1 KiB
RFC 0002: Service Discovery Modernization
Status
Draft
Problem
Service subscription and discovery rely on JSON-based state and ad-hoc synchronization, which makes distributed service indexing harder to evolve.
Proposal
Evaluate Autobase discovery patterns for dynamic service registration and subscription updates, while preserving current subscription behavior.
Scope
- Define canonical service record shape (domain, serviceName, protocol, port, metadata).
- Add optional replicated discovery index.
- Add compatibility adapters for existing subscription files.
Non-Goals
- Removing current subscription files immediately.
- Breaking existing admin workflows.
Migration Plan
- Introduce read-only discovery index generation.
- Expose dual-source view in admin diagnostics.
- Enable optional write-through to discovery index.
- Phase out file-backed writes only after stable parity.
Risks
- Duplicate source-of-truth during transition.
- Peer compatibility concerns across mixed versions.
Rollback
Disable discovery-index write/read toggles and continue file-backed behavior only.