Runtime.NativePeerEndpoint

---- edges ---- A participant's sessions are its incident edges, in ascending peer order. Each edge has one IPv4 address. The lower role of an edge binds and listens on it; the higher role connects to it. Every edge owns a listener slot and a connection slot, so a peer's descriptor is a static slot, never a runtime lookup, and the protocol layer can name it by peer role. Establishment order: copy every address, bind and listen on every edge to a higher peer, announce those ports (two bytes each, big-endian, edge order), then establish edges in order: connect to each lower peer, accept each higher peer and close that listener. Launching participants in role order, each after the previous announced, therefore never connects to an absent listener, and no participant accepts before it has finished its own connects. A star (role 0 listens for every other role) and a two-role pair are instances; with one edge this is exactly the earlier two-role setup. Fixed membership: the addresses are compiled in, and a missing or late peer exhausts the bounded accept/connect budgets and aborts.

35field unrestricted nativePeerEdgeAddress : Bytes