Sanjay

@sanjay

210 Following

5292 Followers

Sanjay pfp

No, none that I know of. I use an M2 for development and it's worked fine.

0 reply

0 recast

0 reaction

Sanjay pfp

Looks like it can’t connect to the hub? Is it running? Is the hub url correct? I think the port should be 2283?

1 reply

0 recast

1 reaction

Sanjay pfp

Hmm, people are out today. I don't have an ETA for the fix. I suggest working around this for now by disabling snapshot sync. I'll set up on some alerts so we can catch this before the snapshot expires next time.

1 reply

0 recast

0 reaction

Sanjay pfp

1 reply

0 recast

1 reaction

Sanjay pfp

Hmm, this is odd that the messages are increasing so fast but peers are 0. Wonder if it's more of a metrics reporting issue than the fact that there are no peers. Could you DM me the most recent logs from the hub?

1 reply

0 recast

0 reaction

Sanjay pfp

Try now? https://download.farcaster.xyz/snapshots/MAINNET/DB_SCHEMA_11/latest.json points to the latest snapshot

1 reply

0 recast

0 reaction

Sanjay pfp

Not that if it's a brand new hub, I think it will still fail. The flag is only for catchup sync. You have to pass the `--disable-snapshot-sync` cli flag to bypass snapshot entirely (and it will start with no data). I would wait for the snapshots to be fixed if it's a new hub.

2 replies

0 recast

2 reactions

Sanjay pfp

Yes, good point. That will work too.

1 reply

0 recast

0 reaction

Sanjay pfp

Look like there's an issue with the hub that generates the snapshots. We're fixing, hope to have the latest snapshot uploaded later today.

1 reply

0 recast

2 reactions

Sanjay pfp

We found about ~1K users in this state, we'll fix. Thanks for reporting.

1 reply

0 recast

3 reactions

Sanjay pfp

We've been so focused on snapchain, I forgot to do the Hub protocol release for Nov 27. Just released Hubble 1.17. Please upgrade before current version expires at Dec 11 midnight UTC. Apologies for the short notice!

0 reply

24 recasts

194 reactions

Sanjay pfp

Hmm, will investigate

0 reply

0 recast

0 reaction

Sanjay pfp

1 reply

0 recast

0 reaction

Sanjay pfp

Considering buying a house, and came across this very cool and very legal covenant (from 1946) for the land in the disclosures. Can't say I wasn't tempted to buy just to stick it to them.

6 replies

11 recasts

77 reactions

Sanjay pfp

Should be fixed now

0 reply

0 recast

2 reactions

Sanjay pfp

Looks like we're consistently running ~4mins behind since last night. Looking

1 reply

0 recast

2 reactions

Sanjay pfp

Not any more. All current messages require ED25519.

0 reply

0 recast

2 reactions

Sanjay pfp

What exactly do you mean by "client side"? The best way to validate a message is to call the validateMessage endpoint on the Hub. databytes is optional, you need to protobuf encode the message to verify the signature, see https://github.com/farcasterxyz/hub-monorepo/blob/aa9cde7543886e7d109ab81877a23646d1cbbfe8/packages/core/src/validations.ts#L312-L322. But note that this is only a small part of what the hub does to consider a message "valid". A few other important steps are to ensure that the signer is still active and that it's associated with the same fid as the message. You might also need to do other validations depending on what you're looking for. Take a look at validateMessage function in engine/index.ts for a more complete view.

1 reply

0 recast

1 reaction

Varun Srinivasan pfp

Varun Srinivasan

One point of feedback we got on the Snapchain design doc is that we didn't fully explain why sync in the current model is a problem. @sanjay wrote up a good thread on our internal slack, which i'll try to summarize below. https://warpcast.notion.site/Snapchain-v2-Public-10e6a6c0c101807aadfacbcddda8ce4f?pvs=74

3 replies

72 recasts

219 reactions

Sanjay pfp

If you query the contactInfo object for the peer, it should have the dns name if the hub is configured correctly (hoyt should be announcing it's DNS name for example). We have to handle this case for syncing see code here on how to translate from the ContactInfo into a working RPC client https://github.com/farcasterxyz/hub-monorepo/blob/1ca66d8cf21c5c98e084175a2bba4b803a85da07/apps/hubble/src/hubble.ts#L1730

1 reply

0 recast

1 reaction