DAPPCON 2025: Vibe Coding Farcaster Mini Apps: Build One Tap Crypto Apps That Anyone Can Use

Transcript

All right, let's go. Uh, welcome to the VIP coding mini apps workshop. Um, we're going to start with a quick overview of what's actually going to happen because some people had questions with this long title. Um, my goal is to basically take you from zero to have a live mini app. I'm going to give some background on why mini apps are cool, what I'm doing, and how to set it up. But then the main part is actually uh VIP coding. We're going to implement some features. I have some specific prompts that I'm often reusing and of course troubleshooting VIP debugging is is always there and in the end wrap up if anyone was actually following along you can uh share what

you've done you can share um quest you can ask questions and we can obviously help you deploy it and go live um so while listen to me just a quick challenge on why I'm here in the front and not in the back uh vibe coding So I've built um the number one open source Farcaster client. That's why I'm building on Farcaster and currently I'm building Vibes Engineering which is kind of a factory to generate mini apps. Um so I have experience from when mini apps on Farcaster were introduced and uh I'm celebrating 20 years of writing code this uh month. So I'm old and I've been writing code manually for a long time.

um and now switching to actually using LLMs or VIP prompting a lot more and I'm active on Farcaster and in crypto for for a while. Um so why mini apps? That's basically me trying to explain why mini apps are nice and uh you should you should build them. Uh it's super easy to get your users to actually do something on chain. So I think everyone is struggling with the discussion on how from protocol improvements to actually users get people to do something um with blockchain that is useful to them. So with mini apps in three clicks or sometimes less you can actually help

them do something and get the value on chain. Few great examples that uh do this. I recently went to the US and just bought an eim five minutes before my plane took off. So just in a mini app. I opened it from the feed. Uh I had USDC in my wallet. Uh and Kartik built it so that it's just an EIM. So I can uh use it from my phone straight away. No emails, no no contracts, uh no user data is leaking. I just have an EIM that I can use. Um, the second example is something that I vibe coded fundraiser to get going. So, people could offload their meme coins uh that they had on any chain, any tiny amount. They could just

donate it to me uh crosschain straight from the feed and it was successful and I could just pay for trip to uh New York to see the conference. And the other two examples are more social and more gamelike, less onchain, but also interesting. The first uh the third one on this slide uh where you're at is sharing your social uh graph on a map. So you can check in in certain locations and only your followers can see where you're checking in. And the last one is just a game. There's a bunch of different ones. This is a take on Wordle uh which is interesting but here again you compete against your friends and you can mint your success on chain. So from utility

you can do a ton of different things um with mini apps. Uh this is kind of a a ton of memes on one slide but the go the mic works. Sorry, there's some hiccup, right? Okay. Uh, so I I'm also confused right now uh with the mic. So going from confusion to actually shipping your first mini app, that's the goal um in in a few tiny steps and how you can do it. Um the main one I see some people with laptops uh here. So, if you have a laptop with you in the room,

the easiest and what I'm going to show you is actually from a laptop. The other one, if you just brought your phone, uh, or you're at home and want to watch the live stream, uh, there is a way to do it, but I'm really going to focus on the first part. Um, if you want to vibe code along, scan this QR code or go to vibes.engineering/go. You're going to see some documentation, a bunch of links, a ton of useful content that you can use in this session and you can bookmark it for later. It's going to help you uh get set up much faster. Tapping on the phone, I don't want to promote it too much, but that's the app I'm building. It's called Vibes Engineering. It does the same thing from

your phone, but I I'm not going to talk about it further. The main thing is just free access what everyone can do at home by coding from your laptop and going from zero to uh to a live mini app. So that was most of the slides. Now we're switching actually checking the setup and how to get started in a few minutes to see maybe this works better. Uh to see the very initial mini app that you can use.

