# Earnify — Publisher Revenue Infrastructure v2.4.1
> **Unshackle your revenue.** Convert idle CPU cycles into deterministic yield. Zero tracking pixels. Zero invasive ads. Pure compute monetization. Open source forever.

https://earnify.cc

---

## Why Earnify Exists

The ad-supported web is collapsing under its own weight. Publishers face a triple assault: 42.7% of users deploy ad-blockers (Statista 2024), CPM rates decline year-over-year as programmatic supply floods the market (eMarketer 2024), and $12.4 billion in annual revenue evaporates to ad-blocking, consent fatigue, and regulatory compliance overhead worldwide (PageFair Report). GDPR fines, cookie deprecation, and consent banners punish publishers while enriching ad-tech intermediaries who deliver sub-40% fill rates on non-premium inventory.

Earnify replaces this broken model entirely. Instead of selling user attention through a labyrinth of trackers, auctions, and intermediaries that skim value at every hop, Earnify establishes a direct mathematical link between user engagement time and publisher revenue. Every second a visitor spends on your site becomes a measurable, monetizable unit of compute. No consent banners. No cookie walls. No IAB framework. No middlemen taking 50-70% of your inventory value before you see a cent.

The result: **100% fill rate across every session, immune to ad-blockers, compliant with privacy regulation by design, and fully open source.**

---

## Core Differentiators

### Zero-Data Footprint
Earnify processes no personal data. None. Ever. Zero cookies. Zero localStorage access. Zero browser fingerprinting. Zero tracking pixels. The miner receives work units from a stratum pool, computes hashes in isolated Web Workers, and submits valid shares. That is the entire data flow. There is no user identifier in the protocol, no session tracking, and no behavioral analytics. This architectural choice means Earnify operates entirely outside the scope of GDPR consent mandates, CCPA disclosure obligations, and ePrivacy Directive cookie restrictions. Your legal exposure from this integration is functionally zero.

### 100% Fill Rate — Guaranteed
Display advertising suffers from unfilled impressions, viewability thresholds, bid flooring, and geo-based rate discrimination. Earnify has no fill rate — because there are no impressions to fill. Every active browser session contributes compute. Every second of engagement translates to hashes. There is no auction to lose, no floor price to miss, and no geo-tier that prices your traffic at zero. The economic relationship is purely computational: session duration × hashrate × network reward = publisher earnings.

### Immune to Ad-Blockers
Standard Web Workers executing WebAssembly hashing are indistinguishable from legitimate application logic to content blockers. There is no domain to blacklist, no request pattern to fingerprint, and no tracking beacon to intercept. While ad-blockers strip 42.7% of display revenue from publishers, Earnify operates on a completely separate layer of the browser runtime that content blockers cannot and do not target. This alone recovers revenue from nearly half of your audience that display advertising cannot reach.

### Radically Transparent Economics — 10% Flat Fee
Coinhive took 30%. Intermediaries in programmatic advertising frequently extract 50-70% before publishers see revenue. Earnify takes 10%. Flat. No volume tiers that mysteriously shift. No "platform adjustments" that reduce payouts after the fact. No hidden data monetization. You configure your own wallet address and pool credentials. Shares are submitted directly from the browser to your pool. Earnify deducts exactly 10% of submitted shares at the protocol level. 90% of every hash your users compute lands in your wallet. The code that enforces this is open source and auditable.

### Fully Open Source — Every Line Auditable
The entire miner library, the landing page, the demo, the blog — all of it lives in a public GitHub repository under the MIT license. You can audit the fee enforcement logic. You can verify that no data exfiltration code exists. You can fork it, modify it, and self-host your own distribution. There is no black-box service dependency that could shut down, pivot pricing, or rug-pull your revenue stream. Self-hosted. Pool-agnostic. Runs as long as stratum pools exist.

### Direct Pool Connection — No Intermediary
Browsers running Earnify connect directly to your configured mining pool via WebSocket stratum. Earnify operates no proxy servers, no relay infrastructure, and no centralized mining coordinator that could become a single point of failure. You bring your own pool credentials and wallet address. Shares flow directly from visitor browsers to the pool. Payouts flow from the pool to your wallet. Earnify sits nowhere in the value chain — it is a client-side library, nothing more.

### Pool-Agnostic Architecture
Earnify connects to any pool supporting Stratum V1 over WebSocket. Tested and confirmed working with zpool.ca, Mining Dutch, Zergpool, and custom/private pools. Auto-exchange pools let you receive payouts in RVN, BTC, LTC, or any supported currency. Multi-region failover keeps mining operational even when individual pool endpoints experience degraded service. You are never locked into a single pool or a single coin.

---

## Technical Architecture

### The Compute Pipeline
Earnify's mining lifecycle follows a four-stage pipeline designed for zero main-thread interference:

**01 — Bootstrap:** The ES module loads asynchronously via a standard `<script type="module">` import. On initialization, it probes `navigator.hardwareConcurrency` for available logical cores, detects device type (mobile/tablet/desktop), and checks the Battery Status API to inform dynamic throttling decisions. No blocking network requests. No DOM parsing delay.

**02 — Spawn:** Dedicated Web Workers are instantiated — one per allocated thread, up to `n−1` cores where `n = hardwareConcurrency`. The primary UI core is always reserved for DOM rendering, event handling, and browser compositing. Each worker loads a WebAssembly module containing the compiled hashing kernel. Workers operate in fully isolated execution contexts with no shared mutable state.

**03 — Compute:** Workers receive stratum job assignments (block header, target difficulty) via the main-thread WebSocket relay. Each worker iterates through the nonce space computing cryptographic hashes against the difficulty target. When a worker finds a hash meeting or exceeding the target difficulty, it queues the valid share for submission. Workers consume approximately 2 MB of memory each under the MinotaurX algorithm. All computation happens off the main thread.

**04 — Payout:** Valid shares are transmitted back through the WebSocket connection to the configured stratum pool. The pool validates every share against the current job parameters. Valid shares are credited to the worker identity associated with your wallet. Payouts follow the pool's configured schedule and minimum threshold. The 10% platform fee is deducted at share-submission time — 9 out of every 10 valid shares are submitted with your wallet address; the 10th is submitted with Earnify's address.

### Supported Algorithms
| Algorithm | Status | Characteristics |
|-----------|--------|----------------|
| **MinotaurX** | Default — most profitable | ASIC-resistant, CPU-optimized, designed for browser execution via WASM |
| **Power2B** | Supported | High-throughput hashing, efficient on modern x86_64 with SIMD |
| **YesPower** | Supported | CPU-friendly proof-of-work, low memory footprint per worker |
| **Yescrypt** | Supported | Memory-hard key derivation adapted for proof-of-work contexts |
| **GhostRider** | Supported | Multi-algorithm chain, resistant to FPGA acceleration |
| **VerusHash** | Supported | Quantum-resistant hash function, optimized for consumer CPUs |
| **Flex** | Supported | Adaptive difficulty algorithm for heterogeneous device fleets |
| **RandomX** | Coming soon | Monero's ASIC-resistant algorithm, memory-hard, 2 GB dataset |
| **CryptoNight-R** | Coming soon | ASIC-resistant, well-suited for low-power devices |

### Technical Specifications
| Spec | Value |
|------|-------|
| Execution environment | Web Workers (dedicated, isolated context) |
| Hashing runtime | WebAssembly (WASM) compiled from C/C++ hashing kernels |
| Network protocol | Stratum V1 over WebSocket (RFC-compliant) |
| Thread allocation | 1 to `n−1` threads (default: `hardwareConcurrency − 1`) |
| Memory per worker | ~2 MB (MinotaurX), varies by algorithm |
| Bundle size | ~1 MB (uncompressed), cachable via CDN |
| Main-thread overhead | <2% (measured via Chrome DevTools Performance panel) |
| Bandwidth consumption | <1 KB/s (stratum packets: 200–400 bytes; share submissions: <150 bytes) |
| Battery drain | ~8%/hour at full utilization (auto-throttled via Battery Status API) |

### Browser Compatibility
| Browser | Minimum Version | Notes |
|---------|----------------|-------|
| Chrome / Edge | 80+ | Full Web Worker + WASM support. Primary test target. |
| Firefox | 78+ | Full support. Slightly lower WASM throughput on complex kernels. |
| Safari | 14+ | Full support. All features functional including Battery API. |
| Brave | Latest | Shields do not block Web Workers or WASM. Fully compatible. |
| Opera | 67+ (Chromium-based) | Full support. |
| Samsung Internet | 13+ (Chromium-based) | Full support. |

### Cross-Device Benchmark Data (MinotaurX, Real-World Measurements)
| Device Class | Avg. Hashrate | Active Threads | Reserved Cores |
|-------------|---------------|----------------|----------------|
| Desktop (8-core, x86_64) | 1,870 H/s | 7 of 8 | 1 core reserved for UI |
| Laptop (4-core, x86_64) | 740 H/s | 3 of 4 | 1 core reserved for UI |
| Tablet (6-core, ARM) | 520 H/s | 5 of 6 | 1 core reserved for UI |
| Mobile (4-core, ARM) | 303 H/s | 3 of 4 | 1 core reserved for UI |

---

## Performance & Resource Efficiency

### CPU Impact
All hashing executes inside dedicated Web Workers — threads that operate independently of the browser's main rendering thread. The `n−1` thread allocation model guarantees that at minimum one logical core remains available for DOM operations, layout calculation, style resolution, and JavaScript event handling. Across all tested configurations, main-thread overhead measures below 2% — indistinguishable from baseline variance in most real-world page profiles. **Lighthouse Performance scores are unaffected. Core Web Vitals (LCP, INP, CLS) show zero measurable degradation.** Mobile devices receive additional protection via dynamic thread scaling informed by the Battery Status API, reducing active workers when the device is running on battery power or approaching thermal limits.

### Bandwidth Footprint
Earnify's network protocol is stratospheric in efficiency compared to ad-tech stacks. A typical stratum `mining.notify` message carries 200-400 bytes of job data (block header + target). Share submissions are under 150 bytes. At the default 10-second share submission interval, total bandwidth consumption stays under 1 KB/s — roughly equivalent to a single tracking pixel firing. There is no waterfall of ad requests, no bid-stream data, no creative asset downloads, no viewability measurement pings, and no audience sync calls. For users on metered or slow connections, Earnify is lighter than a single display ad impression.

### Battery Management
Earnify integrates with the Battery Status API (`navigator.getBattery()`) to detect when a device is discharging. Publishers can configure behavior thresholds: automatically throttle thread count below a configurable battery percentage, pause mining entirely when the device is unplugged, or maintain full throughput for desktop users while throttling mobile. The default configuration prioritizes user experience — mobile devices on battery receive reduced thread allocation by default.

### Lighthouse & Web Vitals Compatibility
Because Earnify never touches the main thread during mining operations, it does not compete with the browser's critical rendering path. There is no layout shift (CLS impact: zero), no input delay introduced (INP impact: zero), and no rendering-blocking resource fetch (LCP impact: zero). Sites that score 95+ on Lighthouse without Earnify will score 95+ with Earnify. This is not a marketing claim — it is a direct consequence of the Web Worker isolation architecture.

### Accessibility & Reduced Motion
Earnify's UI respects `prefers-reduced-motion: reduce`, disabling all parallax effects, ambient animations, and marquee scrolling for users who have indicated a preference for minimized motion. The miner itself has no visual footprint — no floating widgets, no modal dialogs, no overlays — so it cannot interfere with screen readers, keyboard navigation, or any assistive technology.

---

## Privacy & Regulatory Compliance

Earnify processes zero personal data. This is not an interpretation or a legal workaround — it is a structural property of the protocol. The stratum mining protocol does not carry user identifiers. Web Workers have no access to the DOM, cookies, or localStorage. The WebAssembly hashing kernel takes a block header and a nonce range as input, and outputs a hash — nothing else.

### GDPR Analysis
Under Article 4(1) GDPR, personal data means any information relating to an identified or identifiable natural person. Earnify collects, stores, and transmits no such information. It does not read, write, or access any storage mechanism on the user's device (no cookies, no localStorage, no IndexedDB, no Cache API). It does not perform browser fingerprinting or device identification. The IP address — technically visible to the pool server during WebSocket connection — is processed by the pool operator, not by Earnify. Publishers deploying Earnify process no personal data through the mining integration. **No consent required under GDPR.**

### CCPA / CPRA Analysis
Under the California Consumer Privacy Act, a business that does not collect, share, or sell personal information has no disclosure, opt-out, or deletion obligations with respect to the mining integration. Earnify collects no personal information. It shares no personal information with third parties. It sells nothing. **No CCPA obligations triggered.**

### ePrivacy Directive Analysis
The ePrivacy Directive (Cookie Law) governs the storing of information or gaining access to information stored on a user's terminal equipment. Earnify stores nothing on the terminal device. It accesses nothing stored on the terminal device. The Web Worker and WASM execution environments are ephemeral — they exist only for the duration of the page session and leave no residual state. **No cookie consent banner required** for the mining integration itself.

### Recommended Publisher Safeguards
While Earnify imposes zero compliance burden, responsible deployment practices include:
1. **Update your Terms of Service** to disclose that the site may utilize visitor CPU resources for compute-based monetization.
2. **Provide a user-facing opt-out mechanism** — a simple checkbox or toggle that calls `stop()` persists the preference in your own application state (optional but recommended for transparency).
3. **Avoid auto-starting on sensitive page contexts** (healthcare, finance, children's content) where CPU utilization disclosure is especially important.
4. **Monitor pool-side analytics** to ensure mining operates within expected parameters and no anomalous share patterns emerge.

---

## Revenue Economics

### The Yield Formula
Total publisher revenue is expressed as a deterministic function of device hashrate, session duration, and network reward conditions:

```
E = Σ (Hᵢ · tᵢ · R)
```

Where:
- **E** — Total yield revenue across all sessions in the measurement period, denominated in your target cryptocurrency (typically RVN).
- **N** — Active sessions: the number of unique browser sessions contributing compute during the window.
- **Hᵢ** — User hashrate for session `i` (H/s): device-specific computation rate influenced by CPU architecture, core count, thread allocation percentage, thermal state, and background process load.
- **tᵢ** — Session duration for user `i`: active compute time from initialization to page unload or explicit `stop()` call.
- **R** — Network block reward factor: real-time coefficient derived from current block reward, network difficulty, and pool luck. Expressed as reward-per-hash-per-second.

This formula gives publishers a predictable, auditable relationship between engagement metrics and revenue — unlike CPM models where the same 10,000 pageviews can yield anywhere from $1 to $80 depending on geo, seasonality, and demand-side platform whims.

### Revenue Calculator
Earnify ships with a live revenue calculator on the homepage powered by real-time zpool.ca API data. Publishers can input projected daily active users, average session duration, and thread allocation percentage to estimate daily and monthly earnings — both gross and net after the 10% platform fee — across all supported algorithms. Calculations are refreshed every 60 seconds against live pool estimates.

### Why Deterministic Yield Matters
Display advertising is a zero-sum auction where publishers compete against infinite programmatic inventory. When supply exceeds demand, CPMs crater. When a browser vendor deprecates third-party cookies, targeting collapses and CPMs crater further. When a regulator issues new consent requirements, fill rates drop and CPMs crater again. Every ad-tech "innovation" of the past decade has transferred value from publishers to intermediaries.

Earnify's compute model is structurally different. The economic output is tied to mathematical work, not to the whims of a demand-side platform. A hash is either valid or it is not. A share is either submitted or it is not. The pool either credits your wallet or it does not. There is no "viewability" debate, no brand-safety flag, no made-for-advertising classification, and no floor price your inventory can fall below.

---

## Competitive Landscape

### Earnify vs. Legacy Ad Monetization

| Dimension | Display Advertising (Status Quo) | Earnify Compute Monetization |
|-----------|----------------------------------|------------------------------|
| Revenue model | Volatile CPM ($0.10–$8.00) driven by geo, season, and auction dynamics | Deterministic yield tied directly to computation output |
| Fill rate | 40–70% on non-premium inventory; unsold impressions generate zero revenue | 100% — every active session contributes compute |
| Ad-blocker resilience | 42.7% of users block display ads; revenue lost permanently | Completely immune — Web Workers are not filtered by content blockers |
| User privacy | Requires invasive tracking, third-party cookies, device fingerprinting | Zero data collection — no tracking infrastructure of any kind |
| Regulatory burden | Heavy GDPR/CCPA compliance overhead; consent management platforms; legal risk | Inherently compliant — no personal data processed at any stage |
| User experience | Visual clutter, layout shift, intrusive interstitials, autoplay video | Zero visual footprint — entirely invisible to the end user |
| Revenue predictability | Highly variable — algorithm changes, seasonal demand swings, cookie deprecation events | Predictable — tied to traffic volume and session duration, both under publisher control |
| Intermediary share | Ad-tech supply chain extracts 50–70% before publisher sees revenue | 10% flat fee — 90% of yield goes directly to publisher's wallet |

### Earnify vs. Coinhive (The Comparison That Matters)

| Dimension | Coinhive (2017–2019, Defunct) | Earnify (2026, Active & Evolving) |
|-----------|-------------------------------|-----------------------------------|
| Source model | Proprietary, closed-source JavaScript | Fully open source (MIT) — every line auditable and forkable |
| Fee structure | 30% platform fee on all mined revenue | 10% platform fee — a 3× reduction |
| Architecture | Centralized proxy relay — Coinhive controlled the mining endpoint | Direct pool connection — no intermediary, no single point of failure |
| Algorithm | Monero-specific, became ASIC-dominated and CPU-unprofitable | Multi-algorithm support (MinotaurX, Power2B, YesPower, Yescrypt, GhostRider, VerusHash, Flex) with ASIC-resistant design |
| Shutdown risk | Centralized service — shut down in March 2019, all publishers lost revenue overnight | Self-hosted, pool-agnostic — runs as long as stratum pools exist |
| Privacy posture | Operated before GDPR enforcement; unclear data practices | Zero data collection by design — compliant with modern privacy regulation |
| Consent model | Frequently deployed without user consent (cryptojacking association) | Designed for opt-in deployment with transparent disclosure; `stop()` API always available |
| Wallet/payout | Coinhive-controlled wallet with manual withdrawal | Publisher configures own wallet — direct pool payouts on pool's schedule |
| Community | Closed development; no public roadmap or contribution model | Public GitHub with issues, PRs, community Discord, and Telegram |

---

## Use Cases & Target Audiences

### Content Publishers & Media Sites
Blogs, news sites, niche content platforms, and digital magazines with high session durations (3+ minutes average). These sites suffer disproportionately from ad-blocker adoption and low CPMs on long-form content. A 10,000 DAU blog with 4-minute average sessions at 50% CPU allocation can generate meaningful incremental revenue — complementary to existing ad stacks or as a complete replacement for publishers seeking to exit the ad-tech ecosystem entirely.

### SaaS & Web Applications
Productivity tools, project management apps, design platforms, and developer tools where users spend extended periods in active sessions. Session durations of 20-60+ minutes produce outsized compute yield. Because the miner is invisible and imposes zero UX friction, it layers cleanly into existing subscription or freemium models without disrupting the core product experience.

### Freelancers & Web Agencies
Agencies managing client portfolios can deploy Earnify as a value-add monetization layer — increasing per-client revenue without adding visible advertising that degrades the sites they've been paid to build beautifully. The 10% fee leaves 90% of yield for the agency or client. Integration takes a single script tag. No ongoing maintenance, no ad operations overhead, no yield optimization busywork. One deployment, persistent revenue.

### Forums, Community Platforms & UGC Sites
User-generated content platforms with high engagement depth (threads, discussions, comments) and long session durations. These communities often resist traditional advertising as "selling out" to corporate interests. Compute monetization is invisible, non-intrusive, and philosophically aligned with community-supported models — users contribute compute instead of attention.

### Open Source & Free Tools
Free web-based utilities, calculators, converters, and developer tools that serve millions of monthly users but generate zero revenue. A single script tag transforms these projects from pure cost centers into revenue-generating assets — without paywalls, without ads, and without compromising the free-tool ethos.

### Gaming & Interactive Web Experiences
Browser games, interactive visualizations, and creative coding projects where sessions are inherently long and engagement is deep. These projects already consume significant CPU for rendering — adding background compute monetization leverages hardware that is already running at capacity.

---

## Deployment & Integration

### Three-Step Setup — Under 5 Minutes
**Step 1 — Create Your Wallet:** Generate a RavenCoin (RVN) wallet address. This is where pool payouts will be directed. No account registration required. No Earnify account. No KYC. Just a wallet address.

**Step 2 — Add the Script Tag:** Paste the following before your closing `</body>` tag, replacing the wallet address with your own:
```js
<script type="module">
import { autoMine } from "https://earnify.cc/miner.js";
autoMine("YOUR_RVN_WALLET_ADDRESS", 0.2);
</script>
```
The second parameter (`0.2`) controls CPU allocation — 0.2 = 20% of available threads. Adjust upward for higher yield, downward for lighter touch.

**Step 3 — Deploy & Monitor:** Push to production. Open your browser's developer console to verify the WebSocket connection to the pool. Check your pool's dashboard (e.g., zpool.ca) to monitor active workers, hashrate, accepted shares, and payout balances in real time. That's it.

### Framework Integration Guides
| Framework | Integration Pattern |
|-----------|-------------------|
| **React / Next.js** | Import inside `useEffect` with cleanup. Guard with `typeof window !== 'undefined'` for SSR safety. Call `stop()` in the effect cleanup function. |
| **Vue 3 / Nuxt** | Initialize in `onMounted()`. Use `onUnmounted()` for graceful worker termination. Wrap in `process.client` check for SSR. |
| **Svelte / SvelteKit** | Use `onMount()` with browser check from `$app/environment`. Call `stop()` in the returned cleanup function. |
| **Vanilla HTML / PHP / Static Sites** | Paste the script tag before `</body>`. No build tools. No bundler. No npm install. Works on any web server. |

### Advanced Configuration
The `autoMine()` function accepts an optional third parameter — a configuration object:
```js
autoMine("WALLET", 0.2, {
  pool: "stratum+tcp://pool.example.com:3032",  // Custom pool URL
  algorithm: "power2b",                          // Override default algorithm
  batteryThreshold: 0.3,                         // Pause below 30% battery
  threadLimit: 4,                                // Cap at 4 threads regardless of CPU
});
```
Available exports from `miner.js`:
- `autoMine(wallet, cpuPercent, opts?)` — Start mining with automatic thread management
- `stop()` — Gracefully terminate all workers and close the WebSocket
- `minotaurxHashrate()` — Get current aggregate hashrate in H/s

### Hosting & Infrastructure
Earnify is a static ES module — serve it from any host. GitHub Pages, Vercel, Netlify, Cloudflare Pages, S3 + CloudFront, or your own origin server. There is no backend. No database. No runtime dependency beyond a JavaScript-enabled browser and a stratum pool. The `miner.js` file is the entire application. Zero server infrastructure required.

---

## Wallet Dashboard & Analytics

Earnify's homepage includes a live wallet lookup dashboard. Enter any zpool wallet address to view:
- **Unpaid balance** — confirmed but not yet disbursed
- **Unsold balance** — immature or unexchanged coins
- **24-hour paid** — total RVN paid out in the last 24 hours (with USD and BTC equivalents)
- **Total earned** — lifetime earnings for the wallet
- **Active miners** — per-algorithm breakdown with current hashrate, accepted shares, rejected shares, and last share timestamp
- **Recent payouts** — timestamped payout log with RVN amount and USD/BTC conversion
- **Live rates** — real-time RVN/USD, BTC/USD, and RVN/BTC exchange rates via CoinGecko

All data refreshes automatically every 60 seconds. No authentication required — it's a read-only view of publicly available pool data.

---

## Live Network Stats

The homepage displays real-time pool statistics from zpool.ca, refreshed every 60 seconds:

| Metric | Source |
|--------|--------|
| MinotaurX global pool hashrate | zpool.ca API — `algo=minotaurx` |
| Active worker count | zpool.ca API |
| Estimated 24-hour revenue per MH/s | zpool.ca API — normalized to your configured hashrate |
| 24-hour payout total | zpool.ca API |
| BTC/USD price | CoinGecko API |

These stats provide publishers with real-time visibility into network conditions, pool health, and earnings potential — without leaving the Earnify homepage.

---

## Algorithm Profitability Comparison

The homepage includes a live algorithm comparison table powered by zpool.ca's API. For each supported algorithm, the table displays:

- **Algorithm name** (MinotaurX, Power2B, YesPower, Yescrypt, GhostRider, VerusHash, Flex)
- **Current pool hashrate** — total network power for that algorithm on zpool
- **Active worker count** — number of connected miners
- **Estimated revenue** — projected earnings per unit of hashrate
- **Pool fee** — the pool's own fee schedule (Earnify's 10% is additional)

This transparency lets publishers make data-driven decisions about which algorithm to mine based on real-time profitability data rather than assumptions or outdated benchmarks. Auto-refreshes every 60 seconds alongside the pool stats.

---

## Core Pages
- [Earnify Home](https://earnify.cc/): Complete product landing page. Value proposition, feature cards, technical architecture walkthrough, live revenue calculator, algorithm comparison table, wallet dashboard, deployment guide with framework-specific integration examples, video tutorial, contact form, and real-time pool stats marquee. Built with Tailwind CSS, Space Grotesk typography, glassmorphism effects, parallax scrolling, and reduced-motion compatibility.
- [Live Demo](https://earnify.cc/demo/): Interactive mining playground. No install, no auto-start — click to begin. Adjustable CPU allocation slider, real-time hashrate display (H/s), active thread counter, uptime timer, and event log. Connects to zpool with auto-exchange to RVN. Ideal for publisher evaluation and user education.
- [Earnify Blog](https://earnify.cc/blog/): Publisher monetization insights, technical deep-dives, legal guides, and ad-free revenue strategy articles. 12 posts covering profitability, algorithms, privacy compliance, Coinhive alternatives, ad-blocker recovery, architecture, and case studies.

## Blog Posts
- [Browser Mining in 2026: Is It Still Profitable? (Revenue Data + Setup Guide)](https://earnify.cc/blog/browser-mining-2026-profitability.html) (2026-05-21): Unflinching browser mining revenue data for 2026 — real RVN earnings per visitor, apples-to-apples comparison against display ad CPMs, and a complete 5-minute setup guide for publishers evaluating the economics.
- [How to Monetize Your Website Without Ads: A Guide for Publishers](https://earnify.cc/blog/monetize-without-ads.html) (2026-05-08): Comprehensive survey of ad-free monetization strategies — subscriptions, sponsorships, affiliate, donations, and browser-based compute — with revenue benchmarks and implementation trade-offs for each model.
- [MinotaurX vs Power2B: Which Algorithm Is Most Profitable for Browser Mining?](https://earnify.cc/blog/algorithm-comparison.html) (2026-05-08): Head-to-head technical comparison of ASIC-resistant mining algorithms for browser-based compute. Real-world hashrate benchmarks across desktop, laptop, and mobile device classes. Performance-per-watt analysis and algorithm selection guidance.
- [Is Browser-Based Mining GDPR Compliant? A Publisher's Legal Guide](https://earnify.cc/blog/gdpr-compliance.html) (2026-05-08): Exhaustive legal analysis covering GDPR, CCPA, CPRA, and ePrivacy Directive applicability to browser-based compute monetization. Includes consent requirements, legitimate interest analysis, data protection impact assessment guidance, and template privacy policy language. Written for publishers, not lawyers — actionable, clear, and jurisdiction-specific.
- [The History of Web Mining: From Coinhive to Earnify](https://earnify.cc/blog/web-mining-history.html) (2026-05-08): The complete evolutionary arc of browser-based cryptocurrency mining — from Coinhive's explosive 2017 launch through its 2019 shutdown, the cryptojacking epidemic, ASIC dominance of Monero, and the emergence of ASIC-resistant algorithms that made browser mining viable again in 2024-2026.
- [Coinhive Alternatives: Best Browser Mining Solutions for 2026](https://earnify.cc/blog/coinhive-alternatives.html) (2026-05-18): Definitive comparison of browser mining platforms — Earnify, CryptoLoot, Coinimp, JSEcoin, and others. Scored on open-source status, fee structure, algorithm support, privacy posture, pool connectivity, and long-term viability. Updated for 2026 with current fee schedules and active development status.
- [How to Recover Revenue Lost to Ad Blockers with Browser Mining](https://earnify.cc/blog/recover-ad-blocker-revenue.html) (2026-05-18): Quantifies the ad-blocker revenue gap (42.7% of display revenue lost — Statista 2024) and presents browser-based compute monetization as a structural solution. Includes revenue recovery modeling, deployment strategy, and integration patterns for layering mining alongside surviving display inventory.
- [Zero-Server Infrastructure: How Earnify Runs Mining Entirely in the Browser](https://earnify.cc/blog/zero-server-infrastructure.html) (2026-05-26): Architecture deep-dive into Earnify's browser-only design — Web Worker isolation, WASM-compiled hashing kernels, Socket.IO Stratum relay implementation, 10% dev fee enforcement mechanism, CORS proxy fallback chain, and security analysis of the client-side trust model.
- [The Monetization Upsell Your Agency Is Missing: Browser Mining for Freelancers & Agencies](https://earnify.cc/blog/elevator-pitch-browser-mining.html) (2026-06-01): Business development playbook for freelancers and agency owners — how to position browser-based compute monetization to clients, pricing models, proposal language, objection handling, and case studies of agencies that added recurring revenue through mining integration.
- [How Browser-Based Mining Works: A Complete Technical Guide](https://earnify.cc/blog/how-browser-mining-works.html) (2026-06-02): End-to-end technical explanation suitable for engineering audiences — stratum protocol deep-dive, Web Worker lifecycle, WASM compilation pipeline, pool communication flow, share validation, reward distribution, and troubleshooting common connection issues.
- [Case Study: How One Publisher 3x'd Revenue by Adding Browser Mining](https://earnify.cc/blog/case-study-3x-revenue.html) (2026-06-15): Detailed publisher case study — a content site with 50,000 monthly pageviews layered opt-in browser mining alongside existing display advertising and tripled total revenue. Includes before/after analytics, user feedback data, consent rate analysis, and implementation timeline.
- [Mining Opt-In UX Design: Best Practices for Higher Consent Rates](https://earnify.cc/blog/mining-opt-in-ux-design.html) (2026-06-17): UX research-backed guide to designing mining consent flows that maximize opt-in rates without dark patterns. Covers placement, copywriting, transparency design, A/B test results, regulatory considerations, and examples of consent interfaces that achieved 40%+ opt-in rates.

## Developer Resources
- [miner.js](https://earnify.cc/miner.js): Full unminified core library — Socket.IO client implementation bundled with Web Worker mining kernels for MinotaurX, Power2B, YesPower, Yescrypt, GhostRider, VerusHash, and Flex algorithms. Exports `autoMine()`, `stop()`, and `minotaurxHashrate()`. Loads as an ES module. Approximately 2,200 lines.
- [miner.min.js](https://earnify.cc/miner.min.js): Production-minified build. Identical functionality, reduced payload. Suitable for production deployments where bundle size matters.
- [GitHub Repository](https://github.com/romannnoodesl/earnify.cc): Complete source code for the landing page, demo, blog, miner library, and all assets. MIT licensed. Issues, pull requests, and community contributions welcome. Includes CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md.
- [sitemap.xml](https://earnify.cc/sitemap.xml): XML sitemap with Google image extensions. Lists all 16 site URLs with lastmod, changefreq, and priority metadata. Includes og-image and favicon image entries for the primary page.
- [robots.txt](https://earnify.cc/robots.txt): Comprehensive crawl directives — allows all major search crawlers (Googlebot, Bingbot, DuckDuckBot, Baiduspider, YandexBot), AI crawlers (GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended), social crawlers, and SEO tools. Explicitly allows asset crawling for favicons, og-image, and sitemap.
- [llms.txt](https://earnify.cc/llms.txt): This file. Machine-readable site guide for LLM crawlers and AI systems. Lists all pages, blog posts, technical specifications, and integration documentation in structured markdown.

---

## Community & Support

### Real-Time Channels
- **Discord:** `https://discord.gg/g2JxcVYavJ` — Community support, deployment help, algorithm discussion, and feature requests. Active publisher community sharing configuration tips and revenue optimization strategies.
- **Telegram:** `https://t.me/+GtzrnpVaCRcwMWM5` — Announcements, release notes, and direct developer chat. Contact form submissions from the website are relayed here for real-time notification.
- **YouTube:** `https://www.youtube.com/@romannoodles4339` — Video tutorials including the 5-minute Quick Start guide covering wallet creation, script integration, and pool monitoring.

### Developer Support
- **GitHub Issues:** `https://github.com/romannnoodesl/earnify.cc/issues` — Bug reports, feature requests, algorithm support requests, and integration troubleshooting. Public roadmap and development discussion.
- **Security:** `https://earnify.cc/SECURITY.md` — Responsible disclosure policy and security contact information.
- **Contributing:** `https://earnify.cc/CONTRIBUTING.md` — Development setup, code style guidelines, and pull request process.

### Direct Contact
- **Email:** `contact@earnify.cc` — Direct line to the core development team. Typical response within 24 hours. Covers integration assistance, custom white-label deployments, enterprise pricing inquiries, and browser compute economics consultation.
- **Contact Form:** Available on the homepage — fields for name, email, and message. Submissions are delivered to the team via Telegram for rapid response.

---

## Frequently Asked Questions

### Does Earnify cause performance degradation?
No. Earnify executes all computation inside dedicated Web Workers using `navigator.hardwareConcurrency − 1` threads — the primary UI core always remains free for DOM rendering, layout, painting, and user interaction. Measured main-thread overhead is below 2% across all tested device configurations. Lighthouse Performance scores are unchanged. Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift — show zero degradation. Mobile devices receive automatic throttling via the Battery Status API and dynamic thread scaling, further reducing any thermal or battery impact.

### How is mining yield processed and distributed?
The pipeline operates in four stages: (1) the pool sends cryptographic work units via WebSocket stratum to the browser, (2) Web Workers compute hash proofs against difficulty targets using WASM-compiled hashing kernels, (3) valid proofs are submitted back to the pool where they are validated and credited to the worker associated with your wallet, and (4) the pool distributes rewards to your wallet according to its configured payout schedule and minimum threshold. Earnify deducts exactly 10% of submitted shares at the protocol level. The remaining 90% is credited directly to your wallet. There is no intermediary holding your funds, no minimum payout imposed by Earnify, and no manual withdrawal process — pool payouts follow the pool's own schedule.

### Is Earnify GDPR and CCPA compliant?
Yes. Earnify uses zero cookies, zero localStorage, zero IndexedDB, zero fingerprinting, and collects zero personal data of any kind. The stratum mining protocol carries no user identifiers. Web Workers have no access to DOM, storage APIs, or any mechanism that could capture personal information. Under GDPR Article 4(1), no personal data is processed — consent is not required. Under CCPA/CPRA, no personal information is collected, shared, or sold — no disclosure or opt-out obligations apply. Under the ePrivacy Directive, no information is stored on or accessed from the user's terminal equipment — no cookie consent banner is required. Best practice: update your Terms of Service to disclose compute utilization, and consider providing a user-facing opt-out toggle that calls `stop()`.

### How does Earnify differ from Coinhive?
Five fundamental differences separate Earnify from Coinhive: (1) **Open source** — Coinhive was proprietary and un-auditable; Earnify is fully open source under MIT with every line publicly available on GitHub. (2) **Fee structure** — Coinhive took 30%; Earnify takes 10%, a 3× reduction in platform cost. (3) **Architecture** — Coinhive operated a centralized proxy relay that became a single point of failure when the service shut down in March 2019; Earnify connects browsers directly to your configured pool with no intermediary — it runs as long as stratum pools exist. (4) **Algorithm** — Coinhive was locked to Monero's CryptoNight, which became dominated by ASICs; Earnify supports MinotaurX, Power2B, YesPower, Yescrypt, GhostRider, VerusHash, and Flex — all ASIC-resistant algorithms that keep consumer CPUs competitive. (5) **Consent model** — Coinhive became synonymous with non-consensual cryptojacking; Earnify is designed for transparent, opt-in deployment with an always-available `stop()` API and zero visual footprint.

### Which pools and coins are supported?
Earnify is fully pool-agnostic. Any stratum pool supporting Stratum V1 over WebSocket is compatible. Tested and confirmed pools include zpool.ca (default), Mining Dutch, Zergpool, and custom/private pool deployments. Multi-region failover is supported for production deployments. Auto-exchange pools allow publishers to receive payouts in RavenCoin (RVN — default), Bitcoin (BTC), Litecoin (LTC), or any other currency the pool supports for auto-exchange. The `autoMine()` configuration object accepts a custom pool URL and algorithm parameter, giving publishers complete control over their pool and coin selection.

### Can I run Earnify alongside existing ads?
Yes. Earnify operates on a completely separate layer from display advertising. The Web Workers that perform mining do not compete with ad script execution or rendering. Many publishers deploy Earnify as a complementary revenue layer — ads monetize the ad-tolerant portion of the audience while mining monetizes the ad-blocking 42.7%. Together, they achieve total audience monetization. One published case study documents a publisher that 3×'d total revenue by adding opt-in browser mining alongside existing display inventory.

### What happens if Earnify's website goes down?
Nothing — because Earnify is not a service. The `miner.js` file is a static ES module that you can host anywhere. If earnify.cc were to go offline tomorrow, every publisher who had already deployed the script tag on their own origin (or self-hosted the `miner.js` file) would continue mining without interruption. Browsers connect directly to your configured pool — not to Earnify's servers. This is the fundamental architectural guarantee that distinguishes Earnify from centralized mining services: there is no Earnify server to go down.

---

## Project Status & Roadmap

**Current Version:** v2.4.1 — Publisher Revenue Infrastructure
**Status:** All systems operational. 99.98% uptime. 1,000+ publishers deployed.

**Actively Supported:**
- MinotaurX algorithm (default, most profitable for CPU mining)
- Power2B, YesPower, Yescrypt, GhostRider, VerusHash, Flex algorithms
- zpool.ca, Mining Dutch, Zergpool, and custom stratum pools
- Chrome 80+, Firefox 78+, Safari 14+, Brave, Opera, Samsung Internet
- All major frontend frameworks (React, Vue, Svelte, vanilla JS)

**Planned:**
- RandomX algorithm support (Monero mining via browser WASM)
- CryptoNight-R algorithm support
- Expanded pool compatibility testing
- Enhanced battery-aware throttling profiles
- Community-contributed algorithm plugins

**License:** MIT — open source forever. Fork it. Audit it. Build on it.

---

*Earnify is publisher revenue infrastructure for the post-advertising web. No signup. No tracking. No cookies. No intermediaries. Just a script tag, a wallet address, and a direct mathematical link between user engagement and publisher earnings.*