Open julien51 opened 1 month ago
Assumptions (which can be revised later):
Hi @julien51, here's a breakdown of the plan based on our chat and the research I've done:
Custom Hook Implementation: Create custom hooks to trigger actions when a cast is submitted to a specific channel. Hook Trigger: New cast detected on the designated channel.
Data Extraction:
Validation & Action:
Notes:
Currently, DC doesn't allow frame rendering, but this feature is coming soon, so I'll build the application with that in mind to enable a smoother purchase flow in the future.
Instead of a DM, can we just send an @reply to the user (outside of any channel) ? This way that would render as a frame...
Yes, we can. To confirm, you'd like the bot to create a public cast (not on the channel) that tags the user, including a frame to do the purchase flow, instead of sending a DM. Is that right?
@nestorbonilla please post updates here :)
Yes, we can. To confirm, you'd like the bot to create a public cast (not on the channel) that tags the user, including a frame to do the purchase flow, instead of sending a DM. Is that right?
That is right! In fact the frame can be "generic" (and we may let the "owner" of the channel" customize it in the future) because is the the same one that every user will user to "purchase" their membership).
Great, sharing some updates:
Custom Hooks: Implementation complete for triggering actions on new casts to a specific channel. Next Up: Scalability. I'm opting to use a hook per channel for now, while still exploring options for more dynamic multi-channel management in the future.
@botname setup
. The bot will reply with an embedded frame for chain, contract, and referral selection to gate main feed access.Sharing some updates:
Next Steps:
The goal here is to create an application that would integrate completely in the Farcaster ecosystem, thru both channels and frames (and maybe actions).
Let's start with user stories:
@nestorbonilla