Lynx Blockchain
  • Welcome
  • Technical Evolution and Architecture Overview
  • History of Lynx
    • Evolution of a Blockchain
    • Hybrid Proof of Work (HPoW) Protocol
    • Pioneering Blockchain Data Storage
    • Evolution to Proof of Stake
    • Next Generation Data Storage Architecture
    • Preserving Knowledge
  • Lynx Core
    • Hardware and System Requirements
    • Lynx Dynamics
    • Open Source
    • Core Parameters and Strategy
    • Sustainability
    • Circulating Supply Analysis
    • Locked Addresses
    • Data Storage
      • auth
      • fetch
      • fetchall
      • store
      • status
      • list
    • Understanding the Encryption Option
    • Understanding Lynx Staking Wait Times
    • Understanding Asset Retrieval Times
    • Understanding Block Time Targeting in the Lynx Blockchain
    • Understanding the Lynx Blockchain Statistics Report
  • Lynx Administration
    • Public Peer Nodes
    • Understanding Blockchain Bootstrap Files
      • Bootstrap Extraction Script
      • Bootstrap Creation Script
    • How to Sweep a Lynx Wallet
    • Enable/Disable Staking
  • Clevver
    • Revolutionizing Digital Preservation
    • Permanent Storage for Digital Assets
    • Permanent Digital Archives for Journalism
    • How did Clevver originate?
    • Shortened URL Support
    • Assigning Tags to Assets
    • How to delete content
    • Clevver Terms of Service Agreement
  • Clevver API
    • Public Methods
      • Batches
      • Files
      • User
  • ElectrumX
    • Lynx ElectrumX nodes
    • Build Script Details
  • External Links
    • Lynx Explorer
    • Lynx Github
    • Lynx Uptime Report
    • Clevver Website
  • Lynx Bootstraps
  • Wallet Links
    • Komodo Wallet
    • Wally.id Wallet
    • Lynx Paper Wallet
  • Social Links
    • Lynx Discord
    • Lynx on Bluesky
    • Clevver on Bluesky
  • Exchange Links
    • FreiXLite (LYNX/LTC)
  • FreiExchange (LYNX/BTC)
  • Komodo Wallet (SWAP)
  • XredX (LYNX/LTC)
  • XredX (LYNX/DOGE)
  • XredX (LYNX/IL8P)
Powered by GitBook
On this page
  1. Lynx Core

Locked Addresses

Why were two suspicious addresses locked?

PreviousCirculating Supply AnalysisNextData Storage

Last updated 11 months ago

In short, because the addresses contain provably stolen coins.

A bit of history. Long ago, concerning the block numbers listed below, someone attacked Kittehcoin (before the Lynx development team took over the project). The attack exploited a weakness that allowed the attacker to define the mining reward amount. At that time, the default mining reward was only 2,000 MEOW per block. However, the blocks below show the reward was changed to 2 billion each time the attack was executed. The pattern is easy to identify. The Lynx team fixed the security hole when they ported the latest Litecoin code to the (previously named) Kittehcoin chain. While the attack vector was closed, the coins still remained in circulation, increasing the circulating supply by approximately 28 billion coins.

  • Block: 1327713 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1327710 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1327704 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1327689 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1327646 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1327595 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1313353 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1313352 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1299977 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1299963 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1293504 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1293496 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1286358 — Coinbase Reward: 2,000,000,000 — Address:

  • Block: 1256813 — Coinbase Reward: 2,000,000,000 — Address:

The code change implemented in v0.16.3.9 includes a restriction for the

  • KJ2MGS3jq4DPkVmE1ephMCbT7ojDcDSJRG

  • KSho9zUYrFdTPPxfF6ye9sLurgKygeUEzL

The attacker(s) now has two options:

Option 1: Do nothing.

  • The coins in those wallets will never be spendable. All future versions of Lynx will include the lockdown code preventing the coins from being spent. The consensus of the network prevents the coins from being moved.

Option 2: Release the coins in exchange for a bounty.

  • Each of the two blocked addresses may keep 100,000,000 Lynx in their original addresses if they send the rest of the coins to this – and only this – address: KQoKm4bzQvDAwiiFsPz3AE4UJHkHBvX6Bz. Once the coins are received, the blocking code will be removed in future Lynx releases, and the 100,000,000 coins will revert to the attackers’ control.

  • If the coins are ever received at that address, a small portion will be used to reimburse the few Lynx holders who experienced theft (approximately Dec 5, 2019) from an R-value Attack. Then, the remainder of the coins will be verifiably burned. A schedule will be published, and the remaining stolen coins will be burned.

Why are we burning the stolen coins?

We’re burning the stolen coins because it’s the right thing to do. We have no interest in keeping them because it will erode trust in the Lynx project, which we take very seriously. These coins were created outside of the normal business rules of Lynx. Therefore, all Lynx holders paid for them. Lynx never had a pre-mine or ICO. The existence of the stolen coins harms every Lynx holder by suppressing the total value of the network market cap and reducing the total scarcity of the circulating supply. If these coins are burned, the total circulation should be reduced by roughly ~20%. We expect this will positively impact the entire Lynx network — and the community of users that support it.

Our general policy is not to police the Lynx blockchain. However, we made an exception here because of the size of the theft, the number of users it impacts (everyone), and it’s easy to trace on the blockchain. We hope most of the Lynx community accepts and supports this difficult decision.

K7Z3uThEHim6hvQBa1kqb6jwhp9QfynbyM
KPwNzFNnEUcKfiuW4dyVwm9sKvY9rP24Cp
KDbND8WQSXDhmEhEaV62TUH5GJaYxaVXVx
KJqhouB6FX2xnZkGqFXCR5NMdrBgYzgcyd
KKquAGVnSt33WpvRbYPhCcBuaqMSskkjDB
KGaQrKE4jNzS44ZAukmLCpX1jGgsNcJNqE
KFu5EBViCUuUQPNufc3LEQAThVBhfP2LZz
KEgVoShXe1uManCMWB7mifFyzDB6EjGibi
KJ2eg8U4vqHjThLx7tpW1TovgWgURYo5Mx
KEcJNXRM2JZKskLy7Fw3KtQqPhcczmEV3o
KFFjYVKCbsQhWdEDFegCjNVugp4fE3Gmpu
KNJpmWvoBnQ8fLkqoi8SbRBE1xBTrybZz4
KATtxFYoMwdcQJVsCJVDz2VD8K2KUpwqHt
KJxF5BY5zenfHtWrKGEEcPggRiJZFFrbJT
2 largest known single addresses on the Lynx blockchain:
Page cover image