cryptosnif
Bitcoin Gold (BTG)
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
This dossier examines the documented purpose and mechanisms of native Bitcoin Gold (BTG) on the bitcoin-gold-mainnet network. The objective is to evaluate the project's stated goals against the available documentary evidence, without performing live network observation or independent operational verification.
Established facts
The pinned Bitcoin Gold Core README describes BTG Core as the original client, derived from Bitcoin Core. It gives a historical fork boundary at Bitcoin block 491406 and identifies the subsequent start of separate-chain mining. These historical maintainer statements do not establish current mining operation or a verified replay of the split. The stated design goal is reducing mining concentration through GPU-oriented proof of work described as resistant to specialized hardware. The source lists Equihash, per-block difficulty adjustment, replay protection and distinct address prefixes as launch-time differences. It also describes preservation of Bitcoin features such as SegWit, without a reproduced use of those features here. Historical equal balances at the fork boundary supply no present ownership, spendability or claim instruction. No wallet import, balance recovery, mainnet connection or mining test was performed in this review.
Unknowns
Present independent control, beneficial ownership, actual usage, client adoption, supply distribution, market concentration, liquidity depth, and the complete incident history remain unverified. No independently reviewed criterion observation is admitted in this documentary lot regarding identity, usage, token role, supply, concentration, value capture, control, security, governance, accountability, incidents, continuity, or execution.
Consequences
The historical fork statements establish the software review's scope, while current mining and deployment require separate observations. Hardware-resistance and concentration claims need dated mining and participant evidence. The listed replay protection and address distinctions provide features to reproduce in a scoped test. Historic fork balances supply no current ownership or spendability result.
Verdict
Operational strength remains unproven. The project is unrated with 0% scoring coverage. Critical missing essential criteria include identity, supply, and control. The lack of independent verification prevents any assessment of current viability or risk.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. These must be followed by calibration and editorial review to move beyond the current documentary-only status.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Hashrate concentration, consensus rules, full-node independence.
Inspect the evidence
Sources behind this analysis
Bitcoin Gold: pinned BTCGPU/BTCGPU overview (1b85f0953725)
The pinned Bitcoin Gold Core README describes BTG Core as the original client, derived from Bitcoin Core. It gives a historical fork boundary at Bitcoin block 491406 and identifies the subsequent start of separate-chain mining. These historical maintainer statements do not establish current mining operation or a verified replay of the split. The stated design goal is reducing mining concentration through GPU-oriented proof of work described as resistant to specialized hardware. The source lists Equihash, per-block difficulty adjustment, replay protection and distinct address prefixes as launch-time differences. It also describes preservation of Bitcoin features such as SegWit, without a reproduced use of those features here. Historical equal balances at the fork boundary supply no present ownership, spendability or claim instruction. No wallet import, balance recovery, mainnet connection or mining test was performed in this review. No software, node, transaction, governance vote or benchmark was executed in this review. Current deployed versions, participant independence, economic rules, usage, supply, ownership, concentration, liquidity and the complete incident record remain independently unverified. Descriptions of architecture establish a research scope and supply no investment-return forecast or operational safety guarantee.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.