Can you see this in the room? I think that's important. If you can read the text, is that possible? Cool. Thank you. Um, so what's needed to to have a mini app? You need to have a starter project that is linked in the in the repo and then usually you just do pnpm install and then dev to get going. One important piece to actually have a look at the mini app, not in your browser, but as other people will see it, is you need to look at it in the preview tool. And for the preview tool, you need a small tunnel from your local developer setup to the Farcaster preview tool. And for this, I'm using

Cloudflare. There's a bunch of other providers. Um, I'll I'll be using this one. And of course the third terminal or the third piece for VIP coding you need somewhere to to submit the prompts. I'm using cloud code for this and we can uh we can see a bit more of that later. And now to check out a mini app in a preview tool. This is how people will actually see it. As you can see I just copy pasted the address in here and then you can open it. And this is my generic template starter that you can also use as a starting point to to VIP code from here. Um important different than other websites and other

approaches to this is by just opening the website you as the app developer immediately have data on on who's visiting the website. So you see the forecaster user ID, you see the username, you see their their profile picture, a bunch of things to immediately customize how the app looks like and how make it valuable. And you see some other data that we can skip for now, but um you can basically also send haptics and uh register the mini app. You can have a bunch of different actions. And the key things that I want to show is how easy it is to send onchain transactions or do things onchain versus connecting with metam

mask wallet connect going through all of this pain. The easiest thing or the easiest example is just signing something which is uh one click you can send ETH. if I had enough uh money in this wallet. In this test wallet, I could send ETH which is just one click and you can also sign type data where you can check out the data here and also just confirm it and make a signature. Uh this is not just for base or specific change. You can also just change um change the wallet connection without the user having to do anything. So all of this is already much simpler than than other environments. Then another

example that is baked into the template starter just to show you um an actual onchain transaction of minting an NFT. It took a while to load. So this is a dynamic NFT component where you can just submit your contract address and it will render it nicely and you can just forward people to mint it. It will fetch the price and it will switch the chain automatically what you've seen in the background and then hopefully I have enough guess that this works and this will just be the first mint of this NFT that I've set up. Um, if you also want to have kind of a poor, you can also

mint it. And that's just a quick run through of everything that is in the starter template and how easy it is to actually do onchain transactions through mini apps. That was the the first part of just showing what you where you can start from and what you can do. Now the second part, the longer part of this session will be the demo of actually VIP coding building new things and I just had this idea yesterday. So because everything here at Deepcon is very circles focused, um I thought about building a mini app for circles with the very simple use case where you see a list of your

Farcaster friends, meaning the people that you follow and check if they're on circles and if possible trust them on circles as well. So we have an environment that I just showed where we know who the user is that uh logged in and we know the Nana API which fetches forecast the data. We know circles at least that's in my preparation. what we're going to do live is um how it should actually look like and if we can do it in the time that uh we have here but that's going to be the live component of we're prompting cloud code and we want to see um the app that uh comes out of it so I'm going to switch

to my editor and hopefully we'll get some interesting things happening here I'm going to keep the editor on this side and just quickly rearrange so that you can see the mini app that we are generating is on this side. Doesn't look as nice but I think it's fine. Second here we go.

Okay, nice. Now to the interesting part of typing things that I haven't seen as well before. So this going to be fun. Um the first point is we just want to show a list of um friends on Farcaster which I have this um existing Farcaster account which is called Vibes Engineering and uh I follow a bunch of people and I just want to see a list or anyone who opens this mini app should see a list um of their friends. So it's immediately personalized. It's immediately something that people don't necessarily see every day or have access in the context of circles.

So I'm just going to type use the nana API to fetch friends user for the user who visits the mini app. Let's see what it does. This as this session might have some pauses and some waiting for LLMs. So, I'm just trying to explain it if you can't see it that well in the back. Um on what's happening and what cloud code is actually doing. Um and I have a bunch

of stuff prepared as fillers. So, um it's not going to be too boring. Um so, here the first step that I'm always trying to um prompt before it runs into mistakes is making a to-do list. Um so in the background I created a claude MD file which is the default um default way of cloud code to have kind of a repository or knowledge of the repository.

