hubs
/hubs1783
A place to discuss running Farcaster hubs. To run your own hub go to thehubble.xyz
I'm writing a script to map hubs.
When I call GetCurrentPeers() the list returned will have some duplicate entries for the same gossip IP. For example, 46.175.223.29 will be reported two times, one as 1.15.5 and one as as 1.15.4, with two different timestamps.
What's the explanation? How do I interpret these entities?
When I call GetCurrentPeers() the list returned will have some duplicate entries for the same gossip IP. For example, 46.175.223.29 will be reported two times, one as 1.15.5 and one as as 1.15.4, with two different timestamps.
What's the explanation? How do I interpret these entities?
We have been using our hub for reads, and started testing writes today.
Suddenly all incoming peer connections dropped. Any Insights why?
CC: @v @horsefacts.eth
Suddenly all incoming peer connections dropped. Any Insights why?
CC: @v @horsefacts.eth
In the last few days, I started getting emails from Infura that the API key used by my hub is reaching the free quota. Has something changed? Has the network reached a size that keeping track of OnChainEvents requires more than the free quota offered by Infura?
Hub running in a GCP VM
fyi minimum of 200GB for hubs now just found out
gm seems to be a spike in unwritten messages from warpcast to hubs
Please upgrade Hubble to 1.14.4 which implements storage changes defined in https://github.com/farcasterxyz/protocol/discussions/191
We'll min version on Monday at the latest so all hubs will be ready for Aug 28 when storage units were originally scheduled to expire.
If you are manually calculating storage, you'll need to update your logic. You may find the new helper functions implemented in the hub-nodejs package useful https://github.com/farcasterxyz/hub-monorepo/blob/main/packages/core/src/limits.ts
We'll min version on Monday at the latest so all hubs will be ready for Aug 28 when storage units were originally scheduled to expire.
If you are manually calculating storage, you'll need to update your logic. You may find the new helper functions implemented in the hub-nodejs package useful https://github.com/farcasterxyz/hub-monorepo/blob/main/packages/core/src/limits.ts
Seeing a set up unpublished messages in the Warpcast to hub side of things
having trouble accessing gRPC service of a hub deployed to ecs via terraform. http api is fine. 100% my configuration issue, but wondering if anyone has insights.
Hub message disruption today was caused by our hub losing gossip connectivity to all other hubs (unclear why exactly due to a logging bug). It was unable to regain connection due a bad interaction with a libp2p upgrade.
Released 1.14.2 with a fix.
Released 1.14.2 with a fix.
Run a Farcaster Hub - without worrying about RPC endpoints!
Thanks to Allnodes for providing free public RPCs!(https://ethereum.publicnode.com/)
Thanks to Allnodes for providing free public RPCs!(https://ethereum.publicnode.com/)
perf metrics on hubble's grafana from the last 12 hours. Anyone else saw degraded performance on their hubs too? we upgraded to 1.14 yesterday.
Anyone else still having problems synchronizing messages sent via the node after the update?
Hubble 1.14 is out. It includes a bunch of fixes around follows (consistency issues and large compaction events breaking event streams).
If you are using shuttle, make sure you’re on the latest version before upgrading hubs, there’s a breaking api change for events.
If you are using shuttle, make sure you’re on the latest version before upgrading hubs, there’s a breaking api change for events.
I think the no rewards fix is working!
We now have 58% of hubs on the latest
We went from 13k+ hubs last few weeks to 8921 hubs today
We now have 58% of hubs on the latest
We went from 13k+ hubs last few weeks to 8921 hubs today
what's the goal with hub storage requirements?
there a way to run a "light" hub that discards old storage?
(i mainly run my node to be able to submit new posts to the protocol through it.)
there a way to run a "light" hub that discards old storage?
(i mainly run my node to be able to submit new posts to the protocol through it.)
Closing the loop: Hub is back up and running now.
Hey all, I'm curious about current hub network throughput. How many messages per second are being written to hubs?
I'm looking at https://status.warpcast.com/ - How does one read "Messages Written" to get a per second? If it's per 5 min interval is it just X/5/60, so for a height of 3000, it's 3000/5/60 = 10 messages/s? (I understand this is only Warpcast incoming messages, not accounting for other clients.) I'd love to get an overall message throughput metric.
Thanks in advance.
I'm looking at https://status.warpcast.com/ - How does one read "Messages Written" to get a per second? If it's per 5 min interval is it just X/5/60, so for a height of 3000, it's 3000/5/60 = 10 messages/s? (I understand this is only Warpcast incoming messages, not accounting for other clients.) I'd love to get an overall message throughput metric.
Thanks in advance.
Seems like it. Here is the response I got from Alchemy.
how does one get to the flow where Hubble asks for RPCs for an already existing installation? Or what files do I edit with new ones?
What is the alternative to alchemy rpcs? Anyone has recommendations.