<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SQRT Labs Blog</title>
    <description>Engineering notes, product insights, and Web3 development guides from SQRT Labs team.</description>
    <link>https://sqrtlabs.com//blog</link>
    <language>en</language>
    <lastBuildDate>Sun, 19 Apr 2026 11:05:02 GMT</lastBuildDate>
    <atom:link href="https://sqrtlabs.com//blog/rss" rel="self" type="application/rss+xml"/>
    
    <item>
      <title><![CDATA[How to design a secure prediction market]]></title>
      <description><![CDATA[Prediction markets are one of the most interesting applications in DeFi. They allow users to bet on the outcome of real-world events, creating efficient price discovery mechanisms for everything from election results to sports outcomes. But designing a secure prediction market is harder than it looks. There are several attack vectors you need to consider, from oracle manipulation to front-running to collusion between market makers....]]></description>
      <link>https://sqrtlabs.com//blog/secure-prediction-market</link>
      <guid>https://sqrtlabs.com//blog/secure-prediction-market</guid>
      <pubDate>Thu, 20 Nov 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>DeFi & Protocol Design</category>
    </item>
    
    <item>
      <title><![CDATA[When to choose an L2 vs an appchain]]></title>
      <description><![CDATA[One of the most common questions we get from teams is whether they should deploy on an L2 or build their own appchain. The answer depends on several factors that we'll explore in this post. L2s like Arbitrum, Optimism, and Base offer the fastest path to market. You get instant access to existing liquidity, users, and infrastructure. For most applications, this is the right choice. The shared security model means you don't need to bootstrap your own validator set....]]></description>
      <link>https://sqrtlabs.com//blog/l2-vs-appchain</link>
      <guid>https://sqrtlabs.com//blog/l2-vs-appchain</guid>
      <pubDate>Sat, 15 Nov 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>Engineering Notes</category>
    </item>
    
    <item>
      <title><![CDATA[Common smart contract mistakes and how to avoid them]]></title>
      <description><![CDATA[After auditing and building dozens of smart contracts, we've seen the same mistakes come up again and again. Here are the most common ones and how to avoid them. Reentrancy remains the #1 vulnerability despite being well-known. The fix is simple: follow the checks-effects-interactions pattern and use reentrancy guards for any function that makes external calls. But developers still forget, especially in complex multi-contract systems....]]></description>
      <link>https://sqrtlabs.com//blog/smart-contract-mistakes</link>
      <guid>https://sqrtlabs.com//blog/smart-contract-mistakes</guid>
      <pubDate>Mon, 10 Nov 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>Engineering Notes</category>
    </item>
    
    <item>
      <title><![CDATA[Why Farcaster miniapps unlock new growth loops]]></title>
      <description><![CDATA[Farcaster miniapps (formerly frames) are changing how we think about distribution in web3. They embed directly into the social feed, creating viral loops that weren't possible before. Traditional web3 apps suffer from a cold start problem. Users need to leave the app they're in, connect their wallet, approve transactions, and complete actions. Each step loses users. Miniapps eliminate most of these friction points....]]></description>
      <link>https://sqrtlabs.com//blog/farcaster-growth-loops</link>
      <guid>https://sqrtlabs.com//blog/farcaster-growth-loops</guid>
      <pubDate>Wed, 05 Nov 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>Farcaster & Miniapps</category>
    </item>
    
    <item>
      <title><![CDATA[How to build mobile-first dApps without pain]]></title>
      <description><![CDATA[Most dApps are still desktop-first, but most users are on mobile. If you want mainstream adoption, you need to think mobile-first from day one. The biggest challenge is wallet connectivity. Mobile browsers don't support wallet extensions like desktop. You need to use WalletConnect or embedded wallets. We recommend supporting both—WalletConnect for power users, embedded wallets (like Privy or Dynamic) for new users....]]></description>
      <link>https://sqrtlabs.com//blog/mobile-first-dapps</link>
      <guid>https://sqrtlabs.com//blog/mobile-first-dapps</guid>
      <pubDate>Thu, 30 Oct 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>Product Thinking in Web3</category>
    </item>
    
    <item>
      <title><![CDATA[Real-world approaches to gas optimization]]></title>
      <description><![CDATA[Gas optimization is an art. Small changes can save users significant money, but premature optimization can make code unreadable and bug-prone. Here's how we approach it. Start by profiling. Use tools like Foundry's gas reports to understand where gas is actually being spent. Often, the expensive parts aren't where you'd expect. Storage operations, loops, and external calls are the usual culprits....]]></description>
      <link>https://sqrtlabs.com//blog/gas-optimization</link>
      <guid>https://sqrtlabs.com//blog/gas-optimization</guid>
      <pubDate>Sat, 25 Oct 2025 00:00:00 GMT</pubDate>
      <author>SQRT Labs Team</author>
      <category>Engineering Notes</category>
    </item>
    
  </channel>
</rss>