Meanwhile it's just asking to install stuff. We can we can say yes. And um this cloud code file already this cloud MD file now already knows my preferences. So, I already told it, hey, I have a development server running. Please don't use uh pmppm build or don't create new production builds while I'm um running this development server because it would break the demo that we're doing right now. And I also gave it the the task to always say, "Give me a list of to give me a to-do list of the items that it should do and explain them and give me a nice overview of what you're going to

do." And usually as well, tell me, no, tell me a few different options. And I did that. I've prepared some examples here with different prompts that I'm regularly uh using. So one of them is give me suggested solutions. I'm usually working on startup prototypes. So that might not be relevant for everyone but I'm using a startup prototype. Focus on 9010 impact to efforts. So give me simple solutions. Don't overengineering over engineer it. Many people have problems with VIPE coding because if you just let the LLM run its way, then it's

confusing things. It runs into insane corners. It tries to implement enterprise features that you don't need. So I gave it some constraints here. And I always tell it to follow clean code conventions. I have another prompt that I'm often using is I'm telling cloud code to ask me questions for anything that it might not know or that it needs to know before it can proceed confidently explicitly saying don't write any code just respond back let's just have a conversation in cloud code recently they added a planning mode because I think many people ran into the same problem but I still often can use this

explicitly to tell it don't go don't go crazy. And the longest one that we don't need to use yet, but I'm just sharing it while the LLM is still thinking, which is a code review. I don't have many humans on my team, so I'm using LLMs to also do code reviews. And I'm just asking, is there breaking bugs, any crucial breaking points? So don't give me small typos. Don't give me minor things that I don't want to see right now. Just focus on the huge items that uh I need to fix before deploying this to production. Um I'm telling it to find

root causes, which means I don't want a superficial solution that just patches one tiny um case but doesn't go deep enough and actually fixes what is wrong. Um, and I do a similar pro similar aspect of the prompt where I just tell it suggest a few solutions. Don't just nail down or focus too fast on one thing. Just give me a few options so that I can um select which one I like the most. This was a huge unlock for me uh to be honest. That's why I'm promoting it. Maybe it's common knowledge by now, but just saying give me give me a few options. Usually I have

a specific opinion on which one I like best. And if I just tell the LLM in vibe coding to to run as fast as possible with anything that it likes, it usually goes off in a wrong way. So having these points where you force it to go broader and give you a few options and then you pick one or you have a deeper conversation about one usually helps a lot. Um and again some guard rails against um especially in anthropic models or in cloud code. Um don't touch irrelevant parts of the code. Focus on where you actually need to go. Don't scan all files. Don't go super broad. Don't go

overboard with things that are irrelevant to what we're doing right now. Maybe other things are breaking in the project, but I want to focus on a specific uh problem. So, I'm also telling it um this aspect and I'm telling it again to just respond back and don't uh and don't fix things immediately to have this conversation about a few different options. I think now is a good time to just check in on what the LLM is actually VIP coding.

We can refresh here and see if it already implemented some changes. Doesn't look like it. Let's analyze where it went while I was rambling for a while. Okay. So, it's trying to connect to its own uh API endpoint that it created. And apparently there's just some some type error that I'm seeing here. And now it's asking if it can run a a checker.

Let's see which API endpoint it actually created. We can go in here and see it successfully vibe coded fully without us looking into the NA API. It created a NA client. It knows we need to work with a certain FID um which is the unique identifier on Farcaster. And then we're getting the data back on who is the user following and who are their followers and returning the the list of FIDs.

So this all seems good. Now we're waiting. While we're waiting, I can continue explaining some aspects of the mini apps. Um, Tim is here from Ki News.

