DEV Community

StoneVast
StoneVast

Posted on

I withdrew $0.24 of mined crypto to an exchange — and it was the hardest part of the whole project

I withdrew $0.24 of mined crypto to an exchange — and it was the hardest part of the whole project

Mining was the easy part. Moving the coins out took a 3.5-year chain sync, a privacy-coin paradox, and one memo field that almost ate my money.

Context

I run a transparent mining workbench: one RTX 4070 Laptop, lolMiner, FishHash algorithm, mining IRON (Iron Fish) on HeroMiners pool. ~16 MH/s at ~49W. Daily net profit after electricity: about $0.075. Yes, seven and a half cents.

I publish every number publicly. Part 1 of this series covered the brutal economics. This post is about what happened when I tried to actually withdraw — the part most mining posts conveniently skip.

Step 1: The wallet that shows 0

My pool dashboard said it had paid me 1.8+ IRON. My Iron Fish CLI wallet said: balance 0.

Reason: Iron Fish is a privacy chain. Your wallet doesn't "query" your balance — it scans the chain and decrypts notes belonging to your keys. My node was 3.5 years of blocks behind. No sync, no notes, no balance.

Fix was boring but long: official chain snapshot + ironfish start --wallet --workers=-1, then wait for the wallet scan. Final result: 3.09185719 IRON visible.

Lesson: with privacy coins, "the explorer says you got paid" is not a thing. The explorer doesn't know who you are. Only your synced wallet knows.

Step 2: The memo that almost ate the deposit

Gate.io, like most exchanges, uses one shared IRON deposit address for all users, distinguishing accounts by a required memo field.

Iron Fish CLI transfers support memos, but the flow isn't obvious. If you send to an exchange deposit address without the memo, your coins arrive at the exchange — credited to nobody. Recovery means a support ticket and prayers.

I sent a 0.2 IRON test first. It confirmed on-chain (block 1846578) and showed up in the Gate app. Then I sent the remaining 3.0 IRON (block 1846594). Both arrived.

Test-first is the whole trick. The test cost me nothing but a few minutes; skipping it could have cost everything.

Step 3: Verify it yourself

Tx hashes — this is the point of the project, everything is checkable:

9281c0be78dfdb1d0196c832e4ea74afe80544d73b076aa1ecc6298ff335fb0a
c0092ac5633747806c0e222fac770ec81088add39d34557fb0db54a5240af23c
Enter fullscreen mode Exit fullscreen mode

The privacy-coin paradox, in practice: the explorer can confirm these transactions exist and their status, but hides sender, receiver and amounts. So "proof" on a privacy chain is a layered thing — pool dashboard ↔ on-chain tx existence ↔ exchange credit. Three independent ledgers agreeing is the strongest verification available.

What $0.24 proves

3.2 IRON ≈ $0.24. Not coffee money. But the full loop now exists and is documented:

GPU → pool → wallet (synced) → exchange (memo'd) → sellable USDT

Every step reproducible, every number public. Dashboard, daily snapshots, withdrawal log with both tx hashes: https://haolinsong32-lang.github.io/stonevast/withdrawals.html

Honest FAQ

Q: Is laptop mining profitable?
A: No. $0.075/day net. My long-term hardware goal (an RTX 6000 Pro) would take ~30 years at this rate. I do it because a fully-transparent micro-rig generates data, and data compounds.

Q: Why Iron Fish?
A: FishHash is GPU-friendly (memory-hard DAG, ~4.6GB, Blake3 core, ASIC-resistant by design), and the privacy model makes the "prove everything" constraint interesting.

Q: Would you recommend the Iron Fish CLI flow?
A: It works, but budget an evening for first sync + wallet scan. And write down the memo requirement before your first exchange deposit, not after.


Part 1 (the economics): I mine IRON on a laptop and built a base-13 cipher — an honest numbers report

Top comments (0)