Sanjay pfp

Sanjay

@sanjay

185 Following
2503 Followers


Sanjay pfp
Sanjay
@sanjay
Message processing was broken today because some events exceeded grpc client default size. If you're using shuttle, please upgrade to 0.4.1 to get the fix. If you are constructing hub clients manually and listening to events, make sure to pass in the following param
4 replies
13 recasts
71 reactions

Sanjay pfp
Sanjay
@sanjay
This one was tricky to track down. There were a lot of dead ends. Special thanks to @wazzymandias.eth for basically fixing it last night and not telling the rest of us 😂 @cassie and @sds for some deep libp2p and tcp tuning magic, which we thankfully didn't need. And finally to my good friend Claude, who pointed me to the `node --prof` command which is able to profile worker threads, would've been much more difficult to narrow down the root cause without it.
9 replies
11 recasts
88 reactions

Sanjay pfp
Sanjay
@sanjay
Released Hubble 1.13.2 with a crash fix (thanks @cassie). Please upgrade for improved stability. We're also planning to min version to 1.13.1 early next week so all hubs support long casts. We're noticing some sync issues due to older hubs that don't support it.
3 replies
4 recasts
30 reactions

Sanjay pfp
Sanjay
@sanjay
Reminder that the replicator is deprecated by shuttle. We’re going to remove the replicator from the hub codebase by end of next week to avoid any confusion. If you’re still using the replicator, please migrate to the shuttle package. Let me know if you have any questions around migration.
41 replies
183 recasts
1002 reactions

Sanjay pfp
Sanjay
@sanjay
We’re seeing message processing delays again. The team is working on scaling our systems to be able to handle it.
0 reply
2 recasts
14 reactions

Sanjay pfp
Sanjay
@sanjay
alpha version of the package is out https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/hub-shuttle
1 reply
4 recasts
20 reactions

Sanjay pfp
Sanjay
@sanjay
@ted @gregan the RWA thesis is finally playing out. When does the goldfinch goat pool open? There's clear investor demand https://x.com/NeerajKA/status/1775881228656181312?s=20
1 reply
1 recast
12 reactions

Sanjay pfp
Sanjay
@sanjay
Please reach out if you’re interested in using this, or have any feedback
4 replies
3 recasts
7 reactions

Sanjay pfp
Sanjay
@sanjay
We're planning to min version the hubs to 1.11.2 later today to improve network health. This version includes the fix to have all hubs use snapshots to catch up if they are too far behind. If you're on an older version, please run `./hubble.sh upgrade` to get up to date. https://warpcast.com/sanjay/0x4a7d7839
2 replies
3 recasts
10 reactions

Sanjay pfp
Sanjay
@sanjay
We've released 1.11.1. @wazzymandias.eth made it so that hubs will now automatically use snapshot sync to catch up if they are too many messages behind. Note that this will reset the db, if you're running a replicator you can disable this to be safe, by setting `CATCHUP_SYNC_WITH_SNAPSHOT=false` in your .env file
7 replies
3 recasts
9 reactions

Sanjay pfp
Sanjay
@sanjay
This is a very cool talk. Interestingly, it's almost exactly the same algorithm the hubs use right now. Prolly trees are more efficient since it collapses the number of levels required (we use timestamp prefix tries, so it always at least 10 levels), but apart from that it's exactly the same.
1 reply
1 recast
17 reactions

Sanjay pfp
Sanjay
@sanjay
Our existing sync architecture for Hubs is running into scaling issues. Been thinking about a new design that can scale to billions of messages and millions of fids. If you enjoy complex distributed systems problems, I would appreciate feedback https://warpcast.notion.site/Sync-V2-a9c0fd81d7b245a0b3fbd51e6007909f
16 replies
18 recasts
86 reactions

Sanjay pfp
Sanjay
@sanjay
Just min versioned to 1.10.5. This should improve gossip performance for the whole network. Please upgrade via “./hubble.sh upgrade” if you haven’t already. Thank you @wazzymandias.eth for the fix.
1 reply
0 recast
6 reactions

Sanjay pfp
Sanjay
@sanjay
Hubble 1.10 is out, please upgrade. Note that this version requires a minimum of 16GB RAM of ram to ensure Hubs will be capable of keeping up with traffic. Hubs with less than 16GB will fail the startup check.
7 replies
1 recast
22 reactions

Sanjay pfp
Sanjay
@sanjay
1.9.8 released with more performance improvements. Please upgrade. Also recommend switching your instance to 4 vcpus and 16GB of ram.
2 replies
2 recasts
12 reactions

Sanjay pfp
Sanjay
@sanjay
I'd love to have the ability to vote for snapshot.org proposals through frames. If anyone from the snapshot team is interested, I would be happy to help build this. It would greatly improve participation. Start with showing proposals in frame and then delegate votes to your fid eth address and vote with a FrameAction.
13 replies
7 recasts
68 reactions

Sanjay pfp
Sanjay
@sanjay
Hubble 1.9.7 is out with performance improvements. Please upgrade. We're aware of hub sync delays. This release should help, and more fixes coming soon.
3 replies
1 recast
23 reactions

Sanjay pfp
Sanjay
@sanjay
I'm firefighting hubs at the moment, so I didn't have time to build a POC. But here's an idea that could be powerful: After you validateMessage on your frame server, you can sign an EIP-712 message with (userId, casterId, userVerifiedAddress). This will enable your smart contracts to use trusted fc data.
3 replies
8 recasts
38 reactions

Sanjay pfp
Sanjay
@sanjay
I live for days like this. Stressful in the moment, but nothing like working with people at the top of their game solving hard problems.
0 reply
3 recasts
24 reactions

Sanjay pfp
Sanjay
@sanjay
This is the future of crypto ux and how it goes mainstream.
0 reply
3 recasts
9 reactions