Waku Scaling

vac:dst:waku:2025q4-waku-scaling

Description §

We will use realistic Waku node experiments to evaluate and improve Waku’s scalability by conducting performance measurements across its key components and tasks. These efforts contains supporting on-chain RLN memberships, strengthening the foundations for private chats, optimize browser bootstrapping for improved responsiveness, integrate nwaku in Status Desktop for seamless relay functionality, and implement the SDS protocol for group messaging reliability and recovery.

Task list §

Hardening and Scaling Foundations for Private Chats §

Note: This needs more input from project

Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:private-chats-hardening
• owner: TBD
• status: not started
• start-date: 2025/10/01
• end-date: 2025/12/31

Description §

To have: Vac-DST: status-backend benchmarks

Schedule note: Dates reflect quarter bounds; update when actual timing is known.

Deliverables §

• Code:
• Report:

Optimise Browser Bootstrapping §

Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:optimise-browser-bootstrapping
• owner: Pearson
• status: in progress (50%)
• start-date: 2025/10/15
• end-date: 2025/10/31

Description §

Using js-waku, prove that:

• From an operating state, a node can resume transmitting messages within 1 second after disconnection; in a network with 1 bootstrap node, 100 service nodes and 500 browser nodes.

• From a cold start, a node can start transmitting messages within 5 seconds; in a network with 1 bootstrap node, 100 service nodes and 500 browser nodes.

Schedule note: Dates reflect quarter bounds; update when actual timing is known.

Deliverables §

• Code:
• Report:

Integrate nwaku in Status Desktop, relay mode only §

Note: This needs more input from project

Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:nwaku-in-status-desktop
• owner: TBD
• status: not started
• start-date: 2025/10/01
• end-date: 2025/12/31

Description §

Waku estimated date of completion: 30 June

Vac-DST to complete go-waku-based benchmark works and proceed with nwaku-based vs go-waku-based status-backend comparisons.

Schedule note: Dates reflect quarter bounds; update when actual timing is known.

Deliverables §

• Code:
• Report:

SDS protocol in Status - basic integration §

Note: This needs more input from project

Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:sds-integration
• owner: TBD
• status: not started
• start-date: 2025/10/01
• end-date: 2025/12/31

Description §

Waku estimated date of completion: 31 Aug

Prove that:

• When sending a message in a group, the publisher can ensure the message was received by at least one recipient within S seconds

• When receiving messages in a group, the receiver can detect 90% of missed messages within 3*S seconds

Schedule note: Dates reflect quarter bounds; update when actual timing is known.

Deliverables §

• Code:
• Report:

SDS protocol in Status - basic recovery §

Note: This needs more input from project

Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:sds-recovery
• owner: TBD
• status: not started
• start-date: 2025/10/01
• end-date: 2025/12/31

Description §

Waku estimated date of completion: 31 Aug 2025

Prove that:

• When receiving messages in group, the receiver can
• reach eventual consistency within 6*S seconds

Schedule note: Dates reflect quarter bounds; update when actual timing is known.

Deliverables §

• Code:
• Report:

TWN supports RLN onchain tree and deposits, existing memberships only §

Note: Moved from previous quarter

Link to Waku FURPS Link to Waku FURPS

• fully qualified name: vac:dst:waku:2025q4-waku-scaling:TWN-supports-RLN-tree
• owner: Alberto
• status: in progress (90%)
• start-date: 2025/10/06
• end-date: 2025/10/24

Description §

Prove that a new node setup with an RLN membership can be ready to verify RLN proof within 5s, no matter the size of the tree.

Deliverables §

• Code:
• Report: