StackXMR (Monero Signal Engine)

What it is. A single-page XMR price-and-signals dashboard at `stackxmr.dev`. It pulls live XMR prices, computes the usual technical-analysis bands (EMA structure, RSI, MACD, volatility, drawdown, support/resistance, regime), and surfaces a buy/sell/hold recommendation with confidence + entry/exit + DCA suggestions on top. Single static HTML file (~6MB inline). No backend, no signup, no telemetry.

Background. Solo project under the alias `admin191655` (GitHub username — the repo at `github.com/admin191655/stackxmr` has 0 stars and is essentially bare shell scaffolding rather than the actual dashboard source). The author publishes the dashboard as MSE — *Monero Signal Engine* — currently at v5.3, with an X account at `@ocomeoXMR` carrying 17 followers and no visible posts. No real-name identity, no jurisdiction, no team. The dashboard is donation-funded — a Monero address is shown on the page (*"Buy me a Blunt"*) for tips. There is no incident history because there is no service to incident: the page is a calculator on top of live market data, not a service that holds anything.

What you trust.

• The architecture is its own privacy posture. Static HTML running entirely in your browser means there is no backend logging your visits, no analytics pixel, no cookies you care about, and nothing the operator could meaningfully *do* to you even if they wanted to. The threat surface is roughly *"the operator could publish bad signals and you might act on them"* — not *"the operator could exfiltrate your data."*
• Methodology is named. Every indicator the engine uses is listed on the page (EMA, RSI, MACD, ATR-style volatility, regime classifier, etc.). That isn't *audited*, but at least you know which knobs the dashboard is turning, which is more disclosure than most signals services bother with.
• License posture is permissive. *"Freely copy, share, mirror, modify, and distribute this static Monero Signal Engine."* That makes the dashboard genuinely forkable — anyone can host their own mirror, including over IPFS or Tor, without dealing with the operator.
• No KYC, no signup, no payment. It's a free page. If you trust the source-of-truth for the live price (whichever upstream API the page queries) and you trust your own ability to read TA signals critically, the rest is on you.

Operational specs.

• Site. `https://stackxmr.dev` — single static HTML file. No `/about`, `/terms`, `/privacy`, or other surface beyond the dashboard itself.
• Operator channels. GitHub `admin191655` (mostly empty) and X `@ocomeoXMR` (~17 followers, no visible posts at fold-time). No PGP key, no Matrix, no email, no Telegram. If you want to reach the maintainer, GitHub issues are the obvious path.
• Donation. XMR address surfaced on the page (`87ufokoq88LZ3SaqEJmKm6PxZRFzvmc4ec3HRFKyKKWKbyLPSyfEYf8jNiAo4Md17tbyJsu7P5eepXZcS1DWFPjsKESV7qb`).
• Tor / IPFS friendliness. The page is small enough and self-contained enough to be mirrored on IPFS or served from an onion. The author advertises this posture explicitly but does not run a first-party `.onion` themselves as of fold-time.
• No price-source disclosure. The page is live ("waiting…", "calibrating…"), but it does not document which upstream API it queries for XMR price + history. The dashboard's signals are only as honest as that source.
• Settings persist locally. Risk profile (conservative / normal / aggressive), timeframe (swing / scalp / position), holdings, cash budget — all saved client-side. Nothing is sent to a server.

Operator philosophy. The dashboard is positioned as *"an educational dashboard, not financial advice."* The maintainer is publishing a tool, not running a service — there is no support promise, no SLA, no roadmap commitment, and no monetisation beyond optional XMR tips. The choice of architecture (static HTML + client-side state) and license (anyone can mirror) reads as *"I built this because I wanted it; here it is, take it"*. That's a perfectly valid posture for a hobbyist tool, and it shapes what you can reasonably expect: bug fixes when the maintainer feels like it, no guarantees on uptime or accuracy, and no recourse if the signals turn out to be terrible during a market shock.

Grade rationale. Listed at Grade C. The substantive case for listing at all: the architecture is private-by-construction (no backend, no telemetry), the methodology is named rather than hidden, the license is permissive enough that anyone could mirror or fork. What keeps it under B: the operator presence is genuinely barren — a near-empty GitHub repo, an X account with 17 followers and no posts, no real-name identity, and no peer-directory has independently reviewed the dashboard yet. The *"Freely copy and modify"* claim is also somewhat undercut by the fact that the GitHub repo doesn't actually carry the dashboard source — it's a bare shell with no version-controlled history of the page that's actually live. Path to B: publish the actual dashboard source to GitHub (or any version-controlled mirror), pick up a peer-directory listing (monerica or kycnot — though kycnot's scope is no-KYC services rather than tools, so monerica is the more obvious target), and accumulate some independent commentary on the signals (a forum thread, a blog post, anything that isn't just the maintainer's own surface).

Useful when:

• You want a privacy-respecting XMR price + signals dashboard that runs entirely in your browser, with no signup and no telemetry. The architecture is the feature.
• You want a tool you can fork, mirror, or run offline. The static-page + permissive-license combination makes the dashboard genuinely portable.
• You're learning technical analysis on XMR specifically and want a single page that surfaces the standard indicators (EMA / RSI / MACD / regime) with explicit names rather than mystery signals. Treat the buy/sell/hold output as a learning aid, not a recommendation.

Caveats.

• Signals are not advice. The maintainer explicitly says so on the page. Acting on a *"buy"* signal during a thinly-traded XMR market move can blow you up the same way acting on a *"sell"* signal during a relief rally can. The dashboard is a calculator on top of live data — not a trader, not a fiduciary, not accountable.
• Price source is undisclosed. The page does not document which upstream API it queries for XMR prices and history. If that source is wrong or stale, every signal is wrong or stale. Cross-check the price against an aggregator before quoting a number from here.
• GitHub "repo" is barren. The repo linked from the project does not contain the live dashboard source — it's shell scaffolding. The *"Freely copy and modify"* claim only works in the inspect-the-HTML sense, not the read-the-source-and-fork sense. Worth knowing if you intended to mirror or audit.
• Operator surface is essentially empty. No real name, no jurisdiction, no PGP key, no Matrix room, no incident history. If the page goes down, vanishes, or starts publishing different signals tomorrow, there is no recourse beyond opening a GitHub issue and hoping for a reply.
• Tor / IPFS posture is aspirational. The author advertises Tor-friendly use but does not run a first-party onion as of fold-time. Mirroring is left as an exercise for the reader.
• No incident history — which is good and bad. Good because no public incident has happened. Bad because nobody has tested the maintainer's response under pressure (a bad signal during a flash crash, an upstream API change that breaks the dashboard, a fork dispute). The next incident, whenever it comes, will be the first read on how this is maintained.