KON
No-code On-chain App Framework
Demo
About
The problem it solves ## 🤔 Problem Although blockchain offers benefits like _Permissionless_ and _Composability_, its real-world use cases are still limited. - Creators and community managers face high technical barriers and a complex dApp setup process. - Hard-to-understand ideas like wallets and gas fees make it hard for people to get started. ## 💡 Solution __KON - "No-code On-chain App Framework"__ We aim to create something people can use daily without compromising UX while maintaining the benefits of on-chain. This project has been under development for some time. By the time this hackathon began, the following features were already in place: - Reading configuration from ENS Subnames, Text Records - Basic setup of a PWA (Progressive Web App) based on ENS configuration In this update, we've added the following new features: - XMTP group chat integration into app - Extended functionality via XMTP Agent: - Create app (claim ENS Subnames, set ENS TextRecords using XMTP Agent + AgentKit + Smart Wallet) - Create ERC-20 for app (using XMTP Agent + Smart Wallet) - App owner distributes app coin to users via message (XMTP Agent) - App users can request to redeem rewards with coin balance (EAS/NFT) __DEMOs__ - A Shop app __[Wassie Coffee]__: [App](https://wassiecoffee.kon.wtf), [ENS config](https://sepolia.app.ens.domains/wassiecoffee.kon.wtf?tab=records) - A Event app __[ETHTOKYO'25]__: [App](https://ethtokyo.kon.wtf), [ENS config](https://sepolia.app.ens.domains/ethtokyo.kon.wtf?tab=records) __Architecture__ - In media image and [here](https://github.com/buildwithkon/kon/blob/main/docs/20250606-base-batch-messaging-buildathon.md) ## 👍 Why KON? - __Easy to start__: With AI Agent, App owners can start their app in minutes. Users only need a smartphone with a Passkey. - __Ownership__: App owners and users fully control their apps and data—Apple or Google cannot remove them. That's why we chose a PWA. - __Composability__ : Extendable by templates, plugins, smart contracts and reusable on-chain data between apps. Moreover, app and user data are on-chain, and data composability also happens. For example - - An event participants get priority access to the following events - A shop member receiving discounts at another shop or location - Cross-store stamp rally event - __Cost__: Reusing templates, plugins, and smart contracts minimizes both initial and running costs. ## ✨ What's next - Integration with existing group chats and Farcaster miniapp, enabling a seamless experience from group chat <> KON app - More templates and feature additions, including voting, theming, crowdfunding, and more protocol integration - Public version to be released on Mainnet this summer > _Additional technical details are noted [here](https://github.com/buildwithkon/kon/blob/main/docs/docs/20250606-base-batch-messaging-buildathon.md)._
How it's made
Challenges we ran into - __XMTP agent design__: Initially designed to handle on-chain transactions directly by XMTP agent address, we later discovered, through further review of examples, that users can post messages that trigger those transactions. - __XMTP agent deployment__ : We had trouble deploying the XMTP Agent to run on a server. We ran XMTP Agent on localhost, which is connected to XMTP production network, but we plan to run it on a server soon. - __Multi-user app ownership__: For the case where the app has multiple owners, we explored using a multi-owner or multi-sig account to manage ENS Subnames. (XMTP group chat already has a multi-owner design.) We plan to support it in the future. I'm considering using [MultiOwnable functionality of Smart Wallet](https://github.com/coinbase/smart-wallet/blob/main/src/MultiOwnable.sol).