The tracker
Open Problems
Problems in the read path that are in our scope, described once and properly. Not a discussion queue, and not a sprint board: things that are wrong, whether or not we are the ones who will fix them.
Execution and consensus nodes speak RLPx, libp2p TCP, and QUIC. The web platform offers none of these, so a browser can't open a single native connection.
ENRs describe TCP and UDP endpoints a browser can't use. No standard field carries an HTTPS or WebTransport endpoint, or the certificate hashes needed to dial one.
discv5 runs over UDP, and browsers can't send UDP. The discovery layer is unreachable from the platform most readers run on.
Candidate directionsENR trees over DNS-over-HTTPS
Many full nodes sit behind home routers, outbound only and unreachable from outside. They read the network but can't serve it.
A reader who wants an alternative endpoint has no protocol to query. Alternatives arrive out of band, through curated lists and social consensus.
Serving browsers over HTTPS or WebSocket requires a CA-issued certificate, which requires a domain and renewal automation. That selects for professional operators over hobbyist nodes.
Curated by the team. If something belongs here, or something here is wrong, get in touch.