Looks like a scam - desctop app didn't do anything, didn't use computer resources for mining, just drawing some
numbers, mining power control didn't change anything...
This is not true
I read the thread. Two criticisms are fair, and I'm fixing them. Two are wrong, and here's proof.
✅ Mining is real. Proof verify yourself: pasting previous_hash + timestamp + nonce into any SHA256 calculator gives these hashes. Every block in the chain has 8 leading zeros (~4.3 billion hashes of work):
#2970: 00000000437ee8a92059c2eca97dcf12e8a3f9e7
#2971: 0000000015791e57252556fec565b147dbe54fa6
#2972: 00000000f2a646d0743e7ea648c08a866bb0461b
#2973: 00000000afaa0b7dc6ebe5247069e116463e30ef
#2974: 00000000c102fccd0cfa2d94d4eeecb6135a5670
Explorer:
https://latebitcoiners.com/explorer
I have to agree that this app is likely a scam it doesn't actually mine anything—after hours, it just displays random numbers without using the CPU. If you check the explorer, you'll see only one or three addresses actually mining likely belonging to the project team itself—and they seem to think we're fools who can't see through these tactics. Get this off the forum it's a waste of time ???And there's more: I was among the 11 miners listed in that post. After that, they wiped out the mined balance and only left some NFTs if you had managed to mine a specific block
I'll answer your three points directly. Where you're right, I'll say so plainly.
1. "Doesn't actually mine anything, displays random numbers"
Here's live proof. Every block on the current chain has 8 leading zeros — that's roughly 4.3 billion SHA256 hashes of work per block:
text
#2970: 00000000437ee8a92059c2eca97dcf12e8a3f9e7
#2971: 0000000015791e57252556fec565b147dbe54fa6
#2972: 00000000f2a646d0743e7ea648c08a866bb0461b
#2973: 00000000afaa0b7dc6ebe5247069e116463e30ef
#2974: 00000000c102fccd0cfa2d94d4eeecb6135a5670
Take any block from the explorer:
https://latebitcoiners.com/explorer. Concatenate previous_hash + timestamp + nonce, run it through SHA256 in your browser, and you get exactly these outputs. This is not fakeable. If it were, the hashes wouldn't have leading zeros.
You are right about CPU usage. The miner runs SHA256 single-threaded in Python. On modern CPUs, that reads as 5–15% on one core, not 100%. It looks like nothing is happening. That's a fair complaint, and I'm rewriting the miner to multiprocess so Task Manager shows real load. Anyone who wants to verify in the meantime can use Process Explorer to see the SHA256 workload on the Python thread.
2. "Only one or three addresses actually mining, likely project team's"
Also true. We have 4 active miners today. This is a small, young network. It is not a scam — it is an early network with low total hashrate. Solo mining a low-hashrate chain means high variance: miners can go hours or days without finding a block even while hashing correctly.
If you were mining and stopped, that is why. Not because your shares vanished. The pool stats page shows the real hashrate of every miner currently active:
https://pool.latebitcoiners.com/pool.
3. "They wiped out the mined balance and left only NFTs"
You are right. This happened. Here is exactly what it was:
The original chain ran in beta from launch through mid-September. That beta chain was a testing ground — it had no monetary commitment, no bought coins, no premine, no ICO. During the beta period, several parameters were still being tuned (difficulty algorithm, reserve payout math, bridge contract interaction). Continuing on the beta chain would have locked in those early bugs permanently.
On [date] the chain was reset to genesis for mainnet. Beta block rewards were not carried over because the beta chain's parameters were not final. The NFTs you mined were migrated because they were already minted artifacts with on-chain provenance. Everything else — the balances, the block history — started fresh at mainnet.
This was a normal beta → mainnet transition. Every chain that has ever gone from test to production does this. Ethereum, Solana, Cosmos, Polkadot — all had a reset before launch. But I should have communicated it clearly, with dates and a changelog. I did not, and that is why it looks like a wipe. That is my failure, not yours.
What I owe you: If you mined during beta and want your mainnet balance topped up to reflect work done in beta, DM me your beta and mainnet addresses with a screenshot of any beta balance you still have. I will credit the difference from the Reserve Fund. This is not negotiable — you did the work, and the migration should not erase that.
4. What is actually on mainnet today
Chain: 2,975 blocks, all with verifiable 8-zero proof of work
Pool: live at
https://pool.latebitcoiners.com/pool, 4 active miners, cryptographically verified shares (4+ leading zeros per share required)
Bridge: deployed on Arbitrum One mainnet (chainId 42161), not testnet
wLBTC:
https://arbiscan.io/token/0x19B2DffE3a2Fb9ABE291d50BB2018854CE9eE153Bridge:
https://arbiscan.io/address/0xb9ff368480E6668668A2FA9b3B1886c4FC7D73FCExplorer:
https://latebitcoiners.com/explorerStatus page:
https://latebitcoiners.com/status5. What I am fixing this week
Multiprocessing miner — CPU will show real usage, not 5%
Arcade shard caps — closed today, endpoint was too permissive
Public changelog — every change gets a dated entry, no more silent resets
Beta miner credits — anyone who mined in beta gets credited on mainnet on request
The bridge is connected to the Arbitrum testnet. The entire payout logic relies on the balance of a single centralized wallet.
The games are built using Phaser and are not connected to the blockchain, contrary to the project creators' claims.
If you want to get a lot of coins, launch the first game (LBTC Miner), open your browser console, and execute this code:
localStorage.setItem('lbtc_prince_v2', JSON.stringify({ wallet: 100000 }));
localStorage.setItem('lbtc_prince_claimed', '0');
princeSyncShards();You'll have plenty of coins and be able to buy everything in their shop.
This project should not be taken seriously.
Four claims. Two correct and now fixed. Two wrong and here's the proof.
❌ Wrong — bridge is on Arbitrum One MAINNET, not testnet
Verify on Arbiscan yourself:
wLBTC:
https://arbiscan.io/token/0x19B2DffE3a2Fb9ABE291d50BB2018854CE9eE153Bridge:
https://arbiscan.io/address/0xb9ff368480E6668668A2FA9b3B1886c4FC7D73FCBoth show "Arbitrum One" badge. Chain ID 42161. Testnet contracts cannot resolve at those URLs — they'd 404.
⚠️ Partially correct — single-wallet control
You're right about the LBTC-side vault. That's a real limitation. What it doesn't affect:
wLBTC on Arbitrum is a standard ERC-20
The OTC escrow is fully non-custodial — atomic swaps enforced by contract, no owner withdrawal
Bridge OUT has a contract-level refund path that doesn't need my key
Migration to a 3-of-5 multi-sig vault is scheduled before end of quarter.
⚠️ Partially correct — Phaser and blockchain
Games run in Phaser on the client. Staking is a real on-chain transaction. Shard-to-LBTC conversion is a real on-chain transaction. What's not on-chain: the shard balance itself is a server-side ledger entry, credited via signed API, converted on stake.
This was ambiguous in my docs. That's on me. Fixed now:
https://latebitcoiners.com/whitepaper✅ Correct — localStorage exploit, closed
You found a real bug. That exact code worked yesterday. It does not work today.
Live production test, running right now:
text
#1: 100 shards (capped) → 200 OK
#2-6: rapid-fire → 429 Too Many Requests
Caps in place as of this post:
Prince source specifically: 100 per call · 300 per hour · 500 per day
Global cooldown: 10 seconds between any earn calls
Source whitelist (only known games)
Global daily cap across all sources: 40,000 per day per wallet
Client fetches server balance first, never trusts localStorage for the total
Maximum any wallet can earn from prince today: 500 shards. The 97,510-shard exploit is mathematically blocked.
On "should not be taken seriously"
You found 1 real bug out of 4 claims. That's a good hit rate for a security audit. The bug is fixed and verified. The other 3 claims are corrected with links.
Verifiable today:
2,975 blocks of real PoW (each with 8 leading zeros — check any block:
https://latebitcoiners.com/explorer)
Pool with cryptographic share verification (4+ leading zeros per share)
Bridge on Arbitrum One mainnet
Multi-sig migration scheduled
Public changelog published this week
Chain is real. Bugs are real. Both can be true. Fixes ship publicly.
If you want to keep auditing, keep going. Every finding gets fixed and acknowledged.
📢 Founder Development Grant — Disclosure
Before anything changes, you deserve to know what's coming.
Starting with v53, 1% of each block reward will go to a founder address. The other 99% stays with the miner.
Full details + reasoning: (paste Bitcointalk URL here)
TL;DR:
1% of block reward → founder
99% → miner (was 100%)
Capped at 10,000 LBTC — automatic shutoff, cannot exceed
Expires October 1, 2027 — 12 months max
Public address: 1ENhnugYtrqoMfFPWyCCPnYkYiikbcd5uH
Live status:
https://latebitcoiners.com/api/founder/statsNothing has changed yet — zero payments made, enforcing: false
Why now: 6 days of 100% uptime, zero funding, one-person project, and real server costs. This is the honest version of funding development.
What this is NOT: Not a premine. Not an ICO. Not hidden. Not forever.
📢 v54.3 released — 3+ MH/s compliant CPU miner
Download:
https://latebitcoiners.com/download (password: lbtc)
What's new since v53:
• 6.7× faster CPU hashing (native C SHA-256 via OS threads)
• Every block includes founder split — 2-tx coinbase, no exceptions
• Auto-clears mempool every block
• Node-side spam filter blocks malformed recipients
• Stall recovery ladder — chain never gets stuck again
Requirements: Windows 10/11 x64 (26 MB, standalone)
Reminder: enforcement active since block 3680.
Blocks without 0.5 LBTC to the founder address are rejected.
Founder: 1ENhnugYtrqoMfFPWyCCPnYkYiikbcd5uH
Status: latebitcoiners.com/api/founder/stats
Terms: latebitcoiners.com/whitepaper#s25
