Bot or Not

I've been wanting to ship this for a long time...🥳

There is a new "Attest" button in the /bot-or-not frame that allows you to confirm the analysis of a given FID on-chain via /eas attestation on base

Want to double down on someone's bot-like status? Attest.

Find a solid builder and want to let the world know? Attest.

I may iterate on the schema once more, but want to start testing this. I have more thoughts to write on this feature but will save those for another time.

here's an attestion of my own Bot or Not classification: https://base.easscan.org/attestation/view/0xd91aa15ca95407c60b8714bfd9a5526353e242d8609d5efa6f7d0d0456c42e73

More thoughts this morning:

I get asked about a /bot-or-not API a lot. This brings us one step closer to an open, on-chain version of an API.

AND it lets you use whatever system you want to weigh classifications. Weigh by SCS of the attesting FID, openrank, etc.

Checking the chains @witness - icebreaker.xyz/osprey.fc

Accelerating Web3 Ownership
https://witness.co

Creator of /bot-or-not. Contributing to /blitkin & /orange-dao IRL: Building spatial computing for construction @ Resolve YC W15 | FID 1725

something else to experiment with would be @witness, not totally sure how things would play between it and EAS but it feels like it connects. cc @osprey

W̴̢̛͈̘͇̃̾̐̚͝ͅė̴̱b̴͖̱͗̓͗3̸͖͙̫͙̾̂̊ ̸̥͍̙͉̙̉̀̕͝͝͝D̵͇͖̲͆͊̋͝è̷̺̓v̷͙̟͖̥͔̆, 🟪#153

if you are okay paying dynamic/ upfront txn fees for every attestation and want public availability of the data, onchain EAS attestations are 👍

if your usecase or user would benefit from removing dynamic/upfront txn fees while maintaining the ability to verify “when” the attestation was made, then start using offchain EAS attestations (or any other opionayed schema) and @witness 🫡