Pro Tip — Caffeine ☕️ will switch on Web3 capabilities so apps (fully-onchain ICP dapps) can be created with trustless multi-chain capabilities and process and custody tokens like BTC, ETH, SOL and ICP, and even create new token ledgers. Here are the technical aspects of the work: 1. Currently Caffeine recycles "draft" app canisters/smart contracts when they aren't being used for efficiency reasons, so users don't need to pay cycles to maintain draft apps. Since it is the canisters that own/control tokens, recycling would currently result in a draft app losing its tokens — and in principle, the user who gets the recycled canister to work on their draft app would even be able to steal them. To solve this, once Caffeine payment features are turned on, we will add a special "Web3 App Mode" which allow users to permanently own the relevant draft canisters, like they do now for an app they published live. 2. We need to train the AI to implement good token processing and multi-chain patterns, in similar manner we train the AI to use the latest version of the Motoko language whenever we do a release. 3. We'll leverage use the new Motoko language "mix-in" feature, so that the AI can draw on stable DeFi code, rather than creating everything from scratch each time, so we need to start creating some mix-in libraries. Note that the usual guarantee that apps will never lose data on upgrades, which comes from special safety-rails we create for AI inside the Motoko framework, will mean apps never lose references to tokens on ledgers they reference. Objective: Use Caffeine to create fully onchain, trustless multi-chain apps. For example, want your apps to custody tokens? No problem. Want your app to interact with smart contracts on another chain? No problem. Concept: On whichever chain you create traditional DeFi smart contracts, it will be possible to use Caffeine to quickly build a fully onchain secure app functionality and user experience on top. (Decentralized control will also be possible.) Will take a little longer, but we'll get there, hopefully in Q1 next year. Edited: Apologises to those who added comments, there were some typos!