Warpcast

New settings for Warpcast group chat invite links

- Limit to people you are following
- Limit to Active Badge
- Limit to NFT holders

NFT holder feature (i.e. token-gating) works with any OpenSea collection URL.

Settings are live on mobile; will be on web soon.

There's no canonical group chat for each NFT project.

Instead, anyone with the NFT can create a public link and anyone that meets the Farcaster social graph requirements can join.

e.g. you can't just buy the NFT an automatically join the chat. Social proof of work.

Suggestion: Support balance (must hold X tokens), and ERC20.

Not sure if the OpenSea API provides this, but maybe the etherscan API does. Would work both for NFTs (X>0) but also for coins like $degen (X>1,000,000 for example).

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

I recommend checking on-chain using RPC instead of a centralised API.

This is a blockchain after all.

Talks about crypto and coffee. Building on-chain algo trading - check out my channels /algo-trading and /python

You're preaching to the coir. The guys created a decentralized network to build Farcaster on top of it. Building something like this in the protocol is very complicated and it would only make sense if it finds pmf.

I mean you literally can check the token balance easier using RPC than Etherscan.

Which chain? Right now, we have NFTs on L1, OP, Base, etc. What's the single RPC that does this? (I assume you mean Ethereum node RPC)

You can get multichain RPC e.g. from
- Pokt (decentralised)
- Quicknode
- Alchemy
- Infure

For more RPC providers see ethereumnodes.com

Of course I recommend any teams to run their own nodes.

So, what's the difference between using an API from one service vs an other service?  I had the impression you wanted to use own nodes. If one of them censor or go down, so do you. You totally depend on them. "Using an RPC" does not make you "web3".

On complexity: Infura and Alchemy for example, have specific API endpoints per chain, as far as I know. Which means it's up to your application to pick the right one, depending on what the user picked. Moving this to the protocol level (hubs) is even more complicated.

"RPC" (Remote Procedure Call) is an API spec used by 1000s of services. It's like saying JSON or REST or HTTP. There's nothing open or closed to it.

What a proprietary app like Warpcast uses makes no difference. If you have a proposal on how to move this to the protocol level (not trivial), you should post an FIP!

I don't understand. Can you clarify the complexity here?