Content
@
0 reply
0 recast
0 reaction
Tim Mustafin
@mustafin.eth
I actually spend some time on this today. My idea is that majority of hubs are not "fake" but sybil farmers. So, most of them wouldn't know/care about well-connectivity and just run 10-100s of them via automation. My idea is to build something like ethernodes.org, collect enough of peers and run analytics: 1. In-sync status 2. Uptime/Availability. I already noticed some peers struggle to reply for heavy queries Anything else?
1 reply
2 recasts
9 reactions
Tim Mustafin
@mustafin.eth
The biggest problem so far is inconsistency between peer APIs: gRPC API returns useful data about messages/sync status and most of nodes would keep it open, but it has only peerID and not IP address. JSON API has IP addresses, but doesn't have peerID and not reliable as many(?) hubs will have it closed. I'm working on a small patch for JSON RPC to expose PeerID there, once my local hub starts I will test it.
2 replies
0 recast
1 reaction
Wasif Iqbal
@wazzymandias.eth
The bootstrap peers have DNS names: https://github.com/farcasterxyz/hub-monorepo/blob/eacf29c98cdc81fcb614a8e7ae4dbedf889f15da/apps/hubble/src/bootstrapPeers.mainnet.ts#L2-L7 We can query their gRPC get info endpoints to yield associated Peer IDs For other hubs, with gRPC you can invoke peers API to get the list of IP addresses, and then for each IP address you can query the info API That way you get IP<->Peer ID mapping. Agreed it'd be useful to add Peer ID to APIs as well
1 reply
0 recast
2 reactions
Tim Mustafin
@mustafin.eth
> with gRPC you can invoke peers API to get the list of IP addresses, and then for each IP address you can query the info API I don't see IP address in gRPC definition of SyncStatus (part of SyncStatusResponse) and neither i get it in the response. https://github.com/farcasterxyz/hub-monorepo/blob/eacf29c98cdc81fcb614a8e7ae4dbedf889f15da/protobufs/schemas/request_response.proto#L54 Am I missing something?
2 replies
0 recast
0 reaction
