2026-06-01 Messaging Weekly

Highlights §

• Logos Delivery:
• Logos Chat:
• Logos Integrations:
• Status:
  • Kicked-off the integration of logos-delivery into Status. Required migrations will begin in 2.38.

Logos Delivery §

Messaging API — General Availability §

• [Deliverable] Provide Store API access for Status needs
  • next:
    • Redesign API to expose as layers

Reliable Channel API — Developer Preview §

• [Deliverable] Implement Reliable Channel API
  • achieved:
    • start basic reliable channel folder
  • next:
    • Connect delivery persistency with SDS persistency connector
    • introduce SDS persistency glue

RLN for lightpush §

• [Deliverable] Improve RLN UX by reducing contract interactions
  • next:
    • Extend contract to reduce number of Web3 RPC calls

Logos Chat §

Chat — Group Conversations §

• [Deliverable] Add Group Chat

  • achieved:
    • sender Identity for missing messages https://github.com/logos-messaging/libchat/pull/120

• Implement contact discovery

  • achieved:
    • KeyPackage registry https://github.com/logos-messaging/libchat/pull/124.

Status §

Integrate logos-delivery in Status §

• [Deliverable] Integrate Messaging API in status-go
  • achieved:
    • Start migrations required for integration of logos-delivery (https://github.com/status-im/status-go/pull/7495, https://github.com/status-im/status-go/pull/7500)
    • Implemented cross-version automated tests
  • next:
    • Remove envelopes monitoring from status-go
    • Relocate RFC26 implmementation to status-go
    • Remove publish rate limiting from status-go

Maintenance §

• achieved:
  • agentify repo
  • Remove makefile target update
• next:
  • Lift Messaging API out of Waku into its own layer
  • Docs list config keys that the node does not accept
• blocked:
  • Improve config