deploy: 2e56d32b52

docs/protocol/channels-protocol.html

@@ -918,13 +918,13 @@ window.addEventListener('click',(e)=>{
 <p>When a relay receives an invitation to serve a channel, it validates the channel and creates its own relay link. This flow is currently part of channel creation; adding relays to an existing channel is planned but not yet implemented.</p>
 <ol>
 <li>
-<p>Owner sends <code>x.grp.relay.inv</code> to the relay's contact address. This message includes the relay's member ID and role, the owner's profile, and the channel's short link.</p>
+<p>Owner sends <code>x.grp.relay.inv</code> to the relay's contact address. This message includes the relay's member ID and role, the owner's profile, the channel's short link, the channel's public group ID, and the owner's member key. The message is signed with the owner's member key over the public group ID and the owner's member ID.</p>
 </li>
 <li>
-<p>Relay receives the invitation and creates a relay request record. A relay request worker processes it asynchronously.</p>
+<p>Relay receives the invitation and creates a relay request record. From chat protocol version 22 of the owner, an invitation without a valid signature is ignored. The owner's badge is verified under the public group ID, the owner's member ID and the owner's member key from a signed invitation. A relay request worker processes it asynchronously.</p>
 </li>
 <li>
-<p>The worker retrieves the channel's link data from the SMP server, extracts and validates the channel profile and owner authorization.</p>
+<p>The worker retrieves the channel's link data from the SMP server, extracts and validates the channel profile and owner authorization. The request fails when the link's entity ID differs from the public group ID in the invitation, or when the owner's key in the link data differs from the owner's member key in the invitation.</p>
 </li>
 <li>
 <p>The relay creates its own contact address link (the relay link) with the channel's entity ID in the immutable fixed data.</p>