m00npapi.eth pfp
m00npapi.eth
@m00npapi.eth
fun note on @luc’s launch of $fair it was done via “pre-clank” - he went on clanker dot world set the params and saved it with a phrase then he tagged clanker with the phrase and voila - clanker with extra params 🤝 the magic of launching in the feed
29 replies
12 recasts
135 reactions

mvr 🐹 pfp
mvr 🐹
@mvr
Nice, but now I need to figure out why @mecode didn't manage to link the token to his fid 😅
1 reply
0 recast
1 reaction

m00npapi.eth pfp
m00npapi.eth
@m00npapi.eth
do u work on mecode?
1 reply
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
guilty
1 reply
0 recast
1 reaction

m00npapi.eth pfp
m00npapi.eth
@m00npapi.eth
Check the chain on $fair deploy I suspect ur listening to a single EOA
2 replies
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
https://farcaster.xyz/mecode/0xe555f2bd
1 reply
0 recast
1 reaction

m00npapi.eth pfp
m00npapi.eth
@m00npapi.eth
ah wait this was actually the right way to go about it then, it was a fun parlor trick for luc’s thing to show up in feed
2 replies
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
what is your suggestion to confirm this is not spoofed? call your api? i'm currently checking whether fid has the msgSender in verifications or whether msgSender belongs to a fid but that didn't work in this case because 0x24D514Bc8eF5649A367d9c209b3AF16b0f177026 isn't known assume you can login with your fid in clanker.world and sign your prelaunch with whatever wallet which is not linked clankerContext { id: "4013", platform: "farcaster", interface: "clanker.world", messageId: "", }
0 reply
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
looks like @luc used another wallet on clanker.world and this block which checks against farcaster verifications flagged it as spoof :) // Check if tokenCreator matches any address in verifications const exists = fidWallets?.verifications.some((v) => v.protocol === 'ethereum' ? v.address.toLowerCase() === tokenCreator.toLowerCase() : v.address === tokenCreator, );
0 reply
0 recast
1 reaction