Who's your Onchain Graph?  

Introducing Airstack Onchain Graph

♼ analyzes all your onchain interactions and constructs your onchain graph 

dev APIs to build this into any app for recommendations, solving cold-starts, and more

Give it a try at

Who's your Onchain Graph?  

Introducing Airstack Onchain Graph

♼ analyzes all your onchain interactions and constructs your onchain graph 

dev APIs to build this into any app for recommendations, solving cold-starts, and more

Give it a try at https://explorer.airstack.xyz

any reason you didn't go for name.farcaster or name.fname as a better convention for referencing farcaster usernames from outside farcaster?

Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

Yeah, will look at improving that

Thanks!

I'm curious - I'm not sure what the convention is

I don't think there's a convention. We have decided to use a short version of the protocol name followed by the parameter queried. We have fc_id for Farcaster, and similarly lens_id for Lens. 

There's no specific reason, just our internal decision after thinking of way how to support multiple protocols.

This is also not designed to be a consumer app rather a showcase for the APIs. I wouldn't expect an app building on top of our APIs requesting the end user to enter fc_fname 😅