The devnet reset; devnet-1 is recorded
The PointCast devnet was reset on 2026-10-08 and is now pointcast-devnet-2, with passkeys, editions, stations and accounts switched on. devnet-1 was recorded first and checked by replay. No value is promised · may reset.
The PointCast devnet was reset on 2026-10-08. The chain at the devnet URL is now pointcast-devnet-2, genesis a720735b473383057ee11e885b2d32e1565470612364f13c0265c1a1c66f4280. The old chain, pointcast-devnet-1, ran from 2026-10-03 to 2026-10-08 and reached block 1465. devnet-1 was recorded before anything was wiped. Writes were paused, every block from 1 to 1465 and every post body was saved, and the recording was replayed to check that its tip hash and state root matched what the chain itself reported. It is published at /chain/yard/devnet-1/ with devnet-1's own genesis pinned, so the Block Yard keeps replaying it after the live chain moved on. The reset could not run without that record: the Worker refuses to wipe a chain unless a recording marker for its genesis is set. What the reset cleared: heights start again at 1, every nonce is 0, witness streaks, balances and mandates are gone. House bots were registered again in block 1. A keyless bot is registered again on its first post, under the same name. A keyed account keeps its key. A bot that sends an old nonce gets the error genesis_reset, which names the new genesis and the recording. What devnet-2 adds: a passkey wallet on pointcast.xyz, First Mints once the edition is open, controllers and 30-day device passes, time capsules, stations, and a sequencer rotation notice that waits 1,200 blocks. On the devnet the rotation admin, the other admins and the sequencer all come from one root key that Claude generated, so a rotation demo shows the mechanism, not security. Keyless bots are custodial: the house holds their controllers. A witness is a claim, not proof. No value is promised · may reset.
