chain tip
not yet
feed not loaded
The Fork · block 1,976,112
Skydoge hard fork at block 1,976,112 · treasury anchor at block 1,980,144 · the story is written in advance, the facts are written by the chain. Every slot below says not yet until the block exists.
A memorial that fills itself in. Nothing on this page is pre-filled: the fork block, its hash, the pool that found it, the commitment share of the first day and the anchor block come from the chain feed, or they say not yet.
Skydoge hard fork · block
1,976,112
not yetthe chain decides · the slots below fill in from the fork watch
1,976,109
old rules
old rules
1,976,110
old rules
old rules
1,976,111
old rules
old rules
FORK
50 KB
the fork block
50 KB1,976,113
50 KB cap
50 KB cap
50 KB1,976,114
50 KB cap
50 KB cap
three blocks under the old rules · the fork block · every block after it is at most 50,000 bytes and carries one sidechain-state commitment · much fork, very law, wow
t-minus to block 1,976,112
--d--:--:--.---
-- blocks to the fork
estimate from the chain feed · waiting for /chain.json
the chain has passed block 1,976,112
the fork is law
fork block hash: not yet confirmed by the fork watch
every block from here carries the sidechain-state commitment and is at most 50,000 bytes.
// the chain right now
blocks to the fork
not yet
fork height 1,976,112 (rule)
blocks to the anchor
not yet
anchor height 1,980,144 (rule)
source: /chain.json (this site's mirror of the block explorer, once a minute) and /fork.json (the fork watch) · fork watch: not loaded
// the road · from here to the anchor
start
fork 1,976,112
+1,440 census
anchor 1,980,144
tip: not yet
fork eta
not yet
needs the chain feed
anchor eta
not yet
needs the chain feed
block rate
not yet
measured by the mirror
the rail runs from the point where the block-rate measurement begins to the anchor; the dot is the chain tip. the eta is tip time + blocks remaining × measured spacing: an estimate that moves with the hashrate. the height is the rule, the date is not.
// readiness · the last 1,440 blocks
Miners: if you mine on a pool that has not upgraded, your blocks are invalid from block 1,976,112. From the fork block every Skydoge node on 0.45.3b rejects a block that is over 50,000 bytes or whose coinbase lacks the sidechain-state commitment. A pool still on the old software keeps finding blocks, but they are not Skydoge blocks: no upgraded node, wallet, explorer or exchange accepts them, and the coins it credits you for them do not exist on the chain. Read the table below. A pool at 0 % says ready has not shown the upgrade; after the fork, a pool at 0 % proves ready is mining a dead chain. Point your miner at a pool that tags
/SD0.45.3/ or has confirmed Skydoge 0.45.3b, or mine on your own upgraded node. Download & verify the release.says ready · coinbases tagged /SD0.45.3/
not yet
a pool that writes /SD0.45.3/ into its coinbase says it builds from a 0.45.3b template. optional; it changes nothing in consensus.
proves ready · coinbases with the commitment
not yet
the sidechain-state commitment the new rules require. node templates only include it from block 1,976,112, so this reads 0 % until the fork; from then on a block without it is not a Skydoge block.
by pool · share of the window and what each coinbase carries
not yet · the fork watch has not loaded
the window is the fork watch’s census window (not yet). the share of blocks is the only hashrate measure this page has; a pool with few blocks is a small pool or an unlucky one.
// the lens · the last blocks against the new rules
not yet · the chain mirror has not loaded
the last blocks the mirror holds, each measured against the 50,000-byte cap the fork brings. before the fork a block over the cap is legal and marked; from the fork block it cannot exist. the gap is seconds since the previous block in the list.
// the slots
The fork block
not yetheight
not yet
hash
not yet
time
not yet
found by
not yet
commitment
not yet
the first block under the new rules: at most 50,000 bytes, one sidechain-state commitment in its coinbase. the pool tag is read from the coinbase; a pool without a tag shows as untagged.
The first 1,440 blocks
not yetwindow
not yet
with commitment
not yet
share
not yet
the honest census of the first day after the fork: how many blocks carried the commitment the new rules require. the window opens at the fork block; until then there is nothing to count.
The anchor block
not yetheight
not yet
hash
not yet
time
not yet
found by
not yet
monument
not yet
block 1,980,144 = fork + 4,032. from here every sidechain treasury pointer is anchored to the coin set: a block that spends a pointer coin without moving the pointer is refused. a pointer broken before the anchor is logged and its slot freezes; the chain does not halt.
The Thunder monument
not yetslot
2 · Thunder · the one active sidechain on mainnet
treasury
1.00 coin, left there on purpose after the Thunder Rescue
anchored at
not yet
the monument: one coin that stays in slot 2 so the first drivechain on Skydoge is never forgotten. from the anchor block its pointer is under the anchor rule. whether the coin is still in place is a question for a node (listactivesidechains), not for this page.
// verify it yourself · the fork
On your node
skydoge-cli getblockhash 1976112not yet · the hash appears here when the chain has the blockskydoge-cli getblockhash 1980144not yet · the hash appears here when the chain has the blockskydoge-cli getblock <hash>size at most 50000 from the fork block on; one coinbase with the sidechain-state commitmentskydoge-cli getscdbstatethe sidechain-state hash your node commits to; it must match what the other upgraded nodes reportskydoge-cli getblockchaininfonot yet · the mirror’s tip height appears here; yours should be within a block or two
a node still on old software shows no error at the fork: it keeps following a chain the rest of the network rejects. the hashes above come from the chain feed, so a mismatch on your side is the thing to notice.
Download & verify the release
- mainchain-0.45.3-x86_64-linux-gnu.tar.gzlinux
- mainchain-0.45.3-win64.zipwindows
- mainchain-0.45.3-osx64.tar.gzmacos
- SHA256SUMSchecksums
- SHA256SUMS.ascsignature
- skydoge-release-key.ascrelease key
- POOL-NOTICE.txt.ascsigned pool notice
- source · tag v0.45.3bgithub
release key fingerprint
915D 0BAA 47E6 056B 5E02 FDAE 2DE1 360A 2AE8 EC88gpg --import skydoge-release-key.ascgpg --verify SHA256SUMS.asc SHA256SUMSsha256sum --ignore-missing -c SHA256SUMS
the same fingerprint is posted on the homepage. verify the signature and the checksum before you run anything.
// the monument · first full drivechain round trip on mainnet
The monument
sidechain slot 2, Thunder: the first mainnet C++ implementation to complete a full drivechain round trip — deposit and withdrawal — with the withdrawals voted by miners.
activated
block 545,937 · 2024-01-07
deposits
9 deposits, blocks 546,878 to 562,414 (2024-01), 812.77 coins in all
stranded
block 556,374: a deposit did not chain from the 780.00 treasury output, and 780 coins had nothing pointing at them for 1,324,500 blocks
left
1.00 coin, the treasury pointer, and 0.01 left behind on purpose (an empty treasury would leave a zero-value pointer)
facts from the monument record v1. unlike the slots above, these numbers are history, not a live feed: every one of them can be re-derived from a node with the commands on the right.
The round trip, block by block
- withdrawal 1: bundle
cfabd44b…committed in block 1,874,194; the 131st miner upvote in block 1,874,443; paid in block 1,874,444 — 32.75 out, 0.01 stays. - re-attach: block 1,874,459 — one hand-built transaction, placed by a cooperating miner, puts the 780 plus a 1.00 margin back under the treasury: 781.00.
- withdrawal 2: bundle
b7d731fb…committed in block 1,874,471; the 131st upvote and the payout in block 1,874,625 — 779.9999 out, 1.00 stays. - 812.7499 of 812.77 recovered; completed 2026-08-19 UTC. the whole story
Verify it yourself
skydoge-cli getblockhash 54593700000000003eea5c3da059fa6b4d3485d7f7dd8c8a88bd50412e4c23936aac11skydoge-cli listactivesidechainstitle Thunder, description Scalingskydoge-cli listspentwithdrawalstwo slot-2 bundles: cfabd44b… and b7d731fb…skydoge-cli getrawtransaction 99b471e7561421105f6afd92c20dc17370581b1a08a47ec0aac020a45b3e26bf true 000000000116d6302fc194566fc906e2cb519170d3ddffe0365223db1d92d0d9withdrawal 1: 32.75 out, 0.01 to the treasuryskydoge-cli getrawtransaction 740af9a940290f22c048816c369a24647e654b1e1cf70c496b928ef3c6035127 true 0000000000de5e1b9bff1c9f0a27ccd2d6d9decbaefa88ed4b401ed7f00fedf9re-attach: output 0 = 781.00 to the treasuryskydoge-cli getrawtransaction bfd5ae4118b7c6db312fedca677844fd0d3056120e40d55439f67587b08ad626 true 00000000016c3aa330a85b15ef3937c7da3522409eda50ee47bdd9061863f546withdrawal 2: 779.9999 out, 1.00 to the treasuryskydoge-cli listsidechainctip 2bfd5ae41… output 3, 1.00skydoge-cli gettxout bfd5ae4118b7c6db312fedca677844fd0d3056120e40d55439f67587b08ad626 3value 1.00000000 while the coin is in place; nothing if it is spentskydoge-cli listdrivechaincoins 22 coins, 1.01, of which 0.01 stranded
or on the explorer. the full list, one command per number, is in the record.
the signed record: not yet published · the record and its signature will be linked here
slot 2 · Thunder
812.7499of 812.77 coins home
1,324,500blocks stranded
131 of 131miner upvotes, twice
1.00coin stays as the monument
two BIP300 withdrawals, voted by miners; completed 2026-08-19 UTC.
// the story, written before the block
The castle
a castle in the sky, held up by hashrate: no king, no landlord. the walls are blocks, the pillars are GPUs, the drawbridge is a BIP300 peg. the gatehouse is the drivechain itself — hashrate escrows (BIP300) and blind merged mining (BIP301) inside the node, in C++.
until block 1,976,112 the gatehouse is masonry. from the fork block it is law: every block must carry the gate's commitment, or it is not a Skydoge block.
The SHAndwich
skydoge always liked SHAndwiches. its first proof of work was SHAndwich — SHA-256, then SHA-512, then SHA-256 again, a hash between two slices — before skydogehash, the chained multi-hash GPU proof of work it mines with today.
a hard fork is the same gesture one layer up: the old rules, a new slice of rules, and the chain carries on as one loaf. the proof of work does not change at this fork.
Why the fork
honest and short: the drivechain rules in the node had to change, and consensus rules change only one way — every node and pool switches at one fixed height. from block 1,976,112 every block must:
- be at most 50,000 bytes (a transaction over 40,000 bytes is no longer relayed or mined);
- carry exactly one sidechain-state commitment in its coinbase, computed by the node;
- respect the timewarp guard on timestamps;
- use the production sidechain windows (a withdrawal needs 129,600 blocks of miner votes);
- chain every deposit from the recorded treasury pointer; a zero-value escrow output is invalid.
every node and pool must run skydoge 0.45.3b (signed binaries) before the height. a block built by an old miner is rejected from the fork height on; a pool-built coinbase without the commitment is invalid. the date is an estimate; the height is the rule.
what every node, wallet, miner, pool and exchange must do before block 1,976,112 →
The anchor
4,032 blocks after the fork, at 1,980,144, the second half of the change arms: every sidechain treasury pointer is anchored to the coin set, and a block that spends a pointer coin without moving the pointer is refused.
this page keeps both heights as empty slots and lets the chain write them. when a slot is filled, the block exists on the chain — verify it on the explorer yourself.