That's one feature he uses uh a lot and he saw a huge bump in traction from using the feature of um adding mini apps to the Farcaster client. For this, I need to change the example that we're looking at. where you can send notifications directly to the people using your mini app with this dialogue that you can just prompt um for people to see which I'm I'm using this weird name uh Devcon mini app template which isn't really useful but it could be a single word circles.

So here you can just read add mini apps circles and then you can add it to Farcaster and then you have the permission to send notifications to people which on Android and on iOS it looks like a native notification. So if we open this window here and just look at the mini apps that are all pinned. This is my developer account. So it's a bunch of developer apps. All of these uh apps can now send me notifications that will just appear in my feed as regular notifications and on my phone as regular um iOS native or operating system native

um notifications. And as an example, I have a few here where here we're saying thanks for adding this mini app. And up here you can see a bunch of uh a bunch of a bunch of notifications got grouped. Now you can see it. Um for this uh mini app that I'm building repeatedly sending notifications, they get grouped and you can still reach people with updates. So for me, I'm using longunning jobs in the background. So it makes sense for KV news as an example.

if there's breaking news or if there is trending topics, you can easily also notify your users uh to come back to the mini app to re-engage to be aware of the trending news. So that's a very useful feature that is uh as far as I'm aware pretty unique to to many apps. And now we see the cloud code in the background finished. So we can check it out again. Let's open it.

And here we can see we need to go to the friends page. It navigated us to the wrong page. Great success. Let's do slash page. I want to see the friends page as the default when I open the mini app. And what else do I want to see? And I want to focus on only seeing people that the user follows. So we only want to see the friends. I think it went in some

slightly wrong direction where it also checked the followers where it's pretty irrelevant if people follow me right now and they're also on circles. I just want to see who I'm interested in. Focus on followed by the user and not on the followers. Now again we're getting the to-do list

which is just I talked about the main page it understood the API needs to change and updating the friends component should also be there and now for the first time we actually see something interesting that immediately fails but it updated the changes this immediately to change the main page. And we're getting some error because it's also updating the API endpoints. Let's wait until it's done.

failed to fetch friends. It's kind of sad. Let's see. Because we don't know where the arrow is, we might need to look into this thing. Fail to fetch friends. That's another pattern that I'm often doing when developing mini apps because there's the server side component that has the route and makes the API calls

which I don't see in the browser really and then there's the browser side which is running the mini app which is throwing errors for some reason. But when we click here, we only see the front end error which doesn't give us any information. So I prompt the mini app to say lock the server side error so we can debug this better and understand why the request fails.

sending this. That's an interesting newer feature that I haven't seen in cloud code. I think maybe last month was the first time it showed up where it's actually writing curl commands or tiny scripts to check on your local setup, which is a very interesting feature. I don't have to go around and debug is my local server running. Is there a connection error? Is this API actually returning what it says

it's returning or um am I doing everything correct? And Cloudflare is down as it was last week as an example. Um I was VIP coding uh last week and I thought I had a ton of bugs in my system but it was just layers of database and Cloudflare and other service being down. So this thing helps automatically debugging as well. Okay. Now we added the debug logs as well.

Let's give it another try. So, we don't know why this happens. Okay, this seems like a crazy error.

Maybe it's a good example of what I'm usually doing. Not usually. I'm still doing some stuff manually every now and then. But for this example, we can just copy paste the whole thing and use our prompt that we had here in saying find the root cause and not just focus on I can copy paste this. So now we will see it will provide us with a few different solutions. It shouldn't touch the code. It should should really only touch the code once it's really obvious and it's maybe

missing a package or has one simple clear solution. But generally now it's doing a C review and checking what's going wrong. And here it gives us a few item action items where we don't know should we go deeper into the live debugging we can check the nana API because I know the end file is is set up correctly.

Valid FID S3 log 400 errors more precisely so we know what's We can check this is the problem that we're not setting the environment variable. So one thing to actually communicate

between the front end and the back end might be that we need to set a specific environment variable so it fetches our data correctly. Still no success. So, we're getting a nana API error.

