Intuition 👁️ (@0xIntuition): Builder Spotlight | Delegation Framework Tutorial by Zed

Builder Spotlight | Delegation Framework Tutorial by Zed You know when you have used a crypto wallet. You click something. A window pops up. Sign. Confirm. Pay a little gas. Click the next thing, and there is the window again. Every popup is your wallet going "you sure? But twenty of them in a row? Quite irritating. Meet @zedonchain_, a developer advocate. Most of the time, he writes tutorials for a living, and he actually likes it. Earlier this summer he was on an Intuition Dev community call and heard that MetaMask's delegation framework now runs on Intuition. But there was no walkthrough, so he pitched the idea to the DAO, and it went up on the missions board as Mission #09. To be clear, pitching a mission does not mean you get it. Once it went live, Zed applied like everyone else and was picked on his application. Before we get into what he built, a bit of context if you are new to Intuition. It makes the rest way easier to follow. One of the core primitives in Intuition is the claim, also known as “Triple”. A claim is three atoms linked together: [Subject] - [Predicate] - [Object], like [This Podcast] - [Is] - [Worth Your Time]. You back a claim by staking $TRUST on it. Support means you stake for it. Oppose means you stake against it. Want to withdraw? Take it out whenever. Normally, every one of those steps is a popup and a fee. That is what delegation is designed to solve. Delegating means letting something act on your behalf. Think of handing a friend a prepaid card. It only works at one shop, it has a daily limit, and you can cancel it whenever you feel like it. Your friend runs the errands. You do not sign anything. The "friend" here is a smart account: a second pocket that your wallet owns and that can follow instructions. The "shop" is Intuition's MultiVault, the contract holding $TRUST for each claim. The "one shop only" and "daily limit" bits are caveats, rules stuck to the permission that the chain checks every single time, no exceptions. The relayer is the app's own server. It sends each action and pays the fee, so you do not. And revoke just means cancel. That is the whole vocabulary. With that being said, let's look at what Zed actually shipped. One Click, One Signature Mission #09 asked for a full walkthrough of that loop: sign a permission, use it, cancel it. Zed built a real app called ClaimStream, a live feed of Intuition claims, and wrote the tutorial around it so anyone can rebuild the thing from scratch. Setup is four quick steps, each with a one-liner explaining what is happening, and the app will not move on until the last step is confirmed. Make your smart account. Drop some $TRUST in it. Authorize the smart account to deposit and withdraw on your behalf. Then sign the delegation — one free, off-chain signature that gives the app permission to support, oppose, or withdraw on your behalf, within your daily limit and only for the next 30 days. He could have crammed all of that into one big “Enable” button. He did not. The purpose of this app is educational, so the steps are kept separate on purpose. You get to see what is actually happening at each stage, understand what the user is approving, and then decide what you want to simplify in your own app. After that? Support is one click. Oppose is one click. Changed your mind? One click. No popups, no gas fees for the user. There is a little activity log at the bottom of the screen showing every action the relayer sent, with a link to the transaction, so nothing is happening behind your back. And the rules hold the whole time: only the vault, only support, oppose or withdraw, never past your daily cap, and everything lands in your own wallet no matter who hit send. Hit Disable and the delegated access stops, with whatever $TRUST is left swept straight back to you. "Delegated execution transforms web3 from a series of permission dialogs into an experience that feels like a standard application." Fine-Tuning The Experience Most tutorials only show the finished code. Zed also wrote down what broke along the way and how he fixed it, which is the part other developers might need. The spending limit used to be one lump for the whole month, so he made it a daily allowance that resets on its own. The Intuition network keeps its own clock, and it runs a couple of minutes behind real time, so the very first click kept getting rejected as "too early". He fixed it by starting the permission an hour in the past. And fast clicking sent several actions at once and they collided, so now they go out one by one. Small touches like these are exactly what make the difference between an app that works and one that looks broken. Why This Matters for the Ecosystem "For a protocol built on constant interaction like Intuition, this is the difference between an engaging user feed and users bouncing off the first popup." That is the whole point. Intuition is built for everyone. A popup on every tap, and the whole thing goes belly up. The tutorial is built to support any builder in the ecosystem: the same setup, one permission plus a server that sends the clicks, works for pretty much any action on Intuition, and it is written so you can lift it straight into your own app. The demo is live at https://delegation-demo.intuition.box/ The code and the written tutorial are open at https://github.com/intuition-box/intuition-delegation-tutorial-claimstream/blob/main/TUTORIAL.md and the video walkthrough is on its way. Go set it up, and click around! Missions Are Still Open Zed's tutorial came out of the missions program on https://intuition.box/missions, where builders grab a piece of the ecosystem and get paid to ship it. As we post this, these are open: Mission 04 · $500 · Create Onchain Ontology for Intuition Ecosystem Apps Mission 05 · $200 · graph.intuition.box Mainnet Migration + Reality Tunnel Mission 11 · $3,000 · ERC-7710 Liquid Democracy — Production Implementation Want in? Go to https://github.com/orgs/intuition-box/projects/21/views/1 and comment on the mission why it should be yours! For ongoing updates, follow @intuition_box, where you’ll find the latest news, opportunities, and updates on these missions. Builder or not, come hang out in the https://discord.gg/0xIntuition. It is where the people building on Intuition actually are, and where new opportunities show up first. Zed is in there, probably halfway through the next tutorial. Do not miss the next one. $TRUST the process