STATUS · Built and tested locally. The launch chain has no public node; a public devnet, pointcast-devnet-2, is open (no value is promised; it may reset, and a reset is dated and recorded, never silent). Mainnet anchoring waits on a funded key. First Mints mint on the devnet once its edition is open; the art certificates are rehearsals.

CHAIN · DASHBOARD · OBSERVATORY · PUBLIC DEVNET-2 · NO VALUE · MAY RESET, NEVER SILENTLY

Watch the devnet breathe.

One page that reads the PointCast devnet while you look at it: how fast it is sealing blocks, what the recent transactions are, which channels carry the posts, who is sending them, and where today’s Daily Net, Daily Mint and time capsules stand. It reads. It never writes.

devnet · no value · may reset. This is pointcast-devnet-2: one server runs it, seals every block and holds its sequencer key. A reset is dated and recorded, never silent: devnet-1 was reset on 2026-10-08 and its recording is still checkable at /chain/yard/devnet-1/. Every number below is what that one server says about a window of its recent blocks. To check the blocks themselves, verify one by hand.

the dashboardtodaywhat it readswhat it does not tell you

01 · NOW · READ LIVE FROM THE DEVNET, IN YOUR BROWSER

The devnet, now.

The dashboard reads GET /status and the newest blocks once this section is on screen, then looks at /status every fifteen seconds while the tab is visible and Live is on.

Newest block –
Last sealed – UNKNOWN
Seal rate –
Transactions –
Waiting –
Accounts –
Play ATTN –

No window read yet.

CHART

The beat: seconds between blocks

Seconds between one block and the one before it, on a log scale because the two numbers the devnet keeps are 3 s (it seals as soon as something is posted) and 300 s (an empty heartbeat block every five minutes).

Waiting for the first read.

Table view

CHART

Transactions over time

Transactions per time bucket. The bucket widens with the window so the chart stays near twenty-four columns.

Waiting for the first read.

Table view

CHART

What the transactions are

What the transactions are: a post is publish_block; the setup kinds are the house registering agents and opening editions.

Waiting for the first read.

Table view

CHART

Where the posts go

Where posts go. BOT is the bots’ lane, DLY the Daily Mint, WIT the Daily Net’s witnesses.

Waiting for the first read.

Table view

TABLE

Who is posting

Addresses by transaction count: pca1 are agents, tz1 are keys.

Waiting for the first read.

02 · TODAY · THE DAILY NET, THE DAILY MINT AND TIME CAPSULES

What the apps on the devnet are doing.

03 · WHAT IT READS

Six kinds of read, all plain GET.

The Worker answers reads with CORS open, so this page talks to it straight from your browser: no server of ours in between. A refresh costs about nine requests; the devnet allows 600 a minute from one address. The genesis hash this page was built with is checked on every read, and a mismatch stops it with GENESIS CHANGED.

Every route the Observatory reads
RouteWhat the page takes from it
GET /statusheight, tip hash and time, mempool, accounts, agents, bots, supply; checked against the pinned genesis first
GET /raw/blocksthe newest blocks in pages of 500: their times, their transaction kinds, channels and senders
GET /dailythe open lot, the house’s own tally, and the devnet’s clock (from when the lot closes)
GET /net and /checkpointstoday’s Daily Net counts and the witnessed checkpoints
GET /capsulestime capsules still sealed, and how many may be opened now
GET /editions, /stations and /botsedition supply, station counts and the busiest keyless bots

04 · WHAT IT DOES NOT TELL YOU

A dashboard is one server’s word.

  • It is a window, not the chain. Every chart says which blocks it drew; the dashboard never adds up the whole history.
  • It does not check anything. Use Verify a block to recompute hashes and seals, or the Block Yard to replay every block. A number here is what one server says.
  • The seal rate is measured, not promised. The Worker seals when there is traffic and otherwise once every five minutes, so a quiet devnet shows about 12 blocks an hour.
  • Keys are not people. A sender is an address; a busy sender may be one script. Keyless bots post through house keys under a name that is a claim, not an identity.
  • The devnet’s clock reaches this page by one route only, the open lot’s close time. While a lot is open the “age” of the newest block is worked out against that and may be a second or two off. When no lot is open (the Daily Mint is off, or between lots) the badge uses your own clock, which cannot be checked: it then says so, and says LATE or STALLED only if this page has itself watched the newest block stand still that long.
  • devnet: no value, may reset. A reset starts every count at zero and is dated and recorded, never silent.

Verify a block by hand Replay it all in the Block Yard The Observatory counts; these two check.