This is very bad for the demo because it never happened to me before. And I actually don't know the solution. Oh, here it is. Limit must be between one. Yeah, it was 200 two. I expected this account to have many friends, but Nana tells us we shouldn't fetch 200 friends. It should be less. Um, okay. I'm relieved. Hopefully, we'll find a list of our friends now.

And here we go. We have some vibe coding success. Um, I was nervous for only only a bit. Um, perfect. Because now the actually interesting part um or more interesting part is in how we connect this list of friends to circles accounts um where I found some API that returns this data for us in every Farcaster user has a bunch of connected Ethereum addresses. So you can it's called verified addresses and each user account or FID um they they live onchain on optimism but you can verify on Solana on

EVM and soon a bunch of other places that you own certain accounts um which is really relevant for us for now I know Franco here he has a circles account but maybe not all of his Farcaster addresses are actually connected to circles only maybe his main ENS address or a different one and we want to find this connection between Farcaster account and circles account and we have some API prepared for this and this part actually worked in the test yesterday. So I'm more confident we can we can get this done quickly where we can now copy

Maybe we make our lives easier and just say finish the workshop plan related to the circles integration. So we can look up the connection between the forecaster friends that we're showing and if these friends are on circles too and if they are I want to open their uh profile right in the metry app so I can trust them which is I know these

people for a long time from their online activity. Some of them I've met uh in real life but not all of them but I would still trust them on uh circles. So this is what we can show here. We want to open the matri contract address and we have a typo.

Um so now this just simply making one um API call and showing all of these people works. It might take a while for the rest to finish to do the full circles integration. If anyone has questions in the room or online, we can uh go through them while this is running. Um, I can keep rambling about features in Minaps because I'm excited about them. But if there's concrete problems, uh, specific integrations, um, or questions you have on miniaps, we can also go over them now.

Any questions? No questions. contracts. Can you deploy contracts? Yeah, you can make any any onchain interactions, anything that you want to do. So, there's a list of um there's kind of a permissioned list of um blockchains that are supported right now by by Farcaster.

um they are being challenged by Coinbase wallet which will also be a far caster client and which supports many more chains. So the assumption is basically all chains will be supported in the next few weeks or months and then you can deploy contracts on any chains as well. Um, some people already do it to deploy uh saves which has like specific uh deployments or it's just one type of contract. But you can probably also just have a even solidity editor and deployment uh button in in a mini.

Yeah. So the the question is how much we're spending on uh nana or other tools uh around um mini apps in in API providers. Um so for me it's uh to be specific I just have one uh paid plan on most of these providers on the lowest tier. So it's not crazy expensive. It's not immediately you're jumping to the enterprise tier. So I had some apps um that I showed before. For example, the vibe coded fundraising tool um which had a ton of traffic even though only 70 people donated many more people opened it and all of them generated

traffic in including alchemy requests on the on the funding just reversal for hosting and nana as well. Um, so maybe to sum it up, it's 100 uh bucks per month, but you can start with all of them also on the free plan. Nana has a free plan on where you run the mini app. You can also do it um a bunch of APIs and requests are also serves served by Farcaster directly. So these are all free as well. um to send notifications if you're on the not on the receiving side what I showed but on the publishing side of sending notifications. All of this is free as well. So um I mean there's always these versal screenshots

of people going broke because one of the apps are trending. Luckily FAS isn't that big yet. So I don't think the total market is will ruin you. It can run into problems. Um, but it's it's pretty doable to do one for free. Yeah. Mhm.

Yeah. So the question is where are these mini apps actually running or what is the context of where they're running and um is it a website is it a mini app uh what's actually happening. Um so the the easy answer is yeah far caster is just the rapper or the host of a website and they added some fancy sprinkles on top to make it easy to have the wallet connected. So, it's a social client, but it basically has a wallet baked in and it's automatically connected. And through this, you're skipping the annoying wallet connect part, the identifying with different uh services.

