MISAKAScan Misaka testnet-12 connecting…
testnet-12 is live 2026-09-25 launch · run 587cab2b0 before DAA 1,300 (≈ 2026-09-28 05:25 JST) · when a payment is final — expand
This explorer shows testnet-12 (R-core+, ADR-0152 v3.1), launched 2026-09-25 about 23:15 JST from release 0e8ec984e; since 2026-09-27 19:37 JST the fleet runs the second flag day's release 587cab2b0. A node on this network prints params fingerprint 24e1aec3e9a102fa40d559cd28005ad5944c32caa485d685bed65c52e4c056ff and fence schedule 750, 1000, 1300 (schedule id d263d7f2…): the second post-launch flag day: its two fences activate at DAA 1,300 (the 13 of DAA 750 are in force since 2026-09-27 07:29 JST). A node on c3dbaee3c (dbbc9104…) keeps peering below DAA 1,300 and is refused from it; if it crosses DAA 1,300 on that build, move its datadir aside and resync with 587cab2b0. Genesis a27f8f44fe4d91a5…; the eight genesis bonds are outputs 0–7 of premine txid 5e0d5f1b….

Join. Build 587cab2b0 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 were fixed by the activation fences at DAA 750 (release c3dbaee3c).
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).
Loading…