A place for developers to talk about building on Farcaster.

/dev

Build baskets. Track performance. Earn fees. 

Built for @base -- a project by the @percs team.

No token launch (yet)

Some technical lessons we learned while building @basketdotfarm 

Thread Below 👇

Building @basketdotfarm on @base. Ethereum is not an altcoin, it's a buildcoin.

1. AI is easy to get started with and hard to get accurate.

Using any existing frameworks (we are using Eliza), you can create a demo project within hours. 

But when you try using it with actions and accurate user flows, it's very hard to perfect.

3. Gas estimations are still a problem. 

After spending 8 years in crypto, I was hoping to rely on something like Alchemy to be accurate with gas estimations, but I was wrong. 

Sometimes gas estimations are off by 10x. This can scare the users and cancel the transaction altogether.

Our solution: 
- manually enter gas estimations. 

This will definitely backfire in the future, but it will work for 90% of the transactions.

4. Frames V2 notifications is very flexible and powerful.

We had 900+ beta sign ups. When we sent notifications, we got attention from ~60% of the reciepients.

Notifications are also flexible. We wanted users to go to our launch cast so that we can concentrate user engagement. 

Notifications can only open the pages in the frame (of course), so we created a landing page with a simple "open cast" button with a redirect to the launch cast.

It worked flawlessly.

We're early in the development of @basketdotfarm, but we have received so much great feedback. 

We will be discussing this thread and more feedback in our tomorrow's community call. 

Please join and share your opinions

We're early in the development of @basketdotfarm, but we have received so much great feedback. 

We will be discussing this thread and more feedback in our tomorrow's community call. 

Please join and share your opinions

https://events.xyz/events/12094c

2. Too many tokens and not a single reliable source of truth

We have millions of tokens on @base. Many have the same ticker. It's very hard to guess which one is user looking for.

Our current solution
- reverse sort by the amount of transactions
- pick the top one and ignore all else
- hardcode this so that AI does not screw up

Creator of @harmonybot /bot-or-not | /blitkin | /orange-dao | IRL: Building spatial computing for construction @ Resolve YC W15

If I had to restart the project, I'd not use Eliza for the action system. It sucks!

spot on! would love to know if you made any modifications to the Eliza action system that improve it.

I've found that while it's quite good at yapper agents the action system is a bit hit or miss. it has the tendency to prefer a reply vs perform an action.