Skip to content
BLACK CAT coinBLACK CATSOLANA MEME COIN

BLACK CAT / V6.2

Devnet proof-of-work whitepaper

This document describes the pinned Solana Devnet reward release and its Nine Lives schedule. BCAT here is a test token. This is a test launch, not a mainnet release or a promise of value, income, availability, or a successful claim.

Mining guide · CLI miner · Reward explorer

Download the black-and-white technical paper (PDF, seven pages). Includes architecture, proof encoding, reward and difficulty formulas, settlement, security assumptions and source references. Historical base specification dated 31 October 2026: it predates the day-19 hardening and 30-day claim amendments described below. Use this HTML page for those amendments. The historical technical PDF keeps protocol timestamps in UTC; website times use U.S. Eastern Time (EST/EDT). Neither document certifies mainnet readiness.

1. The release

BLACK CAT uses application-level mining rounds on Solana. A miner searches locally for a SHA-256 proof bound to the network, program, mint, policy, round, challenge, target, and miner wallet. A successful finalized transaction records a credit for that wallet and mining day. The credit becomes a token transfer only through a later successful claim.

The separate practice CLI uses a different preview program and pays zero BCAT. Its results are not reward credits. Consult the reward explorer for current finalized observations; a recorded credit is distinct from a completed payout. Service activation and on-chain round status can change independently.

Network
Solana Devnet
Reward program
9hFrNyoid3CPcrhq3861tWi2SMuz9KhMRX43d87Gtttn
Mint
EUPxu3GneEK5RbGNm1FcofVV59e7iFhFx8xtfkCm64hZ
Mining reserve
Bkv5G3FcEPv7p3hEDpKmyCCZRN4oJrVp9zUjmLybxtZb
Policy hash
b7424d6af8b53573e22fbd53cabbbb5a8c90a2aa4b57da0c70fdc5ba3b6f0ddf

2. Supply and Nine Lives

The Devnet genesis supply is 21 million BCAT, with nine decimal places: 19 million are allocated to the mining reserve and 2 million to the non-mining allocation. The schedule has nine consecutive lives of 365 days each, or 3,285 days. These are fixed life budgets and shares, not a halving schedule.

LifeReserve budget (BCAT)Maximum miner share
1200,00060%
2400,00050%
3600,00040%
41,000,00034%
51,500,00030%
62,000,00025%
73,000,00022%
84,300,00020%
96,000,00018%

Across the full 19 million reserve, the scheduled shares imply at most approximately 4.45 million BCAT credited to miners and at least approximately 14.55 million scheduled for burn, subject to base-unit rounding. Those are policy ceilings and floors for the full schedule, not completed transfers or burns. Fewer wins and expired unclaimed credits increase the amount burned. Actual totals depend on transactions being executed and finalized.

Each day receives a scheduled slice of its life budget, using integer base-unit rounding and the remaining life budget. The miner share sets that day’s credit cap. The contract accepts at most 144 rewarded wins in a day. A win credits a rounded quantum up to the remaining daily cap; a wallet may accumulate multiple wins. The final rewarded win may receive only the remaining daily cap.

3. Difficulty and round freshness

The reward policy starts at an expected one billion hash attempts per accepted proof, with a range from one billion to one trillion. The bound on adjacent daily targets limits movement to at most twofold in either direction. Retargeting uses prior wins and elapsed time, and a target for a future day must be pinned on time to authorize reward mining. Expected attempts and search time are statistical averages, not guarantees.

Devnet difficulty amendment of 14 November 2026: the deployed contract schedules an effective target of floor((nominal target + 1) / 10000) - 1 from day 19, opening November 17, 2026 at 3:00 PM EST. This is an explicit one-time 10,000-fold change, followed by the existing bounded daily retargeting. Its expected-attempt range is approximately 10 trillion to 10 quadrillion. Earlier days and earned credits retain their rules. The stored policy hash identifies the base policy; the amendment is bound to a separately reviewed executable and commitment. Live target observations must be verified independently of this document. The versioned PDF describes the original base release; this paragraph records the later amendment.

After a winning proof, the release enters a pending state. Opening the next round selects the earliest retained produced Solana ancestor after the recorded anchor and derives a new challenge. The retained history must cover the anchor; if it has expired, the round fails closed instead of silently choosing a different boundary. Block producers can influence or withhold blocks, so this freshness mechanism is not a verifiable random function.

Mining is competitive. Other transactions, a day boundary, a missing target pin, RPC outages, or a changing round can make locally found work stale. The reward explorer reads a bounded recent page of finalized RPC evidence, not a complete history or an independent proof of RPC finality.

4. Settlement, burn and claims

After a day ends, a successful CLOSE transaction seals the day and burns the scheduled slice not credited to miners. If there were zero rewarded wins, the entire scheduled daily slice burns. The schedule does not burn tokens automatically at midnight. Credits are claimable only after the day is sealed. The 15 November claim amendment records a version-4 deadline exactly 30 days after the successful CLOSE transaction, so delayed maintenance cannot consume that claim window. The deadline is persisted once and cannot be extended by retries. Already-sealed or expired version-3 days retain their original deadline of 72 hours after scheduled day end; expired credits are not revived. The claim lookup and CLI report the deadline recorded for each day. A claim sends the credited test tokens to the miner’s associated token account. The claimant pays Devnet SOL transaction fees and any needed account rent.

After the deadline, the expiry transaction burns remaining unclaimed credits. An on-chain credit, a submitted claim, and a finalized token transfer are distinct states. Check the original transaction and claim page; do not sign a replacement while an outcome is uncertain.

5. Operations and trust

The CLI searches for proofs and signs and submits transactions using the miner’s local keypair. It saves the original submission in durable storage for recovery. The website provides instructions, finalized activity and credit lookup by public address. The on-chain program enforces the proof and claim rules for every client.

Day creation, opening rounds, closure, and expiry require on-chain lifecycle transactions. Availability depends on operators or other eligible transaction payers, Solana, and RPC providers; the schedule does not execute itself. The program is upgradeable: its upgrade authority can change deployed code. The reviewed client checks the pinned program linkage and executable hash when reading reward work, but an RPC observation is not an independent audit or a guarantee of future code or operations.

The first scheduled opening was October 30, 2026 at 4:00 PM EDT. For current status, verify the addresses above and read the reward explorer. For usage, limits, and recovery, see the mining guide.