dev comments

[serejandmyself]

• missing mining stats for monero!
• validator cost = amount of run nodes?
• mining pool revenue - good place for detailed earning stats
• dev mode validators needs to contain mining pools too - this is the idea of validtorinfo. showing validators and pools in 1 unique table
• clicking you on main page (horizontal menu) should prompt web3 login, and logout button should not be visible before i login
• clicking ai from vertical left menu should take to: /ai
• about us icon in color?
• both about us and play break when i click them from left vertical menu - expected behavior like with you, should open on middle tab of the 5 sub-tabs related to topic
• the horizontal tab menu on /help page is form an older version of the website

---

We need to discuss this together:

1. Security

• Total staked | Total network hashrate
• Validator count | Mining pool count + estimated miners
• Active validators | Active mining pools
• Nakamoto coefficient | Pool concentration / hashrate Nakamoto coefficient
• Validator uptime | Pool uptime
• Slashing events | Reorgs, orphan rate
• Validator performance | Pool efficiency
• Missed blocks | Orphaned blocks
• Stake distribution | Hashrate distribution
• Stake-weighted decentralization | Hashrate-weighted decentralization

2. Economics

• APR | Miner ROI
• APY | Annual mining profitability
• Inflation | Emission schedule
• Rewards to distribute | Remaining emission
• Community pool | Tail emission reserve (economic security)
• Treasury | None (or CCS ecosystem)
• Total staked | Daily issued XMR
• Validator rewards | Block reward
• Delegator rewards | Pool payouts
• Commission | Pool fee
• Average delegation | Average miner contribution
• Think, staking inflation -> emissions, tails, circulating supply, stock to flow, etc

3. Pool page (val profile)

• IMPORTANT: The below idea does NOT constitute for the fact that a pool page should be liek a validator page: so it should have a table of tokens you can mine there. Most of the below metrics most probably belong in pool passport (node passport)

• Pool Page

• Hashrate

• Pool fee

• Connected miners

• Blocks found

• Luck

• Historical luck

• Last block found

• Average payout

• Minimum payout

• Payout frequency

• Uptime

• Geographic servers

• Software

• Stratum endpoints

• Historical hashrate

• Historical dominance

• Share difficulty

• Latency

• Pool market share
• Pool switching rate
• Miner loyalty (estimated)
• New miners joining
• Pool growth rate
• Hashrate migration
• Pool churn
• Mining centralization trend

4. Node Analytics

• IMPORTANT: a lot are just ideas

• Reachable nodes

• Geographic distribution

• IPv4/IPv6

• Tor nodes

• I2P nodes

• Software version

• Sync status

• Pruned/full

• Peers

• Incoming/outgoing connections

• Average latency

• Age

• Version adoption

• Network upgrades

5. Governance
   Development Health (Think of this as governance-by-consensus):

• Active maintainers
• Open PRs
• Open issues
• CCS proposals
• CCS funded
• Hard fork schedule
• Version adoption
• Upgrade readiness
• Wallet adoption
• Node upgrade %

6. Network metrics general:

• TPS | TPS
• Average tx fee | Average tx fee
• Average block time | Average block time
• Block utilization | Block utilization
• Block size | Dynamic block size
• Finality | Confirmation depth
• Gas used | Block weight
• Gas price | Fee per byte
• Active addresses | Estimated unique outputs/heuristics
• New wallets | Impossible directly
• Total transactions | Total transactions
• Failed tx | Rejected tx
• Pending tx | Mempool

7. Staking to mining:

• Stake/delegate/APR -> mining profitability calculations in any form

8. Larger comparison points:
   Voting power | Hashrate
   Stake | Hashrate
   Self stake | Pool-owned hashrate (if known)
   Commission | Fee
   Uptime | Uptime
   Missed blocks | Orphans
   Delegators | Connected miners
   Rewards | Blocks found
   Rank | Rank

9. POW network overview:

• Difficulty
• Network hashrate
• Estimated miners
• Active pools
• Full nodes
• Reachable nodes
• Average propagation time
• Orphan rate
• Block interval variance
• Difficulty adjustment stability
• Mempool size
• Average confirmation time
• Transaction backlog

10. Metrics unique to Monero:

