mvr 🐹 pfp
mvr 🐹
@mvr
Testing a new feature for @tipn in the Airdrop Mini App! Tip at least 1 $TIPN as reply to this cast and you will participate in the (weighted) Raffle for my remaining $TIPN allocation. 1 winner get's all. Valid tipn tips only. https://airdrop.ham.cooking/?fid=230238&type=cast&ticket=V0I17aTrx&target=tips https://tipopolis.hamst.art?fid=230238&extra=123adfdfa&tab=tips
31 replies
8 recasts
56 reactions

niftytime pfp
niftytime
@niftytime.eth
Extravaganza indeed! Great way to clear this allocation dust out 1 $tipn
1 reply
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
yeah, cool right? i could also sell it as tip validator about that, am i right to assume that if 'hasFidCast' on the contract returns true the tip is valid? or am i completely wrong there :D
2 replies
0 recast
1 reaction

kompreni 🚂 pfp
kompreni 🚂
@kompreni
It returns true if the tip has been processed.
1 reply
0 recast
2 reactions

mvr 🐹 pfp
mvr 🐹
@mvr
Not sure if I understand. Processed means? You don't have allowance so tip not sent to the other side? It's seen but no further action
1 reply
0 recast
1 reaction

kompreni 🚂 pfp
kompreni 🚂
@kompreni
Sorry for the confusion. We have a backend that listens for eg 100 $tipn from accounts with allocations and performs the onchain update to debit from the allocation and credit the balance of the other. If that function returns false it means either our backend failed to process the tip or there was some issue preventing it from being processed (no allocation, insufficient allocation remaining, usdc not enabled)
1 reply
0 recast
1 reaction

mvr 🐹 pfp
mvr 🐹
@mvr
Allright, that's awesome and exactly what I'm looking for. Thanks for the detailed explanation! I might have ran into a bug then because my tipn implementation showed more $tipn valid on a cast than I was able to claim in the mini app (~1300 vs ~900) Will double check my logic because likely I did something wrong, will get back to you if I couldn't find anything on my side
1 reply
0 recast
1 reaction