Farcaster Devs

@rish @neynar Publish message API (/v2/farcaster/message) seems to be affected by the move to snapchain. It is successfully responding but +50% of casts are not appearing on warpcast.
Is it going to be deprecated?
Example hashes:
0x127a9d1603e0d8e2f1dba0297c4075b9bfdf977d  
0xfc481945dc3a9cdeaebef0b9dbd9f743e19c02ca

building farcaster infra @ /neynar 🪐 | casting @ /rish

easiest way to build on farcaster @ neynar.com | /neynar

explorer says these are submitted but Warpcast client is not rendering them https://explorer.neynar.com/0xfc481945dc3a9cdeaebef0b9dbd9f743e19c02ca

will also check with @sanjay , could be client side

Printing "Hello World" since 1980. Building app.datascience.art

They likely didn’t make it to snapchain. We’ll investigate cc @dynemyte

yeah we will look into our side as well if its a write to snapchain failure cc @manan

Thanks for investigating @rish & @sanjay 🙏  
Also just wanted to make sure: the /v2/farcaster/message endpoint will keep working post snapchain, right? Is there any plan to deprecate it in the near future?

Thank you, I love it when the solution is "do nothing" from my end :)

it will keep working, no plans to deprecate 

the switch to snapchain is silent in the background, shouldn't require any code change for our customers (we will solve the bugs that come up)