• We do NOT need not half, not all of them. But some things will appear as natural when analytics start. Also good for knowledge, even 1/2 from here
• Ring size statistics
• RingCT adoption/history
• Bulletproof transaction share
• CLSAG transaction share
• Average anonymity set
• Decoy selection distribution
• Output age distribution
• Mempool privacy characteristics
• Transaction weight distribution
• Dynamic block-size expansion/contraction
• Difficulty adjustment efficiency
• RandomX performance trends
• CPU architecture distribution (estimated from mining telemetry where available)
• Mining hardware diversity
• Tail emission security ratio (tail emission relative to total miner revenue)
• Fee vs subsidy ratio
• Pool variance ("luck") over time

11. A little table to think about comparing POW and POS

Security Dimension	PoS	Monero (PoW)
Economic commitment	Tokens locked	Compute + electricity expended
Security resource	Stake	Hashrate
Operators	Validators	Miners / mining pools
Delegation	Token delegation	Pool participation
Rewards	Staking rewards	Block rewards + fees
Penalty	Slashing	Operational cost and opportunity cost
Governance	On-chain voting	Social consensus + CCS + node/software adoption

[m1amgn]

PR #644

Issue #642 — dev-comments UI fixes

Fixes from the top bullet list of issue #642 (nav/UX bugs surfaced alongside the recent Monero work). The numbered analytics sections 1–11 and the dev-mode validators+pools merge are R&D and intentionally excluded; the About-Us icon recolor
is parked pending an asset.

Changes

1. /help — stale tab menu. Page rendered a dead mainTabs array (Calculate/Compare/Home/Rumor/Global) left from an old nav refactor. Now uses the current homeTabsHorizontal, matching every other page.

