[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-ethereum-app-list-turns-discovery-into-map-en":3,"article-related-ethereum-app-list-turns-discovery-into-map-en":31,"series-blockchain-724d3162-99fa-485d-9079-08da868c62aa":78},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":23,"views":27,"created_at":28,"published_at":29,"topic_cluster_id":30},"724d3162-99fa-485d-9079-08da868c62aa","ethereum-app-list-turns-discovery-into-map-en","Ethereum.org’s app list turns discovery into a map","\u003Cp data-speakable=\"summary\">I turn \u003Ca href=\"\u002Ftag\u002Fethereum\">ethereum\u003C\u002Fa>.org’s app directory into a practical way to pick onchain tools.\u003C\u002Fp>\u003Cp>I've been using Ethereum apps long enough to know the problem isn't finding one app. It's figuring out which one I should trust for the job. Every directory claims to help, and then I end up with a pile of tabs: one for trading, one for bridging, one for privacy, one for docs, and somehow I still don't know what to open first. That gets old fast.\u003C\u002Fp>\u003Cp>So when I hit the \u003Ca href=\"https:\u002F\u002Fethereum.org\u002Fapps\u002F\">ethereum.org apps page\u003C\u002Fa>, I wasn't looking for inspiration. I was looking for structure. What I found was a pretty opinionated way to sort the ecosystem: not by hype, but by job. \u003Ca href=\"\u002Ftag\u002Fdefi\">DeFi\u003C\u002Fa>. Social. Bridge. Privacy. Productivity. DAO. Gaming. It sounds simple because it is simple, and honestly, that's why it works.\u003C\u002Fp>\u003Cp>This piece is me unpacking that structure the way I wish someone had done for me earlier. I'm not pretending ethereum.org invented app discovery. I'm saying they made a clean public map, and that map is useful if you want to stop treating every dapp like a random bookmark.\u003C\u002Fp>\u003Ch2>Stop browsing crypto apps like a junk drawer\u003C\u002Fh2>\u003Cblockquote>Discover a list of curated applications that run on Ethereum and layer 2 networks\u003C\u002Fblockquote>\u003Cp>What this actually means is: ethereum.org is not trying to sell you on one app. It is trying to give you a curated starting point. That matters because most of us do not need 400 options. We need a sane shortlist.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1783321413334-c7m0.png\" alt=\"Ethereum.org’s app list turns discovery into a map\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>I ran into this the hard way when I tried to explain Ethereum apps to a teammate who only wanted to do three things: swap tokens, bridge funds, and maybe try a social app without getting wrecked by fees. If I hand them a giant list of names, they freeze. If I hand them categories with examples, they can move.\u003C\u002Fp>\u003Cp>The page also makes an important choice by including \u003Ca href=\"\u002Ftag\u002Flayer-2\">layer 2\u003C\u002Fa> networks in the same breath. That tells me the directory is not pretending all useful activity happens on mainnet. It is acknowledging the actual user path: start on Ethereum, then go wherever the app and fee profile make sense.\u003C\u002Fp>\u003Cp>How to apply it: build your own app shortlist the same way. I keep one note with five buckets: trading, bridging, identity\u002Fprivacy, collaboration, and governance. When a new app shows up, I ask which bucket it belongs in before I ask whether it is trendy.\u003C\u002Fp>\u003Cul>\u003Cli>Start with the job, not the brand.\u003C\u002Fli>\u003Cli>Prefer curated lists over endless search.\u003C\u002Fli>\u003Cli>Separate “interesting” from “useful” immediately.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>DeFi is not one thing, and the directory says so\u003C\u002Fh2>\u003Cblockquote>DeFi is a category of decentralized applications that allow users to lend, borrow, trade, and earn interest on their crypto assets.\u003C\u002Fblockquote>\u003Cp>That definition is boring in the best way. It avoids the usual crypto fog and just says what people do. Lend. Borrow. Trade. Earn. I wish more project pages had that discipline, because otherwise you end up with apps that sound like a thesis and behave like a casino.\u003C\u002Fp>\u003Cp>On the page, ethereum.org highlights apps like \u003Ca href=\"https:\u002F\u002F1inch.io\u002F\" rel=\"noreferrer\">1inch\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fcompound.finance\u002F\" rel=\"noreferrer\">Compound\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Faave.com\u002F\" rel=\"noreferrer\">Aave\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fapp.uniswap.org\u002F\" rel=\"noreferrer\">Uniswap\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fsky.money\u002F\" rel=\"noreferrer\">Sky\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fethena.fi\u002F\" rel=\"noreferrer\">Ethena\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fpendle.finance\u002F\" rel=\"noreferrer\">Pendle\u003C\u002Fa>. That is a useful spread because it shows DeFi is not just “swap tokens and pray.” It includes aggregation, lending, stablecoin issuance, and yield strategies.\u003C\u002Fp>\u003Cp>What this actually means is that a category label is only useful if it changes your behavior. If I need the best route for a swap, I do not open a lending app. If I want to park collateral and borrow, I do not start in a DEX. The category saves me from using the wrong tool for the job.\u003C\u002Fp>\u003Cp>I’ve watched people treat DeFi like one giant interface. That is how you get confused, overexposed, and weirdly loyal to the wrong protocol. The directory nudges you away from that habit by making the sub-jobs visible.\u003C\u002Fp>\u003Cp>How to apply it: when you build or document a DeFi stack, split the flow into smaller verbs. Swap, lend, borrow, earn, issue, route. Then assign one app per verb if possible. The moment one app tries to do everything, your docs and your users both get messy.\u003C\u002Fp>\u003Cul>\u003Cli>Use verbs to classify DeFi tools.\u003C\u002Fli>\u003Cli>Separate routing from execution.\u003C\u002Fli>\u003Cli>Document risk separately from convenience.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Social apps only work when identity is part of the product\u003C\u002Fh2>\u003Cblockquote>Social is a category of decentralized applications that allow users to connect with others and share content.\u003C\u002Fblockquote>\u003Cp>I like this framing because it does not pretend crypto social is just “Twitter, but onchain.” It points at connection and content, which are the actual primitives. On the page, ethereum.org highlights \u003Ca href=\"https:\u002F\u002Ffarcaster.xyz\u002F\" rel=\"noreferrer\">Farcaster\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fzora.co\u002F\" rel=\"noreferrer\">Zora\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Frodeo.xyz\u002F\" rel=\"noreferrer\">Rodeo\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Ftowns.com\u002F\" rel=\"noreferrer\">Towns\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Forb.club\u002F\" rel=\"noreferrer\">Orb\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Finterface.social\u002F\" rel=\"noreferrer\">Interface\u003C\u002Fa>. That mix tells me the category is broader than posting hot takes.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1783321412313-19jf.png\" alt=\"Ethereum.org’s app list turns discovery into a map\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>What this actually means is that social apps on Ethereum are often really identity systems with a feed attached. Some are publishing tools. Some are communities. Some are trading-adjacent. Some are closer to messaging. The directory is smart to keep those together because users usually discover them through behavior, not protocol purity.\u003C\u002Fp>\u003Cp>I ran into this when I tried to explain Farcaster to someone who only knew “social network” as a feed. They kept asking, “So is it like X?” That question misses the point. The useful question is: what happens when identity, posting, and distribution are portable across apps?\u003C\u002Fp>\u003Cp>If you're designing around social on Ethereum, stop thinking in terms of one monolithic timeline. Think in terms of identity, audience, and content objects. The app list makes that easier because it shows multiple flavors of social instead of one canonical answer.\u003C\u002Fp>\u003Cp>How to apply it: if you're building or evaluating a social product, map three things first. How do users sign in? What do they publish? Where does the content live? If you can't answer those cleanly, the product is probably still pretending to be social rather than being social.\u003C\u002Fp>\u003Ch2>Bridges are the plumbing nobody wants to talk about\u003C\u002Fh2>\u003Cblockquote>Bridge is a category of decentralized applications that allow users to bridge their assets between different networks.\u003C\u002Fblockquote>\u003Cp>This is the least glamorous category on the page and probably one of the most important. The directory includes \u003Ca href=\"https:\u002F\u002Fbungee.exchange\u002F\" rel=\"noreferrer\">Bungee\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.layerswap.io\u002F\" rel=\"noreferrer\">Layerswap\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fhop.exchange\u002F\" rel=\"noreferrer\">Hop\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fstargate.finance\u002F\" rel=\"noreferrer\">Stargate\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.across.to\u002F\" rel=\"noreferrer\">Across\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fwww.particle.network\u002F\" rel=\"noreferrer\">Particle Network\u003C\u002Fa>. That is exactly the kind of list I want when I need to move value without reading five threads and hoping for the best.\u003C\u002Fp>\u003Cp>What this actually means is that bridging is not a side quest. It is part of the normal user journey on Ethereum and layer 2s. If you use apps across networks, you are already depending on bridge UX whether you admit it or not.\u003C\u002Fp>\u003Cp>I’ve had the usual bridge pain: wrong network, wrong asset format, waiting too long, then trying to remember why I trusted a random interface with money in the first place. A curated directory helps because it reduces the discovery problem. It does not remove risk, but it at least stops me from starting with a search engine full of junk.\u003C\u002Fp>\u003Cp>How to apply it: put bridge choice in your onboarding docs. If your app depends on cross-network users, name the preferred bridge, explain why, and show the failure mode. If you are writing internal docs, include a “where do funds need to live before this step?” section. That question saves time and mistakes.\u003C\u002Fp>\u003Cp>Also, I’d treat bridge selection as a product decision, not a user afterthought. The directory’s placement of bridges alongside other app types is a reminder that movement is part of the workflow, not a hidden backend detail.\u003C\u002Fp>\u003Ch2>Privacy and productivity are the same conversation more often than people admit\u003C\u002Fh2>\u003Cblockquote>Privacy is a category of decentralized applications that allow users to be private.\u003C\u002Fblockquote>\u003Cp>This line is plain, which is why I trust it more than a lot of privacy marketing. The page surfaces \u003Ca href=\"https:\u002F\u002Fprivacy-pools.org\u002F\" rel=\"noreferrer\">Privacy Pools\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Ffluidkey.com\u002F\" rel=\"noreferrer\">Fluidkey\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.railgun.org\u002F\" rel=\"noreferrer\">Railgun\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Frarimo.com\u002F\" rel=\"noreferrer\">Rarimo\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.tornadocash.com\u002F\" rel=\"noreferrer\">Tornado Cash\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fquarkid.org\u002F\" rel=\"noreferrer\">QuarkID\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fzkpassport.xyz\u002F\" rel=\"noreferrer\">ZK Passport\u003C\u002Fa>. Those are not interchangeable tools, and the page does not pretend they are.\u003C\u002Fp>\u003Cp>What this actually means is that privacy on Ethereum spans payments, identity, and compliance patterns. That is a lot broader than “hide the transaction.” The directory keeps these apps visible because privacy is not a niche preference. It is part of how people work, pay, and collaborate without spraying data everywhere.\u003C\u002Fp>\u003Cp>Then there is productivity. The page includes \u003Ca href=\"https:\u002F\u002Fdocs.fileverse.io\u002F\" rel=\"noreferrer\">Fileverse dDocs\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdsheets.new\u002F\" rel=\"noreferrer\">Fileverse dSheets\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fens.domains\u002F\" rel=\"noreferrer\">ENS\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fhuddle01.com\u002F\" rel=\"noreferrer\">Huddle01\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Flivepeer.org\u002F\" rel=\"noreferrer\">Livepeer\u003C\u002Fa>. I like that pairing because it shows a boring truth: once you care about privacy, you start caring about collaboration, storage, identity, and media too.\u003C\u002Fp>\u003Cp>I ran into this when I was trying to review a draft with someone who did not want the document floating around in a bunch of cloud tabs. The usual doc stack was too open, too permissioned in the wrong way, and too dependent on accounts nobody wanted to manage. A privacy-first doc tool is not a luxury in that case. It is the actual requirement.\u003C\u002Fp>\u003Cp>How to apply it: do not treat privacy as a bolt-on. If the workflow includes sensitive data, make privacy a first-class category in your app stack. And if you are choosing a collaboration tool, ask whether identity, storage, and access control are designed together or just glued on later.\u003C\u002Fp>\u003Ch2>DAO and gaming categories tell you who the app is for\u003C\u002Fh2>\u003Cblockquote>DAO is a category of decentralized applications that allow users to govern and create decentralized autonomous organizations.\u003C\u002Fblockquote>\u003Cp>This is where the page gets useful for teams, not just individual users. The DAO section points to \u003Ca href=\"https:\u002F\u002Fsnapshot.box\u002F\" rel=\"noreferrer\">Snapshot\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.tally.xyz\u002F\" rel=\"noreferrer\">Tally\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.hatsprotocol.xyz\u002F\" rel=\"noreferrer\">Hats Protocol\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Faragon.org\u002F\" rel=\"noreferrer\">Aragon\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fdaohaus.club\u002F\" rel=\"noreferrer\">DAOhaus\u003C\u002Fa>. That spread covers voting, permissions, creation, and treasury-ish coordination. In other words: not just governance theater.\u003C\u002Fp>\u003Cp>What this actually means is that DAO tools are not about “having a DAO.” They are about who can act, who can vote, and how decisions move. If you have ever watched a team argue about permissions in a Discord thread for three days, you already know why this matters.\u003C\u002Fp>\u003Cp>The gaming section is smaller but still helpful. Ethereum.org points to projects like \u003Ca href=\"https:\u002F\u002Faavagochi.com\u002F\" rel=\"noreferrer\">Aavagochi\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fbattlebears.com\u002F\" rel=\"noreferrer\">Battle Bears\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fblobarena.com\u002F\" rel=\"noreferrer\">Blob Arena\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fcambria.gg\u002F\" rel=\"noreferrer\">Cambria\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fdarkforest.game\u002F\" rel=\"noreferrer\">Dark Forest\u003C\u002Fa>. That tells me gaming on Ethereum is still a mixed bag of experiments, strategy, and community-heavy experiences, which is probably the honest way to present it.\u003C\u002Fp>\u003Cp>How to apply it: if you are building for a team or community, do not start with “What DAO tool should we use?” Start with “Who gets to do what?” Then choose voting, permissions, treasury, or creation tooling based on that answer. For games, apply the same logic: what is onchain, what is offchain, and what part of the experience actually benefits from Ethereum?\u003C\u002Fp>\u003Ch2>The directory is really a workflow, not a catalog\u003C\u002Fh2>\u003Cp>Here is the part I think people miss. The page is not just a list of apps. It is a workflow map. It starts with categories, adds examples, then nudges you toward the right layer 2 or bridge when needed. That is a much more useful mental model than “here are some dapps.”\u003C\u002Fp>\u003Cp>The category pages also help with team communication. If I am writing a product brief, I can point at the same buckets ethereum.org uses and everyone immediately understands the shape of the problem. That saves me from inventing new labels just to sound clever.\u003C\u002Fp>\u003Cp>There is also a quiet editorial decision here: the page includes community picks and a path for suggesting new apps. That means the directory is not frozen. It is curated, but not closed. I like that balance. Closed lists go stale. Open lists become junk. This one sits in the middle, which is where useful reference material usually lives.\u003C\u002Fp>\u003Cp>How to apply it: when you document your own stack, organize it by user jobs and keep a feedback path open. If the list is internal, add a way for teammates to suggest replacements. If it is public, add a short note on why each app is there. Otherwise your “curation” becomes a pile of stale links with a nice header.\u003C\u002Fp>\u003Ch2>The template you can copy\u003C\u002Fh2>\u003Cpre>\u003Ccode># Ethereum app picker template\n\nUse this when you need to choose an onchain app without getting lost in brand noise.\n\n## 1) Start with the job\nWrite the user job in one sentence.\n\nExamples:\n- I need the best route to swap tokens.\n- I need to borrow against collateral.\n- I need a private way to move funds.\n- I need a collaborative doc with stronger access control.\n- I need a voting tool for a DAO.\n\n## 2) Put the job into a category\nChoose one:\n- DeFi\n- Social\n- Bridge\n- Privacy\n- Productivity\n- DAO\n- Gaming\n- Collectibles\n\n## 3) Pick the app type, not just the app\nAsk which sub-job matters most.\n\n### DeFi\n- Swap\n- Aggregate routes\n- Lend\n- Borrow\n- Earn yield\n- Issue stablecoins\n\n### Social\n- Post\n- Publish\n- Message\n- Build identity\n- Build community\n\n### Bridge\n- Move assets across networks\n- Reduce fees\n- Shorten transfer time\n- Support multiple chains\n\n### Privacy\n- Private payments\n- Private identity\n- Private collaboration\n- Compliance-aware privacy\n\n### Productivity\n- Docs\n- Spreadsheets\n- Identity\n- Video\n- Storage\n\n### DAO\n- Vote\n- Create an org\n- Manage permissions\n- Manage treasury\n- Coordinate proposals\n\n## 4) Write the selection criteria\nUse this checklist:\n- What network does it run on?\n- Does it require a layer 2?\n- What is the trust model?\n- What data does it expose?\n- What is the failure mode?\n- What happens if the bridge or wallet breaks?\n- What happens if the app disappears?\n\n## 5) Add one recommended tool per job\nKeep it short.\n\nExample:\n- Swap: 1inch or Uniswap\n- Borrow: Aave or Compound\n- Bridge: Bungee or Across\n- Social: Farcaster or Interface\n- Privacy: Privacy Pools or Railgun\n- Productivity: dDocs or dSheets\n- DAO: Snapshot or Tally\n\n## 6) Document the workflow\nWrite the exact path a user should follow.\n\nExample:\n1. Connect wallet\n2. Bridge funds if needed\n3. Open the app\n4. Complete the action\n5. Confirm the result onchain\n\n## 7) Keep a review note\nEvery month, check:\n- Is the app still maintained?\n- Is the UX still acceptable?\n- Did the network or fee situation change?\n- Is there a better app for this job now?\n\n## 8) Copy this into a team doc\n\n### Onchain app decision record\n- User job:\n- Category:\n- App type:\n- Recommended app:\n- Backup app:\n- Network:\n- Bridge needed:\n- Privacy impact:\n- Failure mode:\n- Review date:\n\u003C\u002Fcode>\u003C\u002Fpre>\u003Cp>That template is the part I would actually steal. It turns ethereum.org’s directory into a decision tool instead of a passive list. And that is the whole point: less browsing, more choosing.\u003C\u002Fp>\u003Cp>Source attribution: I based this breakdown on ethereum.org’s apps page at \u003Ca href=\"https:\u002F\u002Fethereum.org\u002Fapps\u002F\">https:\u002F\u002Fethereum.org\u002Fapps\u002F\u003C\u002Fa>. The structure and app examples are theirs; the framing, commentary, and template above are mine.\u003C\u002Fp>","I break down ethereum.org’s app directory and turn it into a copyable way to organize DeFi, social, privacy, gaming, and DAO tools.","ethereum.org","https:\u002F\u002Fethereum.org\u002Fapps\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1783321413334-c7m0.png","blockchain","en","a41b65c1-9f7d-43f3-918d-3924d208918b",[17,18,19,20,21,22],"Ethereum","dapps","DeFi","bridges","privacy","DAO",[24,25,26],"Organize apps by user job, not by hype.","Use category labels to narrow the right tool fast.","Turn a directory into a repeatable decision template.",0,"2026-07-06T07:03:04.899413+00:00","2026-07-06T07:03:04.888+00:00","df7d1853-cd8b-4823-aa64-1e6ef7b4f342",{"tags":32,"relatedLang":37,"relatedPosts":41},[33,35],{"name":34,"slug":34},"ethereum",{"name":19,"slug":36},"defi",{"id":15,"slug":38,"title":39,"language":40},"ethereum-app-list-turns-discovery-into-map-zh","Ethereum app list 把探索變成地圖","zh",[42,48,54,60,66,72],{"id":43,"slug":44,"title":45,"cover_image":46,"image_url":46,"created_at":47,"category":13},"d1c22e39-5093-47cd-9dad-be2dde630a98","celestia-fibre-targets-1tbps-blockspace-en","Celestia’s Fibre push targets 1 Tb\u002Fs blockspace","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782952396101-suvh.png","2026-07-02T00:32:54.528817+00:00",{"id":49,"slug":50,"title":51,"cover_image":52,"image_url":52,"created_at":53,"category":13},"31ba71cf-be60-46b9-bc43-0962f1c7f357","ai-utility-tokens-presale-marketing-not-infrastructure-en","AI utility tokens are still just presale marketing, not infrastructure","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782899271246-aapl.png","2026-07-01T09:47:22.653445+00:00",{"id":55,"slug":56,"title":57,"cover_image":58,"image_url":58,"created_at":59,"category":13},"325b4935-72e4-4db3-adc7-d5df1888b60d","web3-identity-dids-vcs-ai-agent-wallets-en","Web3 identity adds DIDs, VCs, and AI agent wallets","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782891175422-58g3.png","2026-07-01T07:32:26.92722+00:00",{"id":61,"slug":62,"title":63,"cover_image":64,"image_url":64,"created_at":65,"category":13},"4ff4dd4a-b930-4176-a495-292c76f6a368","sleepagotchi-private-ai-wellness-sleep-token-en","Sleepagotchi bets on private AI wellness and SLEEP token","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782890290105-c44a.png","2026-07-01T07:17:40.126495+00:00",{"id":67,"slug":68,"title":69,"cover_image":70,"image_url":70,"created_at":71,"category":13},"ca6a5042-52f6-415c-ad29-59c11497636e","fund-tokenization-services-onchain-rails-en","Fund tokenization services turn funds into on-chain rails","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782817408329-inkt.png","2026-06-30T11:03:06.046255+00:00",{"id":73,"slug":74,"title":75,"cover_image":76,"image_url":76,"created_at":77,"category":13},"44a145f0-e893-4e6e-b55e-b1a940ef5d99","stablecoin-boom-policy-limits-central-bank-warning-en","The stablecoin boom is colliding with policy limits","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782791267351-822g.png","2026-06-30T03:47:24.737728+00:00",[79,84,89,94,99,104,109,114,119,124],{"id":80,"slug":81,"title":82,"created_at":83},"cdf2780b-1da6-4aca-a87b-f0974b815b03","moonpay-open-wallet-standard-ai-payments-en","MoonPay's Open Wallet Standard Targets AI Payments","2026-03-28T03:08:33.547032+00:00",{"id":85,"slug":86,"title":87,"created_at":88},"f06da3a4-3b15-4c7b-a250-6077505f5119","next-gen-crypto-simulators-ai-web3-training-en","Next-Gen Crypto Simulators Are Getting Smarter","2026-04-01T09:36:34.200192+00:00",{"id":90,"slug":91,"title":92,"created_at":93},"0794f597-b908-402a-b660-729034ffdbf6","rtk-cuts-claude-code-token-spend-en","RTK cuts Claude Code token spend fast","2026-04-01T10:24:29.50277+00:00",{"id":95,"slug":96,"title":97,"created_at":98},"5101ffbf-7ea9-4baa-b5e2-64729ff55b20","openclaw-flaw-exposes-ai-admin-hijack-risk-en","Openclaw Flaw Exposes AI Admin Hijack Risk","2026-04-01T13:12:33.481569+00:00",{"id":100,"slug":101,"title":102,"created_at":103},"fadea65e-f7c8-41b0-a186-809d21787b4c","how-web3-marketing-changed-in-2026-en","How Web3 Marketing Changed in 2026","2026-04-02T01:36:36.504086+00:00",{"id":105,"slug":106,"title":107,"created_at":108},"88f88741-ff27-41d1-8151-776d0afb9508","ai-agentic-defi-web3-grants-march-2026-en","AI, Agentic DeFi, and Web3 Grants to Watch","2026-04-02T05:51:37.696422+00:00",{"id":110,"slug":111,"title":112,"created_at":113},"43fafe43-772e-48c8-bb95-da8d64cf60e3","why-crypto-is-fixated-on-ai-agents-en","Why Crypto Is Fixated on AI Agents","2026-04-02T05:54:29.121481+00:00",{"id":115,"slug":116,"title":117,"created_at":118},"320ef5e4-fe56-47ab-9a92-290d6fbd3f60","web3-explained-what-it-is-why-it-matters-en","Web3 Explained: What It Is and Why It Matters","2026-04-02T06:15:33.001112+00:00",{"id":120,"slug":121,"title":122,"created_at":123},"f49cffaf-2c57-4f48-9486-7062cca91ba0","trust-wallet-ai-trading-agents-220m-users-en","Trust Wallet Adds AI Trading Agents for 220M Users","2026-04-02T06:24:28.043029+00:00",{"id":125,"slug":126,"title":127,"created_at":128},"2b8501e2-39af-4de3-ade1-29616a58e9fb","trust-wallet-agent-kit-ai-trade-25-chains-en","Trust Wallet's Agent Kit Lets AI Trade on 25+ Chains","2026-04-02T06:27:33.425312+00:00"]