From 9f8ab855be18e4504462cbaad27faa545bea18cc Mon Sep 17 00:00:00 2001 From: Bitcoin Universe Admin Date: Wed, 23 Sep 2026 17:44:44 +0000 Subject: [PATCH 01/11] docs(audit): annotate explicit-network isolation requirements without changing behavior --- frontend/src/app/universe/chain-network.ts | 36 ++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/frontend/src/app/universe/chain-network.ts b/frontend/src/app/universe/chain-network.ts index 7ba848b5c9..09567731b7 100644 --- a/frontend/src/app/universe/chain-network.ts +++ b/frontend/src/app/universe/chain-network.ts @@ -36,6 +36,42 @@ export function configuredChainNetworks(env: Env): ChainNetworkConfig { return lastParsed; } +/** + * IMPLEMENTATION-HANDOFF [M23-NET] | defect F-M23-02 | coverage C-NET-EXPLICIT + * Preparation only, 2026-09-23. Dependency: M23-BASE; coordinate all callers + * of configuredChainNetworks and chainNetwork before changing their contract. + * Verified at 079dc0d79755bc986bfae3288ffe0e479da3e1f6: malformed JSON or an + * explicit unsupported network is dropped here, then chainNetwork defaults + * to mainnet. chain-network.spec.ts deliberately asserts this for Dogecoin + * signet/testnet3. This violates the requested separation of test and mainnet + * contexts; it is not evidence of a transaction having been sent incorrectly. + * Governing requirement: user brief network isolation (lines 41-49), with + * Bitcoin Signet specified by BIP 325; do not infer Signet support for other + * chains from Bitcoin's selector or from a generic list of network names. + * 1. Preserve missing configuration and omitted-chain mainnet defaults, but + * represent an explicitly invalid map/entry as a typed unavailable result + * with a reason. Do not erase the error into an absent entry or substitute a + * different network. Preserve valid entries independently where safe. + * 2. Validate keys against the actual Explorer chain registry and each + * authority's declared supported networks. Pin that registry contract first; + * do not derive support from CHAIN_NETWORK_VALUES alone or invent new chains. + * 3. Update callers to stop affected API requests, clear prior-context data, + * and render a recoverable configuration error. Keep request/cache/query + * identities chain-and-network bound; retry only after valid configuration. + * 4. Extend chain-network.spec.ts with invalid JSON, invalid explicit network, + * unknown chain, valid object/string, omitted defaults, and configuration + * correction. Add consumer tests proving zero wrong-network requests and no + * stale mainnet data after an invalid test-network selection or reconnect. + * Commands (declared, not executed on SERVER in this preparation): + * cd frontend; npm run test:ci -- src/app/universe/chain-network.spec.ts + * npm run lint; npm run build:universe + * Acceptance: explicit invalid input never becomes a mainnet request; absent + * defaults stay mainnet; valid chain-specific testnet reads survive Bitcoin + * selector changes, refresh and reconnect. Record actual supported-network + * consumer evidence separately from unit tests. No mainnet test transactions. + * Rollback: revert the coordinated parser/caller change together; preserve + * production defaults and network-scoped caches. No database migration here. + */ function parse(raw: unknown): ChainNetworkConfig { if (raw === undefined || raw === null || raw === '') {return {};} let value: unknown = raw; From 036208e47e8920d104da3e7070d98e16a256c216 Mon Sep 17 00:00:00 2001 From: Bitcoin Universe Admin Date: Wed, 23 Sep 2026 17:46:42 +0000 Subject: [PATCH 02/11] docs(audit): annotate missing release evidence archive members --- .../workflows/universe-release-artifact.yml | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/.github/workflows/universe-release-artifact.yml b/.github/workflows/universe-release-artifact.yml index 07d2e1acef..53717d096f 100644 --- a/.github/workflows/universe-release-artifact.yml +++ b/.github/workflows/universe-release-artifact.yml @@ -120,6 +120,43 @@ jobs: # compare it against the running release and refuse the hard link when it # differs. That check belongs there, where both trees are visible; here # only one of them is. + # IMPLEMENTATION-HANDOFF [M23-PACK] | F-M23-01 | C-RELEASE-ARCHIVE + # Preparation only, 2026-09-23. Prerequisites: M23-BASE and the existing + # qualified acceptance work; this is not permission to bypass that gate. + # Verified at 079dc0d79755bc986bfae3288ffe0e479da3e1f6: this step copies + # two files into stage/docs, but tar below names only backend/frontend/ + # scripts/production/RELEASE-MANIFEST.json. docs is therefore absent. + # release.sh:gate_qualified_acceptance requires the candidate's protocol + # manifest and rooted evidence before cutover. A successful checkout-side + # qualification does not make the extracted archive self-contained. + # Governing sources: scripts/universe/release.sh:gate_qualified_acceptance; + # protocol-contract.mjs:verifyEvidence; user release/evidence requirements. + # 1. Stage the protocol manifest, acceptance envelope and every evidence + # file referenced by that envelope under a candidate-contained root. + # Enumerate and validate the exact reference closure using the existing + # verifier's schema/path rules. Reject missing files, hash mismatches, + # absolute/traversal paths and symlinks escaping the candidate. Do not + # copy credentials, whole workspaces, or unsupported success assertions. + # 2. Include those staged paths in the archive member list. Keep the + # production artifact and evidence bound to the accepted full source SHA + # and production configuration; do not use a mutable external evidence root. + # 3. Extract the actual archive into a new directory, with the checkout + # unavailable, and run the same protocol-contract --release invocation + # with --acceptance-root set to the extracted candidate. Assert all + # referenced evidence members exist with their expected hashes before + # upload. Keep all existing branding, identity and release gates. + # 4. Extend scripts/universe/release-gates.test.mjs with actual tar member + # and extracted-candidate qualification cases, not regex presence alone. + # Cover missing docs, missing nested evidence, tampered bytes, escaped + # symlinks, stale revision and a valid Signet-qualified mainnet envelope. + # Commands declared, not executed on SERVER in this preparation: + # node --test scripts/universe/release-gates.test.mjs + # node --test scripts/universe/protocol-contract.test.mjs + # bash -n scripts/universe/release.sh + # Acceptance: the exact uploaded archive qualifies after extraction with + # no checkout dependency; failed qualification prevents publication/cutover. + # Rollback: retain the previous immutable artifact, routing and compatible + # configuration. No database migration or live transaction is needed here. - name: Pack id: pack run: | From f364046c91facde0dd339ac129b17378c58f412f Mon Sep 17 00:00:00 2001 From: Bitcoin Universe Admin Date: Wed, 23 Sep 2026 17:47:54 +0000 Subject: [PATCH 03/11] docs(audit): annotate capability freshness and operational recovery acceptance --- backend/src/api/capabilities.routes.ts | 46 ++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/backend/src/api/capabilities.routes.ts b/backend/src/api/capabilities.routes.ts index 54106f8b49..e20c95154f 100644 --- a/backend/src/api/capabilities.routes.ts +++ b/backend/src/api/capabilities.routes.ts @@ -12,6 +12,52 @@ class CapabilitiesRoutes { public initRoutes(app: Application): void { app.get(config.MEMPOOL.API_URL_PREFIX + 'capabilities', async (req: Request, res: Response) => { try { + /* + * IMPLEMENTATION-HANDOFF [M23-HEALTH] | F-M23-03, F-M23-04 + * Coverage: C-BTC-INDEX, C-STATS-FRESH, C-MINING-READY, C-ADDRESS-READY. + * Preparation only, 2026-09-23. Dependencies: M23-BASE, M23-NET. + * Live operational observation, not a mainnet functional test: + * /api/v1/capabilities at 2026-09-23T17:39:41.778Z reported address + * index unavailable, statistics lag 80936 seconds, and mining ready + * despite its indexed height 968172 versus backend-info Core 968299. + * The running backend named 537235052, not the inspected branch tip. + * Verified current-source cause for the readiness gap is in + * capabilities.ts:$miningReport: indexed = total > 0 && poolCount > 0; + * highest/newest are reported but never constrain readiness. Causes + * of the actual address outage and stalled ingestion remain unresolved. + * Sources: Bitcoin Core 31.0 getblockchaininfo RPC; repository + * capabilities.ts, bitcoin/address-index.ts, backend-info-checkpoint.ts; + * user requirements for authoritative freshness and truthful states. + * 1. In capabilities.ts:$miningReport compare the indexed checkpoint + * to a fresh, same-network Core observation and expose the existing + * indexedTip/bitcoinCoreTip/lagBlocks fields. Define a bounded allowed + * lag in the owning configuration contract, tested at its boundary; + * do not infer collector freshness from block mining timestamps alone. + * Preserve unknown separately when a reference checkpoint is absent, + * stale or inconsistent. Existing historical rows must not prove ready. + * 2. Keep this endpoint, release gates and frontend consumers on that + * shared result; coordinate any response/type changes. Exercise cache + * expiry and network identity so a prior ready response cannot conceal + * dependency loss or survive a chain change. Do not substitute HTTP 200 + * or a row count for the final outcome. + * 3. Diagnose the live outage through authorized service/configuration + * identity, cookie freshness, index reachability and ingestion logs. + * Compare Core, completed block cache, SQL tip, address index and + * statistics collector independently. Do not assert one common cause + * without evidence; never restart an active reorg/indexer blindly. + * 4. Add focused tests in the existing capabilities test suite (locate + * before editing): fresh/lagged/unknown tip, database loss, empty rows, + * pool metadata missing, observation expiry, recovery and reorg. + * Run cd backend; npm run test:ci -- --runInBand; npm run lint; + * npm run build. Commands are declared, not executed on SERVER here. + * Acceptance additionally requires real Signet API-to-UI address, + * UTXO/history, mining and statistics outcomes across reload/reconnect; + * faults belong in an isolated environment, not production. Preserve + * historical coverage and accurately report gaps, without fake backfill. + * Rollback: retain the prior artifact, configuration and database backup; + * no destructive rescan, migration or permission relaxation is authorized + * merely by this annotation. Record the verified cause before repair. + */ const report = await capabilities.$report(); res.header('Pragma', 'public'); res.header('Cache-control', 'public'); From 161b7bdd0685631975b95da4f9017db86ba88915 Mon Sep 17 00:00:00 2001 From: Bitcoin Universe Admin Date: Wed, 23 Sep 2026 17:52:00 +0000 Subject: [PATCH 04/11] docs(audit): record partial mainnet preparation baseline, findings and remaining gates --- .../mainnet-20260923/README.md | 55 +++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 docs/implementation-prep/mainnet-20260923/README.md diff --git a/docs/implementation-prep/mainnet-20260923/README.md b/docs/implementation-prep/mainnet-20260923/README.md new file mode 100644 index 0000000000..814f72a904 --- /dev/null +++ b/docs/implementation-prep/mainnet-20260923/README.md @@ -0,0 +1,55 @@ +# Mainnet preparation, 2026-09-23 + +## Decision and evidence limits + +**NO-GO. Preparation is partial; implementation, full functional acceptance and public release are not complete.** No production configuration, runtime logic, permissions, database, live transaction or deployed artifact was changed by this preparation. + +The isolated GitHub branch is `audit/mainnet-prep-20260923-1745`, based on `079dc0d79755bc986bfae3288ffe0e479da3e1f6` (develop). At inspection main was `b2009ac8e2e6a8f594659cc526edd74eea1c534a`; it added a merge commit with no source-tree differences. The source-annotation revision before this index is `f364046c91facde0dd339ac129b17378c58f412f`. Its three commits add 119 comment lines with no deletions. This index is a new non-executable document. + +The SERVER checkout is `D:\universe\mempool\mempool`, whose HEAD file names main. Uncommitted changes, actual Git worktree registration and current service/process state were not established: three Remote Desktop Commander terminal attempts, including read-only Git and Node version commands, were blocked by safety checks. Do not bypass those restrictions or alter the shared checkout. The GitHub branch is real; a prepared SERVER Git worktree is not claimed. + +The created SERVER handoff directory is `D:\universe\mempool\audits\implementation-prep-20260923-1745\mempool_HANDOFF_2026-09-23`. Directory creation alone does not prove a prompt or ZIP was saved; consult the final handoff delivery receipt. Workspace AGENTS.md was read but is not redistributed because it contains credentials. Treat secrets as credentials, never as report content. + +## Source annotation index + +| ID | Actual source anchor | Dependencies | Preparation | Functional status | +|---|---|---|---|---| +| M23-NET | frontend/src/app/universe/chain-network.ts, parse, IMPLEMENTATION-HANDOFF [M23-NET] | M23-BASE | ANNOTATED | FAIL F-M23-02; no repair | +| M23-PACK | .github/workflows/universe-release-artifact.yml, Pack step, IMPLEMENTATION-HANDOFF [M23-PACK] | M23-BASE; existing qualified acceptance work | ANNOTATED | FAIL F-M23-01; no repair | +| M23-HEALTH | backend/src/api/capabilities.routes.ts, capabilities.$report consumer, IMPLEMENTATION-HANDOFF [M23-HEALTH] | M23-BASE, M23-NET | ANNOTATED at API integration point | FAIL F-M23-03/F-M23-04; owning mining helper still needs file-local annotation and implementation | +| M23-BASE | Isolated worktree and running identities | none | BLOCKED on SERVER terminal | NOT TESTED | +| M23-AUTHORITY | backend-apis chain health and named indexers | M23-BASE, M23-NET | NOT ANNOTATED in owning repositories | Operational failures below; individual journeys NOT TESTED | +| M23-COVERAGE | scripts/universe/acceptance-matrix.mjs and owning API registry | M23-BASE | Existing source reviewed; new work not annotated | NOT TESTED; denominator unreconciled | +| M23-ACCEPT | Actual services, UI and protocol operations | all relevant repairs | NOT IMPLEMENTED | NOT TESTED | +| M23-RELEASE | release.sh, accepted artifacts, routing and public endpoints | all acceptance gates | NOT EXECUTED | BLOCKED | + +## Confirmed defects and operational observations + +1. **F-M23-01, release packaging.** The pinned workflow stages `docs/protocols/PROTOCOL-COVERAGE.json` and `docs/acceptance/qualified-release-evidence.json`, then runs `tar -czf "$out" -C "$stage" backend frontend scripts production RELEASE-MANIFEST.json`. Neither document enters the archive. `scripts/universe/release.sh:gate_qualified_acceptance` requires a manifest and candidate-contained evidence before cutover. Repair the member list and complete rooted evidence closure, then qualify the extracted actual artifact without access to the checkout. Missing evidence, wrong hashes, traversal, escaping symlinks and stale candidate identities must fail. Extend `release-gates.test.mjs` beyond string-presence assertions. + +2. **F-M23-02, network isolation.** `parse` drops malformed JSON and unsupported explicit network entries; `chainNetwork` then uses mainnet. The current unit tests intentionally expect this. In the isolated Linux sandbox, actual TypeScript source transpilation reproduced Dogecoin signet and malformed JSON falling back to mainnet. No API request or transaction was sent. Preserve genuinely absent production defaults, but reject explicit invalid contexts through a typed unavailable state, suppress wrong-network requests, clear stale context and update all parser consumers together. + +3. **F-M23-03, mining readiness.** In pinned `backend/src/api/capabilities.ts:$miningReport`, `indexed = total > 0 && poolCount > 0` decides readiness; highest indexed height and data age do not participate. Compare a completed indexed checkpoint to a fresh same-network node checkpoint. Do not equate time since the last mined block with collector health; represent missing/stale reference information separately. + +4. **F-M23-04, Bitcoin operational degradation.** First-party public operational GET observations on 2026-09-23, not mainnet functional tests: + - `/api/v1/backend-info`: release `537235052`, node blocks/headers 968299, initialBlockDownload false, completed explorer checkpoint 968172, a 127-block difference. GitHub resolves that reported prefix to `537235052b9f2d2908aa70c41c4e66c79fcd5e4a` (September 19), not the inspected main revision. + - `/api/v1/capabilities`, generated 17:39:41.778Z: addressLookup unavailable, configured address index did not answer, backendKind electrum. Statistics degraded with 80936 seconds lag. Mining ready despite indexed tip 968172 and 82474 seconds reported age. + - The outage/ingestion root causes are unresolved. Inspect authorized service identity, index reachability, cookie/configuration freshness, Core/cache/SQL checkpoints and collector logs before selecting a repair. Do not blindly restart active indexers or reorg processing. + +5. **F-M23-05, authority availability.** `/api/v1/chains`, observed 17:39:53.152Z, reported ready=false for Bitcoin, Dogecoin and Zcash, with overlay release `fcdc2e2f3bd226bead63cdf0b81fad1ef1ad45bd`. Bitcoin included ten unconfigured authorities and numerous stale/lagged authorities; ready/qualified did not always mean complete historical coverage. Dogecoin block/address history authorities were unavailable; doginals/drc20/dunes were 1380833 blocks behind the node. Zcash zerdinals/zrunes/zrc20 were partial and unqualified. These are operational failures, not proof that each individual transaction journey was executed. Preserve indexing progress, bound load and resolve each authority's own prerequisite. + +6. **F-M23-06, Zcash synchronization inconsistency.** The same response published synced=true and initialBlockDownload=true. Root cause is unresolved. Zcash 6.12.2 RPC documents `initial_block_download_complete`, whose meaning is opposite to Bitcoin's `initialblockdownload`. Inspect the actual deployed node implementation and normalization before changing semantics; do not assume field parity between node families. + +## Coverage and research boundaries + +The pinned protocol roster at `docs/protocols/PROTOCOL-COVERAGE.json` identifies 39 protocols, registry 1.1.0, owner backend-apis revision `7ec4602e7a5dcd6495268ae64698280657cc9c73`. Its seven historical readable declarations are not current test passes. Its read descriptors do not cover the whole application. CAT20/Fractal is the 39th identity outside the three-chain response; absence there is not independently established as a defect. + +The existing `acceptance-matrix.mjs` intentionally records `operationDenominatorReconciled: false` and `FUNCTIONAL NO-GO`. Reconcile its actual source candidates rather than changing those fields to claim completion. Retain all offered APIs, public UI, admin authorization, workers, node/indexer paths, portfolio and observatory/tool capabilities. Do not invent minting, trading or key custody merely because a protocol supports them; do not exclude an actually offered integration because an older README lacks it. + +Primary sources reviewed include Bitcoin Core 31.0 getblockchaininfo RPC, BIP 325 Signet, Zcash 6.12.2 getblockchaininfo RPC, Esplora API and Ord API documentation, plus pinned repository contracts. Complete protocol-by-protocol governing specification/version research and operation traceability were not achieved. Missing pins, exact authority prerequisites and unexecuted checks remain explicit work, not completed research. + +## Validation and next sequence + +Exact UTF-8 snapshots of all three baseline and annotated files were checked against six Git blob hashes. TypeScript 5.8.3 transpilation produced identical comment-stripped JavaScript before/after. Parsed workflow YAML structures were equal. An isolated tar-member reproduction confirmed missing docs. The preparation patch applied to disposable copies and reproduced the annotated bytes. Environment: Linux sandbox, Node v22.16.0, not the SERVER-pinned Node 24.19.0. These results prove preparation/reproduction properties only, not a full build, lint, project typecheck, Signet pass or release. + +Continue M23-BASE, network isolation and authoritative state repair, then per-authority/protocol requirements, persistence/recovery, API/UI integration, complete operation reconciliation and real acceptance, then packaging and gated release. Preserve existing work and first-party-only data infrastructure. Full Signet PASS is functional acceptance where supported; use an explicitly justified supported testnet otherwise. No mainnet funds or test transactions. Test-network/mainnet differences need offline/configuration evidence. Public release follows only after every applicable operation passes and every repair/dependency regression is evidenced. No release is claimed here. From 6aaf932ff58d4635091969611215a8961d2a7a41 Mon Sep 17 00:00:00 2001 From: Bitcoin Universe Date: Wed, 23 Sep 2026 20:57:02 +0000 Subject: [PATCH 05/11] fix(network): refuse explicit invalid chain network settings instead of reading mainnet M23-NET, F-M23-02. A malformed UNIVERSE_CHAIN_NETWORKS value or an unsupported network used to be dropped with a warning, and the chain then read mainnet. An explicit setting that is wrong now resolves to a typed unavailable result with a reason; absent or omitted settings still read mainnet. Keys and networks are pinned to the overlay's explorer-context contract (dogecoin, zcash, fractal). Every caller changes together: chain reads are deferred and fail with ChainNetworkUnavailableError before any request, the picker skips the chain and names the setting invalid, the websocket opens no socket, bookmarks and visits are never filed under a substitute network, and the dashboard, mining and chain pages render a recoverable configuration error. Co-Authored-By: Claude Opus 5.5 --- .../master-page/master-page.component.ts | 18 +- .../chain-dashboard.component.html | 8 +- .../chain-dashboard.component.ts | 8 +- .../chain-dashboard.service.ts | 6 +- .../chain-mining.component.html | 8 +- .../chain-dashboard/chain-mining.component.ts | 8 +- .../chain-docs/chain-docs.component.ts | 9 +- .../universe/chain-network-consumers.spec.ts | 86 ++++++++ .../src/app/universe/chain-network.spec.ts | 80 +++++++- frontend/src/app/universe/chain-network.ts | 188 ++++++++++++------ .../multichain-explorer.component.ts | 28 ++- .../app/universe/universe-api.service.spec.ts | 51 ++++- .../src/app/universe/universe-api.service.ts | 124 ++++++------ .../app/universe/universe-local.service.ts | 15 +- .../universe/universe-websocket.service.ts | 12 +- .../zcash-viewing-key-workspace.component.ts | 5 +- 16 files changed, 480 insertions(+), 174 deletions(-) create mode 100644 frontend/src/app/universe/chain-network-consumers.spec.ts diff --git a/frontend/src/app/components/master-page/master-page.component.ts b/frontend/src/app/components/master-page/master-page.component.ts index 9b72995f6f..77377a54ef 100644 --- a/frontend/src/app/components/master-page/master-page.component.ts +++ b/frontend/src/app/components/master-page/master-page.component.ts @@ -7,7 +7,7 @@ import { EnterpriseService } from '@app/services/enterprise.service'; import { NavigationService } from '@app/services/navigation.service'; import { StorageService } from '@app/services/storage.service'; import { ChainHealthService, ChainHealthState } from '@app/universe/chain-health.service'; -import { chainNetwork } from '@app/universe/chain-network'; +import { resolveChainNetwork } from '@app/universe/chain-network'; import { healthServiceSummary, nodeHealthLabel, readHealth } from '@app/universe/multichain-explorer/chain-health'; import { UniverseLocalService } from '@app/universe/universe-local.service'; import { mainReady } from '@app/universe/main-ready'; @@ -244,7 +244,8 @@ export class MasterPageComponent implements OnInit, AfterViewInit, OnDestroy { } chainCapability(capabilities: ChainCapabilityEnvelope[], chain: ExplorerChain): ChainCapabilityEnvelope | undefined { - return capabilities.find((capability) => capability.chain === chain && capability.network === this.resolvedNetwork(chain)); + const network = this.resolvedNetwork(chain); + return network === null ? undefined : capabilities.find((capability) => capability.chain === chain && capability.network === network); } chainState(capability: ChainCapabilityEnvelope | undefined): string { @@ -252,12 +253,17 @@ export class MasterPageComponent implements OnInit, AfterViewInit, OnDestroy { } chainNetwork(chain: ExplorerChain): string { - return this.networkLabel(this.resolvedNetwork(chain)); + const network = this.resolvedNetwork(chain); + return network === null ? $localize`:@@master-page.network-setting-invalid:Network setting invalid` : this.networkLabel(network); } - /** Bitcoin follows the selector; every other chain reads its configured network. */ - private resolvedNetwork(chain: ExplorerChain): string { - return chainNetwork(chain, (this.stateService.network || 'mainnet') as ExplorerNetwork, this.stateService.env); + /** + * Bitcoin follows the selector; every other chain reads its configured + * network, or null when that configuration is invalid and nothing is read. + */ + private resolvedNetwork(chain: ExplorerChain): string | null { + const resolved = resolveChainNetwork(chain, (this.stateService.network || 'mainnet') as ExplorerNetwork, this.stateService.env); + return resolved.available ? resolved.network : null; } chainDetail(capability: ChainCapabilityEnvelope | undefined): string { diff --git a/frontend/src/app/universe/chain-dashboard/chain-dashboard.component.html b/frontend/src/app/universe/chain-dashboard/chain-dashboard.component.html index dbc1717538..e225963ab4 100644 --- a/frontend/src/app/universe/chain-dashboard/chain-dashboard.component.html +++ b/frontend/src/app/universe/chain-dashboard/chain-dashboard.component.html @@ -8,6 +8,12 @@

{{ profile.name }} dashboard

+ + +

{{ profile.name }} mining

+ + +

Dogecoin is merged mined: miners work on Litecoin's scrypt proof of work and commit to Dogecoin blocks through AuxPoW, so most Dogecoin blocks are found by Litecoin pools.

@@ -27,7 +33,7 @@