Conversation Token

Status: ⚠️ Future/Planned Feature

This token represents a group conversation (group chat) between multiple participants.

The conversation token must contain a content (c) field. For other constraints see the Action Tokens.

Note: For 1-to-1 direct messaging, see Message Token (MSG), which is currently implemented. CONV is planned for future implementation.

Content-Addressing

This token will be content-addressed using SHA-256:

• The entire JWT token (header + payload + signature) is hashed
• Action ID format: a1~{base64_hash}
• See Content-Addressing & Merkle Trees for details

Example

• CONV: @alice.cloudillo.net –> @somegroup.cloudillo.net “Let’s talk about this!”
  • ACK: @somegroup.cloudillo.net
  • JOIN: @alice.cloudillo.net
  • INV: –> @bob.cloudillo.net “Come on, let’s talk about this!”
  • INV: –> @charlie.cloudillo.net “Come on, let’s talk about this!”
  • JOIN: @bob.cloudillo.net
  • JOIN: @charlie.cloudillo.net
  • MSG: @alice.cloudillo.net “Hi!”
  • MSG: @bob.cloudillo.net “Hi!”
    • REACT:LIKE @alice.cloudillo.net
  • MSG: @charlie.cloudillo.net “Hi!”
  • JOIN:DEL: @alice.cloudillo.net