← SKYDOGE.NET

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.

// the chain right now

chain tip
not yet
feed not loaded
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 slots

The fork block
not yet
height
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 yet
window
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 yet
height
not yet
hash
not yet
time
not yet
found by
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 is refused. a pointer broken before the anchor is logged and its slot freezes; the chain does not halt.

The Thunder monument
not yet
slot
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.

// 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 sandwiches. 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 runs skydoge 0.45.3 (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.

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 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.