DST Task: vac:dst:status:2025q1-status-go-evaluation:subscription-performance

Subscription performance - Chat protocol benchmarks link

Deployment:

Setup 1 (using discV5BootstrapNodes/wakuNodes and base image):

  1. Deploy 1 service node A that will act as bootstrap.

  2. Deploy 1 service node B that will act as store.

    1. It will use A as bootstrap node.
  3. Deploy 4 relay nodes (Group C)

  4. Deploy 5 light nodes (Group D)

    Looks like C are not sending/receiving messages between themselves, but the service node is forwarding to 4 other nodes.

  5. In group C:

    1. Initialize with :3333/statusgo/InitializeApplication
      • Payload:
    2. Create accounts with :3333/statusgo/CreateAccountAndLogin
      • Payload:
    3. Start core services with :3333/statusgo/CallRPC
      • Messenger payload:
      • Wallet payload:
    4. Create community with :3333/statusgo/CallRPC
      1. Done on the first one (index 0).
      • Payload:
    5. Make other nodes in C join community previously created with :3333/statusgo/CallRPC
      • Payload:
    6. Accept join requests with :3333/statusgo/CallRPC in the node that created the community (index 0)
      1. Sometimes we obtain the following error, but doing another retry makes the request to work: 'error': {'code': -32000, 'message': 'sql: no rows in result set'}
      • Payload
  6. In group D:

    1. We follow the same steps that in point 5, but in step b, we change "wakuV2LightClient": False to "wakuV2LightClient": True

      When we reach step f, we obtain the following error:

      'error': {'code': -32000, 'message': 'sql: no rows in result set'}

  7. First node in group C (index 0) starts publishing messages with :3333/statusgo/CallRPC

Behaviour:

When using the base image, either setting up the ENR in wakuNodes or discV5BootstrapNodes resolves in the same behaviour. The light nodes cannot join the community.

When using other version the in the fleet configuration, when the other nodes in group C are trying to join the community, we obtain:

{'code': -32000, 'message': 'store node is not available'}