BREAKING: Native p2ns.core RPC — invite.deliver, remove legacy invite channel
Replace RPC-to-string adapters and processCoreRequestMessage (~470 lines) with
typed handlers in core-swarm-handlers.js. Autopass invite wire now uses
invite.deliver RPC only; p2ns.core-invite protomux channel is removed.
- Add core-rpc-contract.js (METHODS, INVITE_STATUS) and core-swarm-handlers.js
with shared processInviteWire for deliver, relay, and pairing
- core-rpc.js: deliverInviteWire via invite.deliver; invite.request returns
{ status, reason, inviteId }; invite.ack carries optional inviteId
- p2ns.js: register native handlers; slim p2ns.core-request (lifecycle only);
proactive invite ack tracks inviteId; fix missing invite.queued handler
- proxy-server: channel-manager + shared handlers (no p2ns.core-invite strings)
- Tests: core-swarm-handlers.test.js, core-invite-rpc-integration.js; extend test:core-rpc
- Docs: PLUGIN_SDK RPC table; consensus.removeDomain in longform/RESTAPI/glossary
This commit is contained in:
+1
-1
@@ -47,7 +47,7 @@ The principle that only the peer that created a claim can modify or remove it. O
|
||||
When removing a domain where you have a claim but aren't the resolved claimant, only your own claim and votes are removed. A `removeConflictDomainClaim:` notification is broadcast to other peers, who update their consensus state but preserve their own claims.
|
||||
|
||||
### Resolved Claimant Removal
|
||||
When removing a domain where you are the resolved claimant, all claims and votes for the domain are removed. A `remove_domain:` message is broadcast to trigger other peers to clean up their own claims as well.
|
||||
When removing a domain where you are the resolved claimant, all claims and votes for the domain are removed. A `consensus.removeDomain` RPC event is broadcast to trigger other peers to clean up their own claims as well.
|
||||
|
||||
### Hybrid DNS
|
||||
P2NS's approach to DNS resolution that combines P2P domain resolution with fallback to public DNS servers. Local DNS records take priority, followed by P2P consensus, then public DNS.
|
||||
|
||||
Reference in New Issue
Block a user