Archived experiment
XMR web miner: what changed
This page used to load a browser-based Monero miner. That integration is now intentionally disabled: the old mining scripts are no longer shipped with the project, modern browsers and security tools treat this pattern as suspicious, and the practical return is usually too low to justify the CPU cost.
Why it no longer runs here
- The miner depended on external JavaScript and mining-pool connectivity that is brittle over time.
- Running CPU-heavy code in a visitor browser is a poor default unless consent is explicit and reversible.
- Antivirus, ad blockers and browser protections commonly block this type of workload.
The numbers above are only a simple educational estimate. They are useful for understanding scale, not for predicting real revenue. Real mining depends on device performance, pool rules, network difficulty, fees and Monero price.
What to use instead
If the goal is learning proof of work without burning visitor CPU, the safer version is the educational mining simulator: open the simulator.
Indexing note: why this page stays useful
The page is kept because it documents an important technical and ethical lesson: a feature can be interesting from an engineering point of view and still be a bad product decision. Browser mining touches JavaScript execution, user consent, monetization, security reputation and performance at the same time.
If you are evaluating a similar idea today, start with a threat model. Ask what code is downloaded, who controls the pool endpoint, whether the visitor can stop execution, how mobile devices behave and how the feature appears to antivirus and corporate proxies. Those questions matter more than the hash-rate number.
A practical replacement is to separate the educational part from the monetization part. Use a local simulator to explain nonce search and difficulty, and choose a transparent business model for the website itself.
In short, the technical lesson is still useful, but the original implementation should remain disabled. A page that protects trust, battery life and informed consent is more valuable than a hidden monetization experiment.
What this teaches about performance
Browser mining is also a good example of why performance budgets are not only a frontend metric. A script can load correctly, pass a functional test and still damage the experience because it competes with scrolling, rendering, battery usage and other tabs. Any background workload should be measurable, limited and easy to stop.
For a modern website, the safer engineering lesson is to keep expensive work on trusted infrastructure, expose progress to the user and avoid surprises in the browser. That applies to mining, image processing, AI inference and any long-running JavaScript task. It also makes analytics cleaner, because performance problems can be traced to intentional backend jobs instead of hidden client-side work.
Consent and reputation checklist
Any feature that consumes noticeable CPU should be evaluated with the same care as payments or personal data. The visitor must know what will run, why it runs, how long it will run and how to stop it. Consent should not be hidden inside a generic cookie banner because the impact is different: mining affects battery, heat, fan noise and perceived security.
From an SEO point of view, this is also a trust issue. A page associated with unwanted mining scripts can be treated by browsers, antivirus tools and users as hostile even if the developer's original intention was educational. Keeping the old implementation disabled and explaining the decision is therefore part of the value of the page.
If you need an interactive lesson, use the simulator, synthetic numbers and local state. That keeps the learning objective intact without connecting visitors to a mining pool or making their device perform hidden work.
The engineering takeaway is broader than Monero. Any browser feature that performs hidden work can damage user trust: invisible analytics loops, aggressive fingerprinting, background AI inference or expensive canvas tasks. The same checklist applies in every case: make the cost visible, keep the feature optional, provide a stop action and measure the effect on low-powered devices.
A safe educational page should therefore explain the original implementation, why it was removed and what a responsible alternative looks like. That context is what keeps this archived experiment useful for developers who arrive looking for web mining examples today.