for solidity practice I wrote a funny april fools token that stops working at midnight on april 2nd in the latest timezone

hardcoded allowlist to be all farcaster users, no admin functions https://gist.github.com/gskril/1ac1494a122a44b7fa7d38c5707fe5bc

ok i deployed it https://fool.gregskril.com/

every farcaster user that had a connected address as of this morning can claim 100,000 $FOOL

it will stop working at midnight tonight in the latest timezone (UTC-12)

it will activate again next year april 1st for 36 hours, then repeat for 10 years

use at your own risk

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

weird ive been connected for awhile and not on the allowlist

hmm @rish @manan i used neynar dune data https://dune.com/queries/3581281

any idea why some people’s addresses might not be showing up?

🪐 Building @neynar, join us in /neynar

working @ /neynar   🪐  casting @ /rish

🟠 OG - 💰 /allowance 🔗 metrix.tools



dune picks from this same db and that seems to have the data (see screenshot)

so do our APIs curl --request GET \
     --url 'https://api.neynar.com/v2/farcaster/user/bulk?fids=267915' \
     --header 'accept: application/json' \
     --header 'api_key: YOUR_API__KEY'

haven't looked into dune directly but seems weird

Looks like it’s not returning my connected address. It’s showing a longer one that I’ve never seen before

did you connect a solana address? 

@greg the data on dune is not encoded in base58 that's why you're running into this. 

It's correctly encoded on our APIs (you can check on the docs site), do you want to use that instead? or you could encode it on your end after reading from dune

which db are you referring to? 

our db shows you having a connected address

pretty sure this db is wrong.

i have always had a connected eth address.