How Brendan Eich built the browser three times: Netscape, Firefox, and Brave

Executive overview

The open web's advertising infrastructure is built on third-party tracking — a problem baked into the browser since the first cookie in 1994. Brave blocks that infrastructure entirely, restoring page-load speed and battery life while giving users a direct economic stake in the ads they choose to see.

Eich has rebuilt the browser category three times: at Netscape (commercialising the web), at Mozilla (rescuing it from Microsoft), and now at Brave (reclaiming it from Google). Each time the incumbent grew too large to act in users' interests, a smaller, faster team filled the gap.

The browser is the universal app — whoever controls it controls the data feed for every human activity online.

From cookie to surveillance infrastructure

• The tracking vector existed from 1994: third-party image embeds plus cookies let any image server follow a user across every site.
• Netscape engineers knew it was a problem but couldn't break backwards compatibility; the genie was out of the bottle.
• Double-click (acquired by Google in 2008) was already running cross-site tracking in 1999.
• Mozilla's revenue dependence on the Google search deal created implicit pressure not to ship third-party cookie blocking.
• Google's 2016 privacy policy change and its 2018 silent sign-in across tabs were the clearest signals the model had fully turned against users.

Building Firefox: open source as competitive weapon

• After AOL bought Netscape and Microsoft won the first browser war via illegal bundling, the Mozilla codebase was the only escape pod.
• Firefox started as a pirate project inside Mozilla — Blake Ross, Dave Hyatt, Joe Hewitt — building a single-purpose browser on the XUL front-end stack.
• The 2003 roadmap ("one app, one thing") killed suite-ware thinking and unlocked the extension ecosystem — the first browser add-on marketplace, years before Chrome's.
• Distribution was entirely organic; the lead-user cohort of the early web acted as the growth engine.
• Google's search deal (0.9 era) funded Mozilla but also telegraphed Chrome: by 2006 Google was pulling engineers off Firefox.

Why Brave, and why now

• Chrome's dominance (claimed 2.65 billion users) is built on tracking users to fund Google's ad business — a structural conflict of interest baked into the product.
• Mobile made the cost visible: ad scripts drain battery, consume data plans, and sometimes prevent pages from loading at all.
• Brave's core proposition is speed from blocking, not a feature add; users feel the difference immediately.
• The chromium rebasing (end of 2018) removed the maintenance drag of the Electron fork and made extensions work — growth doubled five years in a row to 50 million MAU.

The Basic Attention Token and user-side economics

• Brave blocks all trackers by default; users who opt in to Brave Rewards receive 70% of ad revenue in BAT (Basic Attention Token).
• Ad matching happens entirely in-browser using a downloaded catalog — no user data leaves the device, no network tracks the download.
• KYC is required for payouts because of AML regulations; on-chain sends would fingerprint users through transaction patterns.
• The next-generation ad system (Themis, targeting Solana) uses zero-knowledge proofs so advertisers can verify performance without seeing any user data.
• Self-custody wallet is now native to the browser — more secure than a browser extension, and the foundation for peer-to-peer creator tipping without custodians.

Web3 strategy and the decentralisation trade-off

• Brave treats blockchains pragmatically: EVM compatibility spreads like Unix system calls — design DNA, not code — and Solana is the default for multi-chain dApps.
• Moxie Marlinspike's critique (centralisation is inevitable for usability) is largely correct; Brave's answer is cryptographic protocols that make centralised servers fairer, not replacing them.
• The hardest UX problem is the public/private key confusion: users treat seed phrases like passwords and share them; training will take as long as it took for credit cards.
• At 400 million users Brave would have standards leverage, pre-install negotiating power, and enough creator-side KYC to run fully on-chain peer-to-peer tipping.

Competitive risks

• Google and Apple control default placement on their platforms; paid distribution is expensive and organic growth has limits.
• DuckDuckGo has brand recognition and airport advertising; a privacy-on-privacy war benefits neither.
• Big tech could ship wallets in Chrome or Safari — but structural conflicts make genuine privacy features self-defeating for ad-funded browsers.
• Regulatory risk around crypto (US ban scenario) is real but hard to hedge; the growing number of wealthy holders makes an outright ban less likely.