So, it's just a simple host where you run a website. So, all of these things run on versal uh for me and that means you just get a URL that you can post on the internet and other people can also use it. But if you open it on Farcaster, it has some special properties to uh run easier there to have some additional features. But you're not blocking people from accessing it. It's not exclusive. It's not iOS versus Android. It's just a link in the end. Yeah, very good question. So the the

question is I showed um yeah we vibe we vibe coded it away. Uh but in the beginning you saw the context of the user viewing the mini app and the question is is this verified? Is this authenticated? Um can people fake it? And yes people are faking it. the the initial loading of the page um you can fake it and just act as a different user which is helpful in debugging as well where I get user reports that something isn't working and I can log in as if I'm this user for simple tests but there is verification um there is signatures that can happen in the background there is a new um it's called quick authentication

from farcaster which can just happen in the background and through this you And you can check can you trust the user. Um which uh many apps are also called frames v2 uh which hints as there was a frames v1 where this was a huge problem. Many people were just spamming it and trying to yeah get to some airdrop uh which happens in crypto. And uh this quick authentication method and a bunch of other things help to actually authenticate the user uh often without them having to do an action which is also very nice. So to the user it still looks the same, but in the background you're doing a bunch of handshakes um that I didn't get into today um to keep it more vibe uh prompting uh focus. But

that's definitely a huge problem and there is some quick solutions. Yeah. Yeah. So, so the question was um if someone opens a mini app, can you see who else has already opened the mini app? Are your friends already kind of in the game on the circle in this location sharing mini app? whatever it might be.

Uh I'm not aware that there is a public API for this. Um so I don't think there is a public API from Farcast or from any of these other providers that can just easily tell you um if there's a Tinder like mini app and you would leak the data, hey all of these guys are also on this mini app there's some consequences uh to this. So, I'm not aware. Um, for what I'm doing, uh, if someone adds the mini app, um, as I, as I showed, if they add the mini app or pin it to the client, um, you just get a web hook request to, um, to to save in your database or

wherever you want to save it in key value store. Um, so through this I basically already know who has added it and I have this list and I can just also message people automatically or try to reach out to them. Hey, five of your friends are on this mini app. Do you also want to check it out? Or if they open it, I can show not this long list as we're showing here of people that I follow, but I can show them specifically, hey, these five people also have this app installed or they were recently active on this mini app. So because it's just a generic website, you can do these kind of things. Does that web hook still work in dev mode as well? Um so like it like the web hook will go back to the Cloudflare page

which goes to your laptop dev and that works. Yeah, great question. Yeah, for sure. Um so I didn't get into this part as well. There is um a domain association step which you have to do. Um I can just show it quickly here to to focus on this part. uh you have this title, but then below it, it says by Vibes Engineering. Vibes Engineering is just my dev test account. Here, to get to this step uh in a live um feed sharing system, you actually need to associate this mini app that you're hosting with your Farcaster account. And only then can you add uh mini apps to to a client or you can send notifications.

So, it's it's permissionless. You can just do it. You don't need to ask Farcaster to to help you with it, but you need to connect between any domain and um and a Farcaster account. And that's kind of a blocker. If you do this in your local dev setup and saying, "Hey, this Cloudflare domain is legit. I want to connect it to this mini app," then you can can do it. And many people do it because the web hook interactions and notifications should be tested in in staging and not straight in production. Uh how do I do that? Because I I did also add that add to caster button and it says invalid domain manifest which I guess is that exactly. Um yeah I think we have some time. Perfect. Let's get

into it. So currently um yeah let let me zoom out. Um there is a bunch of developer tools on uh that that Farcaster provides. So you just go to Farcaster and then it's uh slashdevelopers and you have a preview tool, you have an ambit tool and a manifest tool. And what we're talking about here is the manifest tool or domain association. And here you can just enter uh let's just use vibes engineering.

