Content
@
https://warpcast.com/~/channel/openventures
0 reply
0 recast
0 reaction
alex 🎩
@proxystudio.eth
Man @warpcast cash tag integration is great One of the best, simple features for discovery I’ve seen since joining crypto Works shockingly well given name collision stuff Study Merkle product dev process
6 replies
7 recasts
80 reactions
Sinaver
@sinaver.eth
@rish any plans to index this, although I assume it's not protocol level yet
1 reply
0 recast
1 reaction
rish
@rish
the tags are already part of the cast so thats on the protocol and returned as part of the indexed data we have a few ideas but curious what you'd like neynar to provide here
1 reply
0 recast
1 reaction
Sinaver
@sinaver.eth
along with cast return optionally, mentioned_tokens []: {"ticker": string, "chainId", number, "address": string, "market_cap", "price": number, ... }
2 replies
0 recast
0 reaction
rish
@rish
how do you determine the exact token from the ticker when there are name collisions?
1 reply
0 recast
1 reaction
Sinaver
@sinaver.eth
currently, I have a list of supported tokens, but going forward if I was expanding to support any token, I would pick the top 3 by market cap for chains I support and ask user to pick one; other approach to have additional meta like the origin of token if it's created through clanker / on farcaster / related to a product, etc, and user mentions that matching meta in cast, this way an agent could potentially figure out the match, or user already made some tnxs before with a token in the list ...
1 reply
0 recast
0 reaction
rish
@rish
makes sense. the ideal way here is for client to let users select a token when mentioning it, same as what they do with users. When user selects a token, the client puts the CAIP of the token into the message when submitting a cast to the protocol then anyone reading has exact information of which token the user was talking about. Services like Neynar can fetch the real time token information and hydrate that as part of the cast metadata when sending the response. @dwr.eth mentioned putting this on the protocol at some point but I think prioritization is still tbd
0 reply
0 recast
0 reaction
