This explorer shows testnet-12 (R-core+, ADR-0152 v3.1), launched 2026-09-25 about 23:15 JST from release 0e8ec984e (now main). A node on this network prints params fingerprint b8564b888e55bb5f797e708a3f65e7cd122065123a3ab09cbeb8d10c98715d8f and fence schedule 1000 (schedule id 93da24cc…). Genesis a27f8f44fe4d91a5…; the eight genesis bonds are outputs 0–7 of premine txid 5e0d5f1b….

Join. Build main (or 0e8ec984e) and run kaspad --testnet --netsuffix=12; the CLI is misaka --network testnet-12 (its default). Peers come from the DNS seeders seeder1–4.misakascan.com; the P2P port is 26311. A datadir from an earlier testnet-12 genesis is refused at startup — move it aside. A main build no longer joins testnet-11 (the previous network; build 1f98d3bf4 for it). The faucet has no testnet-12 funding yet. Producing or verifying: docs/testnet12-join-mining.md.

Known issues — details in the launch note (in Japanese). The two CRITICAL ones are fixed by activation fences after launch: rebuild when the fence release is announced.

• CRITICAL — heartbeat transparency: a heartbeat miner with no bond can pull published attempts into a private chain and reorg within the merge depth (about 30 blue, about 10 minutes) — a double spend.
• CRITICAL — panel-seed grinding: the panel seed is the anchor block's identity, so an anchor producer can redraw its panel before publishing; being fenced as soon as possible (the execution-commitment seed plus, as a stopgap, anchors only from the eight genesis bonds). Grinding needs panel seats, and the operator holds back faucet funding and large transfers until the fence is live; per-operator panel skew is monitored.
• DNS finality is in Bootstrap: validators are funded after launch; until then the DNS reorg gate does not act, and the EVM bridge's deposit claims wait for it.
• Valid locks after Final may fill a seat's 500‰ room (predicted): at λ 5 seats may stop binding within 1–3 days. Monitored; the remedy is being designed.
• Unlicensed claims (V04): a claim can stay unlicensed although every seat filed Valid. Cause found (collectors license claims in claim-id order, so large ids wait); fixed by a node update due well before the first receipt deadline.
• 8k readiness: a stalled 8k seat can drop the class to Held, which voids its unbound claims. Partly fixed in this release; the rest follows by fence and node update.
• Scheduled fixes: registry resilience, the bridge audit (BR-1–BR-7), position fixes.

When is a payment final? Never count blocks, blue-score depth, DAA or heartbeats — heartbeats can inflate all of them, and a stretch with only heartbeats confirms nothing. Small amounts: on your node's selected chain, a blue attempt block at least 30 blue score above the block carrying the transaction, with attempts still following. Large amounts: finality depth 600 blue (about 4 hours), or a Final PALW anchor (getPalwSettlement / misaka palw settlement).