2. Logout hidden until logged in. LogoutButton rendered unconditionally on /profile while auth is client-only. Now reads walletData and returns null when disconnected (defense-in-depth alongside fix App architecture (server side) #7).

3. About Us & Play sub-tabs. About pages and the Library layout wired the top-level homeTabsHorizontal instead of their own sets, orphaning their sub-pages and breaking active-tab highlight. About now uses aboutTabs (AboutPage namespace),
   Library uses libraryTabs (LibraryPage) — mirroring /profile.

4. Horizontal You gates web3 login. Horizontal tab rendered You as a bare link to /profile. Added optional TabOptions.isWalletLogin (set on You); TabListItem now opens the wallet-connect modal when disconnected, mirroring the vertical menu.

5. Dedicated /ai chat page. AI opened a floating modal and never navigated; /ai was an "Under Development" placeholder. Extracted the modal's chat body into a shared AiChatPanel, reused by both the modal and a new full-page /ai chat;
   removed the /ai nav interception so the item routes to the page. Contextual "explain" modal preserved. The /ai page is full-width and fills the viewport height so the input needs no scrolling.

6. /profile gated behind a connected wallet. The whole /profile subtree was reachable logged-out. Added WalletContext.isInitializing to tell "still verifying the JWT" from "logged out" (no modal flash at logged-in users), and a client
   ProfileGuard: shows a loading spinner while verifying (on entry and right after Connect); shows a "Connect your wallet to view your profile" screen + button (reusing the existing wallet modal) when disconnected; renders the profile once
   connected. The spinner reuses the AI chat's loading indicator via a new shared LoadingDots component (also adopted by the AI chat, DRY). New i18n keys ProfilePage.LoginRequired / Connect / Verifying in en/pt/ru.

7. Dimmed backdrop for the wallet modal. BaseModal drew only a floating box. Added an opt-in withOverlay prop (default false → all other modals unchanged) rendering a bg-black/50 backdrop-blur-sm overlay; WalletModal enables it — dimming
   the page from all three entry points (vertical You, horizontal You, /profile gate).

[m1amgn]

PR #645
Monero PoW Analytics (issue #642)

Adds a full analytics surface for Monero across the network, mining-pool, blocks, transactions and tokenomics pages. Turns already-indexed data (and, for one slice, previously-discarded indexer fields) into decentralization, economics, and
network-activity metrics — matching the site's existing card/passport-row idioms, localized in en / pt / ru.

Built as sequential slices, each grounded in a data-readiness audit that split metrics into bucket A (derivable from data already in the DB) and bucket B (needs persisting fields the indexer already fetches).

What's included

1. Network Health panel — /networks/monero/stats
   Decentralization/security signals from the existing pool-stats + hashrate snapshots: Nakamoto coefficient, HHI concentration (with band label), avg block-time stability, difficulty-adjustment stability. Threshold-coloured values. New pure
   util pow-decentralization.ts (BigInt-safe difficulty CV). Reuses the shared PassportRow.

2. Mining-pool "Metrics" tab — /mining-pools/[slug]/metrics
   Enabled the previously-disabled tab. Shows hashrate, pool fee, blocks found (window + all-time), market share, last block as MetricsCardItem cards (matching the validator metrics layout). Secondary detail (hash, relative time,
   window/all-time counts) moved into tooltips. Extracted a shared PassportRow + signalColors component reused across panels.

3. Emission / Supply — moved into /networks/monero/tokenomics
   PoS/PoW-conditional tokenomics cards (Gini stays blurred pending data): circulating supply, block reward (tail 0.6 XMR), annual issuance, annual inflation, stock-to-flow, emission phase. New pure util monero-emission.ts (deterministic
   emission math: MONEY_SUPPLY, tail floor, estimateBaseRewardAtomic, handles Monero being past tail where circulating > the base-formula asymptote).

4. Block telemetry cards — /networks/monero/blocks (bucket B — schema + indexer change)
   New chain-wide MoneroBlock table + migration. The monero-pool-attribution job now persists per-block fields the indexer REST already returned but we discarded (reward, weight, tx count, versions, canonicality) — no new upstream call — and
   mirrors reorg canonicality flips into the new table. Cards: avg block reward (real, incl. fees), avg block weight, consensus version + share, reorg rate. New util monero-block-metrics.ts. Telemetry persistence is isolated (its own
   try/catch) so a malformed block can't abort pool attribution.

5. Transaction metrics cards — /networks/monero/tx
   Total transactions, TPS, avg tx fee — derived purely from the MoneroBlock table (no new fetch/pipeline). Avg fee uses the Monero identity block reward = subsidy + fees (fee = (Σreward − tail·blocks)/Σtx), reusing the emission util. New util
   monero-tx-metrics.ts.

[m1amgn]

Summary

Ships the Monero / PoW analytics slices from #642 that have a real data source, and triages the rest of the ideas list. All metrics are derived server-side from our own PostgreSQL (indexer → DB → service → SSR); no browser-side blockchain
or pool-API calls.

What this PR ships

Connected miners (T1) — per-pool live miner counts from the pool APIs, persisted as a freshness-gated gauge (MiningPool.minersCount + minersUpdatedAt, hourly). Shown as a Miners column on the network mining-pools table with a
tracked-pools total. p2pool is labeled separately (sidechain participants, not stratum workers) and excluded from the total; nanopool has no stats endpoint → honest no-data; values older than 24h read as no-data.

Fee vs subsidy + tail emission security (T2) — fee share of miner revenue on the Stats tab and a tail-emission-security card on Tokenomics, both derived from the existing 24h MoneroBlock reward aggregate (fees = max(0, reward − 0.6 XMR × blocks)). Reuses the same fee split as the avg-fee card so the two can't disagree.

Pool dominance over time (T4) — new MoneroPoolDailyShare table + a daily catch-up indexer job that materializes per-day, per-pool share (numerator = canonical block-hash attribution, denominator = canonical MoneroBlock, unknown/solo
= residual). Multi-series chart on the Stats tab, gated until ≥7 days of history. Job resumes from the first gap day, so a transient failure can't leave a permanent hole in the series.

Dev health (T3) — open PRs, PR-corrected open issues, and active maintainers (unique commit authors, 30d) on /networks/{chain}/dev for all chains, fed by the existing daily GitHub job via the Search API (no per-repo fan-out).

Data-honesty notes

• Miners total is pool-scoped ("tracked pools only") — solo/gupax miners and unregistered pools are invisible by construction.
• Open issues subtract org-wide open PRs (GitHub bundles PRs into open_issues_count); it's an approximation, forks can add small noise. Clamped ≥ 0.
• Dominance denominator is the true canonical block count per day, so named-pool shares are never inflated by the unattributed residual.

[m1amgn]

Real ideas that need your decision before we build:

1. Node analytics (§4) — geo/Tor/I2P/versions/peers need our own P2P crawler (separate service). Build it, or drop §4?
2. Pool static info — stratum endpoints, server geo, software: pool APIs don't expose these. OK with a manually curated table?
3. Mempool / confirmation depth (§6, §9) — our indexer doesn't serve mempool. Worth the indexer work?
4. Profitability calculator (§7) — doable; what should the user input (hashrate? hardware? electricity cost)?
5. "validators + pools in one table" — what do rank / commission mean for a pool vs a validator?
6. Tail emission security ratio (§10) — implemented as fees / total block reward (24h). Confirm that's the intended definition.
7. Privacy metrics (§10) — ring size, RingCT/CLSAG share, decoy/output-age need raw-tx parsing in the indexer. You said "not even half needed" — which 2–3, if any?