frames

attempting to integrate frames and getting this warning on a pretty generic contract. this is a provably false claim and the call works great on all other wallets I've tried. Can anyone from the Farcaster team share a little more info on what is happening behind the scenes here? what causes this flag?

we scan with Blockaid. there are sometimes false positives. you can self-report at the portal here:

building sidequest.build • https://twitter.com/codybrown

we scan with Blockaid. there are sometimes false positives. you can self-report at the portal here: https://report.blockaid.io/

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

more often than they should. this in particular is a weird error for a simple contract, we'll look into it. I know it really sucks to get hit with a false positive warning like this, but the best thing you can do right now is    proactively verify with Blockaid, reserve some time to make sure you're not flagged before you launch a new contract, and reach out to someone at Warpcast if you do get flagged.

more often than they should. this in particular is a weird error for a simple contract, we'll look into it. I know it really sucks to get hit with a false positive warning like this, but the best thing you can do right now is    proactively verify with Blockaid, reserve some time to make sure you're not flagged before you launch a new contract, and reach out to someone at Warpcast if you do get flagged.

https://report.blockaid.io/

do you have a sense of how often false positives happen? or how to write a contract that doesn't trigger this flag? this is a super generic NFT contract.