KMac🍌 ⏩ on Warpcast

Sanjay pfp

Both @neynar and @warpcast are reading/writing to Snapchain now. If you’re using Hubble, you should migrate to use snapchain exclusively and let us know if you run into any issues. https://docs.farcaster.xyz/hubble/migrating https://warpcast.notion.site/Snapchain-Mainnet-Public-1b96a6c0c101809493cfda3998a65c7a?pvs=4

14 replies

33 recasts

219 reactions

KMac🍌 ⏩ pfp

If we are hitting an open hub via grpc - what needs to happen? eg assume rhe hub operator migrates to snapchain, what will we app devs have to do?

2 replies

0 recast

2 reactions

Andrei O. pfp

Nothing for now, but at some point not very far in the future, hubs will cease to work. I haven't seen anyone providing a public open node. At that point, you will be forced to either run a node or buy one.

1 reply

0 recast

1 reaction

KMac🍌 ⏩ pfp

Thanks. What’s your take on how we can make this more open? IF im understanding this correctly, the ecosystem would benefit from a lot of public read nodes & (iirc!) they forward the writes to a smaller set of permissioned nodes.

1 reply

0 recast

1 reaction

Andrei O. pfp

My take is that the Merkel team should provide 1-2 open nodes. This is similar to how many L2 projects offer open RPC nodes. A node is useful for both reading and writing to the network, but it has some costs. It's called "Snapchain", for such open networks it is common to provide a test network and public nodes for both test and mainnet environments. If a test environment is too much to ask for, at least 1-2 open nodes should be provided. However, in the last dev call, the Warpcast team said they would not provide any such public nodes. So, if no one steps in to provide them, then no open nodes will be available.

1 reply

0 recast

2 reactions