Resources Required:

  • 1 Delivery engineer (50% of work)
  • 1 Status engineer (50% of work)

Status currently has partial Logos Delivery (nwaku) integration in relay mode, with significant issues. The integration plan has been agreed:

  1. Remove nwaku CI jobs — stop maintaining duplicated CI for go-waku and nwaku
  2. Remove existing nwaku integration from status-go
  3. Wait for Messaging API to be integration-ready
  4. Integrate Messaging API in status-go — full switch to Logos Delivery, drop go-waku dependency
  5. Remove existing peer management from status-go — peer management is encapsulated in Logos Delivery Messaging API

Work is split 50/50 between Delivery team and Status team. Delivery team provides the library and Go bindings; Status team adapts status-go.

Risks

Risk(Accept, Own, Mitigation)
Go bindings for C librariesstatus-go needs Go bindings for Logos Delivery C-bindings. Extra development work.
Messaging API readinessIntegration cannot begin until Messaging API is stable enough. Track readiness closely.
DST blocked on discoveryDST testing of Logos Delivery in Status is blocked by a discovery issue. Needs resolution before meaningful benchmarking.

Deliverables

Remove existing nwaku integration

Owner: Delivery Team + Status Core

  • Remove nwaku CI jobs from status-go (no more duplicated jobs)
  • Remove existing nwaku relay integration code from status-go
  • Status continues with go-waku only until Messaging API is ready

Integrate Messaging API in status-go

Owner: Delivery Team (library + Go bindings) + Status Core (status-go adaptation)

  • Provide Go bindings for Logos Delivery Messaging API (via C-bindings)
  • Replace go-waku usage in status-go with Messaging API (send, health, subscribe)
  • Drop go-waku dependency entirely
  • Remove existing peer management from status-go — Messaging API handles this internally
  • Single implementation path in CI