[ANN] DogKong v2 - Experimental cryptocurrency (CPU miner)

Topic ID
5595220
Thread author
MioziM
Thread added to tracking
2026-09-29 00:10 UTC
Last scan
2026-10-05 00:13 UTC
Generated
2026-10-05T00:13:03Z
Original thread on bitcointalk.org β†—

About the coin (primary summary)

  • What coin: DogKong v2 (ticker not specified)
  • Mining algorithm: not specified
  • CPU-only or not: CPU-only (positioned as a CPU miner)
  • Brief description: This is an experimental cryptocurrency focused on CPU mining. The announcement warns that mining now may cause a fork, and recommends keeping wallet keys and the recovery phrase safe until the final update is released.
  • Where to mine/pool: not specified
  • Wallet/links: not specified
  • Community reaction: no replies yet, no reaction.

Update history (deltas)

2026-10-01 00:19 UTC β€” 1 new msg.

Main topic of new posts: User MioziM posted a link to an archive with a new version of DogKong v2 (release V._6) on GitHub.

Key news/updates:

Issues/complaints:

  • (no mentions of issues or complaints)

Overall tone: neutral (purely informational message without evaluation).

2026-10-05 00:13 UTC β€” 6 new msgs.

Main topic of new posts: Discussion of synchronization issues with DogKong v2, release of a fixed version v8.1, and promotion of the project through marketing and a Telegram group.

Key news/updates:

  • Fixed version dogkongv8.1 released with protection against saving corrupted blocks; release link on GitHub.
  • Direct link to the explorer for checking synchronization provided: https://dogkong.duckdns.org/search?q=
  • Telegram group created for discussion: https://t.me/+hqDQl2Sz_fU4MmQx
  • Recommendation to clear the *data* folder and restart the miner after saving the wallet file.

Issues/complaints:

  • User Nauda reports that the client gets stuck at block 12260 (or 11199) in version V8 and does not synchronize.
  • It is noted that blocks from 13999 onward were saved in a corrupted state, causing synchronization failures.

Overall tone: Positive – developers promptly fix bugs, provide recovery instructions, and actively promote the project.