And here we can already see everything that I registered. And it says when it was last synced. It says it's not connected to this current account, but with a different one. I can see the preview of how it looks like if it's kind of a minimized um embed in in the feed or if it's a large one. And then you can see the full mini app configuration. There's a bunch of icons, images, text, uh splash, uh URL, and and color, and even um kind of app store- like categories and tags that you can add. Um all of this just lives in a in a JSON

file. Um this was the nice view to to look at it on Farcaster. Just to give you the full view, it's at It's always atwell minus known forecaster JSON. So for every domain that has a mini app, you need to have this file and it looks like this. So what I showed you before in the nice faras uh interface the raw data is just this and here you can see the structured data is in the frame and above that you need to do the account association which is connect this domain where this file

lives to an a farcaster account. Now the sad news is you need to do this on mobile. you need to generate the signature where your Farcast custody wallet actually lives and that's usually in the Farcast wallet if you didn't export it. Now we can get into many more details. Um so this uh header payload and signature is easy uh to generate in the mobile app. You enter your domain and it will do it for you and then you can just copy paste it um to to this um wellnown forecast.json file.

Um side note on features that are that are coming from Farcaster is this is the most annoying part. That's why I didn't get into it from the start. It's kind of a requirement to go into production, but to have your first mini app live, um it's it's more annoying than a requirement. Um Farcaster will offer a way for you to not do it and just point uh this file or redirect from this file to Farcaster. So they will host it for you and you will be able to manage it from um basically this manifest tool is not just right now it's read only and in the future it can also write and you can

change the data or associate it with a different account. Um so this will blow up and will be um or will be a bigger feature um than it is right now but currently you still need to do it manually. Let's give one more try to the to the V coding. Did you implement the features? This is the point when I'm too lazy to read all of the output and I'm just asking for TLDDR. Tell me what happened.

Yes, please implement it. Okay, maybe we maybe we'll run out of time. Um because we can't get enough tokens to quickly write the code for us now. Um so if we open this one, it still only shows uh our friends, which is nice. It's nice to see the people we follow, but it's it's still without the surface integration, which uh might take a while. Um, okay. Do we have any more questions?

Okay, let's give it five more minutes. If it will finish the feature, we can clap. Otherwise, we need to do a follow-up circus integration. Um, yeah, just to keep going. The workshop plan obviously was also VIP V by prompted. I ran into a bunch of

problems with the circles SDK. Let me find the SDK which is here. Um, so they have a nice um description and they have a bunch of things uh already explained. you can easily set it up with React. So, this was super helpful. But for the specific case of I'm looking for specific forecast, I'm looking for specific addresses that I know um people have and I want to check if they are on circles too. This obviously wasn't there. It's kind of a niche use case.

This is much more focused on setting people up with new circles profiles, inviting them, minting the circles, a bunch of different things. Um, so I had to go through this a bunch of times, try five different approaches, uh, where four didn't work and then the last one actually, um, I got to I got to get the data. Um, so the workshop plan already includes kind of all of this research and I just told it now that we solved the puzzle just use just use the working solution and don't uh try to do different things.

But maybe we have something else I can show in the meantime which is the demo demo circles. Well, it now also tells us it finished the feature. Let's see if it actually works. That would be a a great success. Let's go back to the main page. See what it does.

We lose the internet connection. Let's try this again with the new address. Yeah, I just restarted it.

Let's restart it again. So I'm wondering here it says compiled. Okay, we can see something. And we're checking circles. This is new. So far there are zero people on circles. We need to check all verified

Ethereum. I can't type anymore Ethereum addresses of the forecaster users, not just the primary one. Okay, we can obviously continue VIP coding for a long time. I think that's a good place to stop. We have the basic integration between um seeing the followers, refreshing it, checking if they are on circles. So far, we need to I think check that we're using all addresses to look up and not just the the main ones, which is a tiny hiccup.

And yeah, if you follow me on Farcaster, I'll just share this later once it's done. And any more questions?