Network parameters
The parameters below identify Ark-0. The genesis block is shared by every signet; the challenge and the message start derived from it are what set this chain apart.
- Signet challenge
5121026fc5d8e79a9fbc8bc3dea07d82641d16717ce0b000c13c512d8e8c1788c6e5da51ae- Message start (network magic)
40e8e404- Genesis block
- 00000008819873e925422c1ff0f99f7cc9bbb232af63a077a480a3633bee1ef6
- P2MR rules active from height
- 1
- ML-DSA-44 block signature (M2) required from height
- 20000
- Tripwired leaves (version 0xe0, M3) run from height
- 30000
- SLH1 leaves (OP_CHECKSLHDSA128S, M4-S) checked from height
- 32000
- Rescue lane (M4-R) open from height
- 51000
- Difficulty adjustment
- 600 s per block up to the adjustment at 6048; 90 s per block from the adjustment at 8064 on
- Address prefix
tb1z- Node version
/Satoshi:31.1.0/
Drill tripwire (M3)
M3 is an experimental rule of this test network, not part of BIP-360 or BIP-361. From height 30000, nodes run P2MR leaves of version 0xe0, tripwired leaves, as tapscript. Once either of two designated tripwire outputs is no longer in place, from the next block on, elliptic-curve signature checks in these leaves fail, while ML-DSA-44 checks go on as before; leaves of version 0xc0 are not affected. It is an experimental implementation following the P2XX-T idea of sipa's mail of 2026-06-25: what is constrained is one experimental leaf version, and the tripwires are two designated outputs. It is a drill on a test network, and does not mean that any elliptic-curve key has been broken.
- Elliptic-curve checks in leaves of version 0xe0, from the next block
- Off: a tripwire is not in place
- NUMS tripwire
- In place: unspent, and created below the activation height
4319a38c…7c1bc3a0:1
x-only key50929b74c1a04954b78b4b6035e97a5e078a5a0f28ec96d547bfee9ace803ac0
Locked to the BIP-341 NUMS point, whose private key nobody knows. - Drill tripwire
- Not in place · spent by 2885e18bf4e9…cd2708b389c9 · Block 36897
8991bb83…b1d42495:0
x-only key2f605bb3d127c17ff8e88e214587876b0c7623dbad79f8a1115fa172bda0315f
Locked to the operator's drill key, to be spent at an announced time.
As the node reports it at height 39635.
OP_CHECKSLHDSA128S (M4-S)
From height 32000, byte 0xf1 in an executed P2MR leaf (leaf version 0xc0, or 0xe0) is OP_CHECKSLHDSA128S, which checks an SLH-DSA-SHA2-128s signature (FIPS 205). Nodes relay one script with it, SLH1: a 32-byte public key followed by OP_CHECKSLHDSA128S. Below that height the byte is OP_SUCCESS241, and a leaf with it succeeds unchecked. OP_CHECKSLHDSA128S is an experimental opcode of this test network, not part of BIP-360.
Rescue lane (M4-R)
From height 51000, in an executed P2MR leaf of version 0xe0 at depth one or more, OP_CHECKSIG, OP_CHECKSIGVERIFY and OP_CHECKSIGADD with a 32-byte public key take a rescue token in place of a Schnorr signature: the input's annex then carries a 130,218-byte proof that the spender knows the seed the key was derived from, and nodes check that proof instead. Nodes relay one script for it, R1: a 32-byte public key followed by OP_CHECKSIG. A rescue token discloses the key's Schnorr private key. Below that height a token is only an invalid signature. Mempools take rescue spends only while tripwires disable elliptic-curve checks for the next block. The rescue lane is an experimental rule of this test network.
- Rescue lane, from the next block
- Not open
- Rescue spends in the node's mempool
- Not accepted
To follow this chain with a node of your own, see the joining guide.