Skip to content

Devnet-4: clients not respecting configured subnet subscription/publish topology #697

@ch4r10t33r

Description

@ch4r10t33r

Summary

When running a devnet with multiple subnets, each client must subscribe and publish to the subnet it is configured to be a part of. Currently this is not being adhered to across most clients in devnet-4.

Quick analysis of the last ~60 min logs across all clients (16 nodes).

Network is configured for 2 subnets (0 and 1), but behavior is inconsistent across clients.


Findings by client

zeam

ream (0 / 1)

  • Bug: reads committee_count = 1
  • Both nodes subscribe only to subnet 0
  • ream_1 is on wrong subnet entirely

grandine (0 / 1)

  • Both nodes subscribe only to subnet 0
  • grandine_1 should be on subnet 1 but is not

gean (0 / 1)

  • Same issue as grandine
  • subnet 1 node incorrectly subscribed to subnet 0

nlean (0 / 1)

  • Same pattern
  • subnet partitioning not respected

qlean (0 / 1)

  • No explicit subscription logs
  • Likely correct for subnet 0 traffic
  • Cannot confirm subnet 1 correctness

ethlambda (0 / 1)

  • ethlambda_0 is over-subscribed (joins subnet 0 + 1)
  • ethlambda_1 subscribes to subnet 0 instead of subnet 1

lantern (0 / 1)

  • Both nodes subscribe only to subnet 1
  • Missing subnet 0 entirely
  • Effectively deaf to actual network traffic

Global publishing behavior

  • All observed attestations are on subnet 0
  • No evidence of subnet 1 publishing traffic
  • Suggests most clients compute publish topic incorrectly or default to subnet 0

Overall issue

  1. Several read incorrect committee_count (treating it as 1)
  2. One client (lantern) is flipped entirely to subnet 1
  3. One client (ethlambda_0) is over-subscribed
  4. Subnet 1 is effectively unused in practice

Net result

  • Subnet isolation is broken
  • Traffic is collapsed into subnet 0
  • Subnet 1 exists only in subscription state, not in actual message flow

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions