Browser-native compute network

Your browser can contribute compute, not just content.

Temple Earth lets browsers offer verified spare capacity — inference, compute, storage, and networking — so users and sites earn from work that already happens inside the page.

Consent-based Open-source worker Non-custodial payouts WebGPU / WASM fallback
How it works

A simple path from spare capacity to verifiable reward.

Three stages that keep the user in control and make participation auditable.

01 — Browser node
A lightweight container runs in the browser. It uses only spare CPU, GPU, and optional bandwidth. No installer, no background service, no hidden bridge.
02 — Verified job runtime
Job requests are validated, sandboxed, and rate-limited by the worker runtime. Execution stays local and results leave only as verified outputs.
03 — Rewarded participation
Completed jobs are submitted to the network. Rewards accrue to a non-custodial wallet. The node operator can pause or withdraw anytime.
Trust

Built to be auditable from the first click.

No secrets, no silent bridges, no external daemons.

Local execution boundaries
Inference and compute is isolated to the page context. Memory is released after each job. No data leaves the device except results.
Consent by design
Users choose which resources to share and see current usage. Limits are enforced client-side before jobs are accepted. Pause or adjust limits instantly.
Wallet ownership
A non-custodial rewards wallet is created at onboarding. Recovery stays with the user. Withdrawals go directly with no intermediary custody.
Open-source worker
The worker code is published under a real GitHub repo and is reproducible from source, not hidden behind a closed endpoint.
Example

Earn Idle — the first validated client.

Earn Idle demonstrates the network promise end-to-end: contribute resources, complete jobs, earn rewards. Everything runs inside the browser. Your data stays on your device. Only the resources needed for each job are used. You get paid per job completed.

What the client actually does
  • Runs inside the browser container, no download needed
  • Executes the verified inference worker on-device
  • Uses WebGPU with WASM fallback for broad support
  • Your data stays on your device; only job resources are used
  • Pays out per job completed to a non-custodial rewards wallet
Repository
terexitarius/earnidle-transformers-worker. Same worker used in the live client.
Contribute

Resource Client

Contribute spare resources, complete verified jobs, earn rewards. Everything runs in the browser. Your data stays on your device.

Welcome / Trust
Step 1
Secure widget runtime with granular consent. Share CPU, GPU, and bandwidth when you choose. Pause or adjust limits instantly.
Wallet Genesis
Step 2
Sign in to get started. A non-custodial rewards wallet is created automatically. Wallet funds are controlled by you.
Hardware Consent
Step 3
Choose which resources to share and set your limits: CPU, GPU, bandwidth. Adjust anytime from your session settings.
Verify Wallet
Step 4
Sign a message with your wallet to verify ownership. This prevents abuse and keeps the reward pool honest.
Active Session
Step 5
See live earnings, session time, reputation, and completed tasks. Pause sharing or adjust limits from this panel.
Withdraw / Payouts
Step 6
Withdraw rewards to your non-custodial wallet anytime. No custodial accounts, no hidden fees.
Monetize

Publisher

Earn from placements while users contribute resources in-browser.

Setup
Step 1
Create your publisher account and link a verified domain. One publisher per domain keeps fraud low.
Verify Domain
Step 2
Add one TXT record to your DNS. Once checked, your domain is verified and eligible for placements.
Payout Wallet
Step 3
Create a secure, non-custodial wallet for payouts. You own the key. Passkey + backup phrase recovery.
Create Placement
Step 4
Define page id, placement id, allowed domain/path, resource limits, and reward split.
Embed Code
Step 5
Copy the script and iframe snippet. Add to your verified pages and start monetizing placements.
Dashboard
Step 6
Monitor verified pages, active sessions, earnings, and payout history from one place.
Browser capabilities

What the browser container can do.

The browser can contribute more than just inference. These are the rentable services the container makes available.

Inference
Run verified AI inference jobs on-device using WebGPU with WASM fallback. No data leaves the browser.
CPU / WebAssembly compute
Execute general-purpose compute tasks using spare CPU cycles inside a sandboxed WebAssembly runtime.
GPU / WebGPU + WebGL
Leverage the GPU for parallel workloads. Automatically falls back to WebGL when WebGPU is unavailable.
Bandwidth / routing
Relay or proxy small amounts of network traffic. Useful for distributed routing and connectivity checks.
Memory / caching
Store temporary data for the network. Clean, sandboxed memory that is released after each job.
Temporary storage
Hold short-lived files or intermediate results needed for the current job only. No persistent device access.
Micro-sensors / RTC
Use device sensors or real-time communication metadata only when explicitly allowed by the user.