diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 2f0805968..47d816738 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -11,9 +11,10 @@ # Where it runs: `pow` and `sims` go to the box's runner (igneum-build-1, rustc pinned, sccache read-only, 48 jobs) # when the repository variable IGNEUM_CI_RUNNER is `box`, else to ubuntu-latest (docs/plans/ci-self-hosted.md; GitHub # has no fallback in runs-on, the variable is the switch). The `site` job stays on GitHub's machines. The `red` job -# runs on the box after any failed master or release-* run and records the failure for the watcher -# (tools/ci/red-watch.mjs; infra/build-server/ci-red): one line per run to the hidden updates channel and to -# /srv/ci-red/red.jsonl, so nobody opens the Actions page to learn master is red. +# runs on the box after any failed run on ANY branch and records the failure for the watcher +# (tools/ci/red-watch.mjs; infra/build-server/ci-red): one line per run, naming the branch, the commit, the red check +# and the pushing author, to the hidden updates channel and to /srv/ci-red/red.jsonl, so nobody opens the Actions page +# to learn a branch is red (master and release-* only until 7 October 2026, when eight red runs on ca3-v4-node went unseen). # # What does not run, on purpose: the node fork (vendor/igneum-node*, a rusty-kaspa fork of about 500 crates with # rocksdb, blst and the execution layer) is gitignored here and too big for the free runners today (a cold build is @@ -77,14 +78,14 @@ jobs: run: node tools/ci/public-api-check.mjs https://igneum.network red: - # Runs only when a master or release-* run has a failed job, on the box's own runner (not a GitHub-hosted machine: + # Runs when a run on any branch has a failed job, on the box's own runner (not a GitHub-hosted machine: # the billing block of 6 October 2026, 18:37Z to 20:10Z, failed every hosted job at start and nobody was told). # tools/ci/red-watch.mjs record appends ONE line for this run to /srv/ci-red/red.jsonl (idempotent per run attempt); # the box's igneum-ci-red.timer posts each new line once to the hidden updates channel. Never blocks a release: # it reads the run, writes one line, and ends. - name: red watcher (master and release-* only; one line per failed run to the updates channel and the box file) + name: red watcher (every branch; one line per failed run, with the branch, commit, red check and pushing author, to the updates channel and the box file) needs: [pow, sims, site] - if: ${{ failure() && (github.ref == 'refs/heads/master' || startsWith(github.ref, 'refs/heads/release-')) }} + if: ${{ failure() }} runs-on: [self-hosted, linux, x64, igneum-build-1] timeout-minutes: 5 permissions: @@ -94,8 +95,9 @@ jobs: - uses: actions/checkout@v4 with: sparse-checkout: tools/ci - - name: record this run (one line, the failed jobs and their first failed step, from the run's own API) + - name: record this run (one line, the branch, the commit, the failed jobs and their first failed step from the run's own API, the pushing author) env: GITHUB_TOKEN: ${{ github.token }} RED_WATCH_TITLE: ${{ github.event.head_commit.message }} + RED_WATCH_AUTHOR: ${{ github.event.head_commit.author.name }} run: node tools/ci/red-watch.mjs record --file /srv/ci-red/red.jsonl diff --git a/docs/bench-log.md b/docs/bench-log.md index af812f224..5d5220b34 100644 --- a/docs/bench-log.md +++ b/docs/bench-log.md @@ -2521,6 +2521,25 @@ same once; a pool user nothing; a fleet operator gets a node that keeps its only every peer (13,354 lines of work it did not need in seven minutes). Owed: the fleet agent's synced-node reading; a receiver-side limit on certificates per index per minute as a second belt once the seed is fixed; the formatter's reflow of `finality.rs` (taken out of the commit). +## 6 October 2026, Counter ASIC 3.0: the class v4 rehearsal + +A fleet of real GPU boxes ran a fleet-only chain from the devnet's genesis state and crossed a class v4 activation by miner signal, in the shape the live devnet will see. Numbers only; the per-box record is `docs/plans/counter-asic-3-gate/class-v4-20261006-rehearsal-PASS.json`. + +| Number | Value | +|---|---| +| Nodes on the chain | 16 (15 mining, 1 seed) plus 37 more miners joining after the flip; 1 box left on the old binary as the stale case | +| Object | 17 fields, epochs of 600 DAA, the signal window 600 DAA, the threshold 9,500 bps, the floor at DAA 2,400; one consensus digest on every node | +| First block | 18:41:10 UTC | +| The flip | DAA 1,202, 19:00:5x UTC, by miner signal at epoch 2: 10,000 bps over the window, 599 of 599 blue blocks, the identical line on all 52 signalling nodes | +| Program ids | one id per epoch on every box for epochs 2, 3 and 4, each equal to the CPU verifier's class v4 id for that seed and era and different from the class v3 id of the same seed; the pre-flip epoch's id is a class v3 id | +| Blocks rejected for proof of work | 0 on every node over the whole run; every miner's CPU re-check mismatched 0 | +| The old-binary box | refused at every connect by consensus digest (11 refusals, 22 mismatch lines), never a peer; given the full object it exits at parse | +| The floor | crossed at DAA 2,400 with v4 already in force; the chain mined through it at about 1.6 blocks/s; one chain, no fork at the 19:34:54 UTC sweep (heights 2,502 to 2,509, blue 2,432 to 2,440) | +| Verifier against the GPU on the first v4 pack | 1,024 of 1,024 nonces at target ff..ff found by the GPU worker and re-derived by the CPU verifier, one digest on both sides | +| The stall | 90 s at the flip and then a stop: the shipped worker of the previous release refuses a generator-4 pack by design; the fleet resumed on the release tree's generator-4 worker 15 minutes later | + +What it means per tier: a class change on this chain is decided by the miners' own signal and lands at an epoch boundary with no human release; an old node cannot join the new chain and an old worker cannot mine the new class, so a home miner, a rig and a pool update the node and the worker together before the signal window closes, which the one-click app does in one update; a chip built for the old class mines nothing from the flip. The live cut carries the one lesson: the new object is published only once every node and every worker runs the release that reads it. + ## 6 October 2026, 16:01Z: Ember run 6 on PC 1 (ember-tune-pc1-6, 0.3.13 + kit-6 = 564bdea, elevated, one click) The helper registered inside the run but on the scratch copy (fixed: task_exe, the `reregister` verb; see the plan's diff --git a/docs/community/discord-hooks.md b/docs/community/discord-hooks.md index 2c0bbb14b..bb2d3b9c1 100644 --- a/docs/community/discord-hooks.md +++ b/docs/community/discord-hooks.md @@ -14,6 +14,7 @@ eight fields, UK time in the footer with UTC in brackets, never a mention, never | Weekly numbers | #numbers | Monday 09:00 | the reddit kit's template (docs/community/reddit/posts/02-weekly-numbers-template.md) as six fields with the last-week column, a link to the ledger | | Release | #announcements | on a publish, by the shipper | version, three download links with full sha256, node commit, consensus digest, up to five "what changed" lines read from the release plan | | Incident open / resolve | #incidents | by hand, or by the watcher | UTC time, what happened, who is affected per tier, what is being done; then cause, the rule or fix, duration | +| Network feed | #network-feed | every hour, when `DISCORD_WEBHOOK_FEED` is set | height and blocks/s over the hour, hash rate and difficulty, keys active and voters, the last lock; the daily hash-origin field once per report date from `/api/live state.hash_origin`; milestones once each (every 100,000 blocks, 10,000 locks, 10,000 paid shards; the first crossing of a vote-key count and of a hash-rate step). Added 7 October 2026; docs/community/discord/structure.md section 4.1 | Every number comes from the public API (`/api/stats`, `/api/live?window=300`, `/api/supply`; docs/api/public-stats.md). The Devnet 2 line reads the fleet file and uses its numbers and the gate word only; the seed address and the state text never pass. @@ -35,6 +36,7 @@ The watcher's texts are fixed sentences in the script, each a stated rule, and a ``` node tools/community/discord-hooks.mjs pulse | digest | weekly [--live] [--force] +node tools/community/discord-hooks.mjs feed [--live] [--via updates] the hourly feed; --via updates posts it through DISCORD_WEBHOOK_UPDATES until #network-feed has a webhook node tools/community/discord-hooks.mjs release 0.3.14 --windows --windows-sha --mac --mac-sha --hive --hive-sha \ --node-commit 4c6b129d --digest "b18ed271 (thirteen fields, unchanged)" --plan docs/plans/release-0.3.14.md --section "1. Why" [--changed "line"]... [--live] node tools/community/discord-hooks.mjs incident open --what "..." --affected "..." --doing "..." [--at 2026-10-06T15:44:00Z] [--id inc-...] [--live] @@ -65,7 +67,9 @@ parenthetical dropped, 160 characters at most; a line that trips the guard is dr ## Credentials and deployment `~/.config/igneum/discord`, mode 600, KEY=VALUE lines: `DISCORD_WEBHOOK_NUMBERS`, `DISCORD_WEBHOOK_ANNOUNCEMENTS`, -`DISCORD_WEBHOOK_INCIDENTS`. Never in the repository, never printed; `check` prints which keys are set. +`DISCORD_WEBHOOK_INCIDENTS`; optional `DISCORD_WEBHOOK_FEED` (no key, no feed, one "feed off" note per tick) and +`DISCORD_WEBHOOK_UPDATES` (the hidden updates channel, the `--via updates` route). Never in the repository, never printed; +`check` prints which keys are set. The scheduler runs on igneum-build-1 because the Mac sleeps: `infra/build-server/discord-hooks/{igneum-discord-hooks.service, igneum-discord-hooks.timer, install.sh}`, a tick every minute. `install.sh` copies the script to `/srv/discord-hooks/bin`, the diff --git a/docs/community/discord/README.md b/docs/community/discord/README.md new file mode 100644 index 000000000..48b420a82 --- /dev/null +++ b/docs/community/discord/README.md @@ -0,0 +1,68 @@ +# Discord server assets and boost perks + +Server: Igneum (id 1557085229330464808), vanity https://discord.gg/igneum, boosted to level 3 on 7 October 2026 (20 boosts: 14 on the three levels, 3 on the Server Tag add-on, 3 on the Enhanced Role Styles add-on; 0 spare). + +Every file in `assets/` is built from the brand in this repo: the ember mark from `site/index.html`, the colour tokens from `site/site.css` (obsidian #0C0C0E, ember #F2541B, ember-hi #FF6A2B, molten #FFB35C, bone #F4F1EC, ink-2 #C9C7C2, ash #9A9A9E), the fonts in `site/fonts/` (Unbounded for the wordmark, IBM Plex Sans and Mono for the rest) and the DAG step recording `docs/plans/site-ui-3-shots/after-v2/home-steps-1440-dark.webm`. + +Rebuild everything from the repo root: + +``` +python3 docs/community/discord/make-assets.py [path to a frame of the recording for the invite backdrop] +sh docs/community/discord/make-banner-gif.sh +``` + +The guide banner (1920x480) was rendered with the same helpers; see the commit that added it for the snippet. + +## Files + +| File | Size | Purpose | Where it is set | +| --- | --- | --- | --- | +| `server-banner-960x540.gif` | 5.9 MB | Animated server banner: nine seconds of the live DAG scene between two dark bands that carry the lockup and the tagline (level 3 perk, limit 10 MB) | Server Settings, Boost Perks, Server Banner Background | +| `server-banner-960x540.png` | 42 KB | Static fallback for the same slot | Not uploaded (the GIF is live) | +| `banner-overlay-960x540.png` | 16 KB | Transparent overlay ffmpeg composites onto the recording for the GIF | Build input only | +| `invite-background-1920x1080.png` | 368 KB | Invite embed and invite page background: lockup and tagline over a blurred, darkened DAG frame | Server Settings, Boost Perks, Server Invite Background | +| `guide-banner-1920x480.png` | 69 KB | Server Guide header (4:1) | Server Settings, Onboarding, Server Guide, Server Guide Banner | +| `role-*.png` | 2 to 5 KB each, 64x64 | Role icons, one mark variant per role (limit 256 KB) | Server Settings, Roles, each role's Display tab | +| `emoji-*.png` | 2 to 8 KB each, 128x128 | The ten custom emoji | Server Settings, Emoji | +| `sticker-*.png` | 9 to 24 KB each, 320x320 | The three stickers (limit 512 KB) | Server Settings, Stickers | +| `make-assets.py` | | Generator for every PNG above | | +| `make-banner-gif.sh` | | ffmpeg recipe for the animated banner | | + +## Role ladder (7 October 2026) + +| Role | Colour | Style | Icon | Hoisted | Permissions | +| --- | --- | --- | --- | --- | --- | +| Founder | unchanged | solid | `role-founder.png` (molten mark on obsidian) | unchanged | untouched | +| Core | unchanged | solid | `role-core.png` (ember-hi mark on obsidian) | unchanged | untouched | +| Pool operator | #FF6A2B | gradient ember to molten | `role-pool-operator.png` (mark in a molten ring) | yes | none | +| Node runner | #F4F1EC | gradient ember to molten | `role-node-runner.png` (bone mark) | yes | none | +| Verified miner | #F2541B | gradient ember to molten | `role-verified-miner.png` (ember mark with a tick) | yes | none | +| Miner | #F2541B | gradient ember to molten | `role-miner.png` (ember mark) | yes | unchanged | +| Early miner | #FFB35C | solid | `role-early-miner.png` (obsidian mark on molten) | no | none | +| Prover | #FFB35C | gradient ember to molten | `role-prover.png` (molten mark) | no | unchanged | +| Builder | #E8E4DC | solid | `role-builder.png` (bone mark on graphite) | no | Embed Links, Attach Files | +| Researcher | #9A9A9E | solid | `role-researcher.png` (ash mark) | no | Embed Links, Attach Files | +| Community | #C9C7C2 | solid | `role-community.png` (outlined mark) | no | none | +| Bot | #9A9A9E | solid | `role-bot.png` (ash mark on row) | no | unchanged | + +"None" means the role grants nothing of its own; members fall back to @everyone. Early miner is for the first 1,000 miners. Gradient roles use the Enhanced Role Styles add-on with start #F2541B and end #FFB35C. Holographic was tried on Founder and left off: it is a fixed pink and blue shimmer with no colour control and does not read as the brand. + +List order (set by drag on 7 October 2026): Founder, Core, Pool operator, Node runner, Verified miner, Prover, Miner, Early miner, Builder, Researcher, Community, Bot, Server Booster. + +## Emoji and stickers + +Emoji names: `ign_ember`, `ign_block`, `ign_shard`, `ign_lock`, `ign_gpu`, `ign_proven`, `ign_hash`, `ign_letter`, `ign_flame`, `ign_ladder`. + +Stickers: Ember (related emoji fire), Proven (white_check_mark), GPU (desktop_computer). Three of the five free slots are used. + +## Onboarding + +Server Guide: welcome sign plus five to-dos (start-here, mining, ledger, announcements, read the rules) and the guide banner. Pre-join question "What do you mine with?" with five answers: NVIDIA, AMD and Apple grant Miner and #mining; "I run a node" grants Node runner and #devnet; "I build" grants Builder and #proving. Multiple answers allowed, not required. + +## Server Tag + +IGNM, enabled 7 October 2026 on the 3-boost add-on. Badge: Fire (Discord offers only its own pixel-art badge set, no custom upload, so the ember mark cannot be the badge; Fire is the nearest). Badge colour: custom, primary #F2541B. Members adopt the tag from Server Settings, Server Tag ("Adopt Tag") or from their own profile; the founder's account has not adopted it yet. + +## Not set, and why + +- Server Profile banner: that field only offers colour presets; it stays on "Server Icon Colour", which derives from the ember icon. diff --git a/docs/community/discord/assets/banner-overlay-960x540.png b/docs/community/discord/assets/banner-overlay-960x540.png new file mode 100644 index 000000000..6f1b1ab9c Binary files /dev/null and b/docs/community/discord/assets/banner-overlay-960x540.png differ diff --git a/docs/community/discord/assets/emoji-block.png b/docs/community/discord/assets/emoji-block.png new file mode 100644 index 000000000..1d04927b0 Binary files /dev/null and b/docs/community/discord/assets/emoji-block.png differ diff --git a/docs/community/discord/assets/emoji-flame.png b/docs/community/discord/assets/emoji-flame.png new file mode 100644 index 000000000..ae2e89138 Binary files /dev/null and b/docs/community/discord/assets/emoji-flame.png differ diff --git a/docs/community/discord/assets/emoji-gpu.png b/docs/community/discord/assets/emoji-gpu.png new file mode 100644 index 000000000..aa0927f9c Binary files /dev/null and b/docs/community/discord/assets/emoji-gpu.png differ diff --git a/docs/community/discord/assets/emoji-hash.png b/docs/community/discord/assets/emoji-hash.png new file mode 100644 index 000000000..40e0c4116 Binary files /dev/null and b/docs/community/discord/assets/emoji-hash.png differ diff --git a/docs/community/discord/assets/emoji-igneum.png b/docs/community/discord/assets/emoji-igneum.png new file mode 100644 index 000000000..633461fd9 Binary files /dev/null and b/docs/community/discord/assets/emoji-igneum.png differ diff --git a/docs/community/discord/assets/emoji-ladder.png b/docs/community/discord/assets/emoji-ladder.png new file mode 100644 index 000000000..aa4d6addb Binary files /dev/null and b/docs/community/discord/assets/emoji-ladder.png differ diff --git a/docs/community/discord/assets/emoji-letter.png b/docs/community/discord/assets/emoji-letter.png new file mode 100644 index 000000000..86f7d241a Binary files /dev/null and b/docs/community/discord/assets/emoji-letter.png differ diff --git a/docs/community/discord/assets/emoji-lock.png b/docs/community/discord/assets/emoji-lock.png new file mode 100644 index 000000000..198f4ec71 Binary files /dev/null and b/docs/community/discord/assets/emoji-lock.png differ diff --git a/docs/community/discord/assets/emoji-proven.png b/docs/community/discord/assets/emoji-proven.png new file mode 100644 index 000000000..e4a5c187a Binary files /dev/null and b/docs/community/discord/assets/emoji-proven.png differ diff --git a/docs/community/discord/assets/emoji-shard.png b/docs/community/discord/assets/emoji-shard.png new file mode 100644 index 000000000..87db67ced Binary files /dev/null and b/docs/community/discord/assets/emoji-shard.png differ diff --git a/docs/community/discord/assets/guide-banner-1920x480.png b/docs/community/discord/assets/guide-banner-1920x480.png new file mode 100644 index 000000000..868475e7a Binary files /dev/null and b/docs/community/discord/assets/guide-banner-1920x480.png differ diff --git a/docs/community/discord/assets/invite-background-1920x1080.png b/docs/community/discord/assets/invite-background-1920x1080.png new file mode 100644 index 000000000..5ccdaf903 Binary files /dev/null and b/docs/community/discord/assets/invite-background-1920x1080.png differ diff --git a/docs/community/discord/assets/role-bot.png b/docs/community/discord/assets/role-bot.png new file mode 100644 index 000000000..62c7e13cb Binary files /dev/null and b/docs/community/discord/assets/role-bot.png differ diff --git a/docs/community/discord/assets/role-builder.png b/docs/community/discord/assets/role-builder.png new file mode 100644 index 000000000..7f70ed0e8 Binary files /dev/null and b/docs/community/discord/assets/role-builder.png differ diff --git a/docs/community/discord/assets/role-community.png b/docs/community/discord/assets/role-community.png new file mode 100644 index 000000000..edc8a3c1d Binary files /dev/null and b/docs/community/discord/assets/role-community.png differ diff --git a/docs/community/discord/assets/role-core.png b/docs/community/discord/assets/role-core.png new file mode 100644 index 000000000..ba42f9619 Binary files /dev/null and b/docs/community/discord/assets/role-core.png differ diff --git a/docs/community/discord/assets/role-early-miner.png b/docs/community/discord/assets/role-early-miner.png new file mode 100644 index 000000000..5f74bf5dc Binary files /dev/null and b/docs/community/discord/assets/role-early-miner.png differ diff --git a/docs/community/discord/assets/role-founder.png b/docs/community/discord/assets/role-founder.png new file mode 100644 index 000000000..d252da90c Binary files /dev/null and b/docs/community/discord/assets/role-founder.png differ diff --git a/docs/community/discord/assets/role-miner.png b/docs/community/discord/assets/role-miner.png new file mode 100644 index 000000000..90887c9a0 Binary files /dev/null and b/docs/community/discord/assets/role-miner.png differ diff --git a/docs/community/discord/assets/role-node-runner.png b/docs/community/discord/assets/role-node-runner.png new file mode 100644 index 000000000..6655a4199 Binary files /dev/null and b/docs/community/discord/assets/role-node-runner.png differ diff --git a/docs/community/discord/assets/role-pool-operator.png b/docs/community/discord/assets/role-pool-operator.png new file mode 100644 index 000000000..02728ab72 Binary files /dev/null and b/docs/community/discord/assets/role-pool-operator.png differ diff --git a/docs/community/discord/assets/role-prover.png b/docs/community/discord/assets/role-prover.png new file mode 100644 index 000000000..04cc69b75 Binary files /dev/null and b/docs/community/discord/assets/role-prover.png differ diff --git a/docs/community/discord/assets/role-researcher.png b/docs/community/discord/assets/role-researcher.png new file mode 100644 index 000000000..1b384b605 Binary files /dev/null and b/docs/community/discord/assets/role-researcher.png differ diff --git a/docs/community/discord/assets/role-verified-miner.png b/docs/community/discord/assets/role-verified-miner.png new file mode 100644 index 000000000..022e03bb8 Binary files /dev/null and b/docs/community/discord/assets/role-verified-miner.png differ diff --git a/docs/community/discord/assets/server-banner-960x540.gif b/docs/community/discord/assets/server-banner-960x540.gif new file mode 100644 index 000000000..2dc924533 Binary files /dev/null and b/docs/community/discord/assets/server-banner-960x540.gif differ diff --git a/docs/community/discord/assets/server-banner-960x540.png b/docs/community/discord/assets/server-banner-960x540.png new file mode 100644 index 000000000..9caf2f0c7 Binary files /dev/null and b/docs/community/discord/assets/server-banner-960x540.png differ diff --git a/docs/community/discord/assets/sticker-ember.png b/docs/community/discord/assets/sticker-ember.png new file mode 100644 index 000000000..219a7502f Binary files /dev/null and b/docs/community/discord/assets/sticker-ember.png differ diff --git a/docs/community/discord/assets/sticker-gpu.png b/docs/community/discord/assets/sticker-gpu.png new file mode 100644 index 000000000..dfc52cb73 Binary files /dev/null and b/docs/community/discord/assets/sticker-gpu.png differ diff --git a/docs/community/discord/assets/sticker-proven.png b/docs/community/discord/assets/sticker-proven.png new file mode 100644 index 000000000..c480799d1 Binary files /dev/null and b/docs/community/discord/assets/sticker-proven.png differ diff --git a/docs/community/discord/make-assets.py b/docs/community/discord/make-assets.py new file mode 100644 index 000000000..1a8482dc1 --- /dev/null +++ b/docs/community/discord/make-assets.py @@ -0,0 +1,379 @@ +#!/usr/bin/env python3 +"""Build the Discord boost assets from the brand (mark, fonts, tokens in site/site.css). + +Run from the repo root: python3 docs/community/discord/make-assets.py +Writes into docs/community/discord/assets/. The animated banner is built by ffmpeg from +docs/plans/site-ui-3-shots/after-v2/home-steps-1440-dark.webm (see make-banner-gif.sh). +""" +import math +import os +import sys + +from PIL import Image, ImageDraw, ImageFont, ImageFilter + +ROOT = os.path.dirname(os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))) +OUT = os.path.join(ROOT, "docs", "community", "discord", "assets") +FONTS = os.path.join(ROOT, "site", "fonts") +os.makedirs(OUT, exist_ok=True) + +# site.css tokens (dark theme) +OBSIDIAN = (12, 12, 14) +GRAPHITE = (22, 22, 26) +ROW = (17, 17, 20) +LINE = (42, 42, 48) +LINE2 = (58, 58, 66) +EMBER = (242, 84, 27) +EMBER_HI = (255, 106, 43) +MOLTEN = (255, 179, 92) +BONE = (244, 241, 236) +INK2 = (201, 199, 194) +ASH = (154, 154, 158) + +# The ember mark, from site/index.html (viewBox 100 units) +OUTER = [(50, 4), (74, 34), (67, 58), (80, 54), (61, 96), (39, 96), (20, 54), (33, 58), (26, 34)] +INNER = [(50, 42), (59, 58), (50, 82), (41, 58)] +SS = 4 # supersample + + +def font(name, size): + return ImageFont.truetype(os.path.join(FONTS, name + ".woff2"), size) + + +def rgba(color, a=255): + return tuple(color) + (a,) + + +def mark(size, color=EMBER, cut=None, box=None): + """Return an RGBA image of the ember mark. `cut` fills the inner diamond (None = transparent).""" + W = size * SS + im = Image.new("RGBA", (W, W), (0, 0, 0, 0)) + d = ImageDraw.Draw(im) + if box is not None: + d.rounded_rectangle([0, 0, W - 1, W - 1], radius=int(W * 0.16), fill=rgba(box)) + pad = 0.12 if box is None else 0.19 + s = W * (1 - 2 * pad) / 100.0 + o = W * pad + pts = [(o + x * s, o + y * s) for x, y in OUTER] + d.polygon(pts, fill=rgba(color)) + inner = [(o + x * s, o + y * s) for x, y in INNER] + if cut is None: + hole = Image.new("L", (W, W), 0) + ImageDraw.Draw(hole).polygon(inner, fill=255) + alpha = im.getchannel("A") + alpha = Image.composite(Image.new("L", (W, W), 0), alpha, hole) + im.putalpha(alpha) + else: + d.polygon(inner, fill=rgba(cut)) + return im.resize((size, size), Image.LANCZOS) + + +def text_size(d, txt, f): + l, t, r, b = d.textbbox((0, 0), txt, font=f) + return r - l, b - t, l, t + + +def lockup(width, mark_px, word_px, word_color=BONE, mark_color=EMBER, gap=None): + """Mark + IGNEUM wordmark on a transparent strip, returned as RGBA with the strip height.""" + f = font("unbounded-900", word_px) + probe = ImageDraw.Draw(Image.new("RGBA", (10, 10))) + tw, th, tl, tt = text_size(probe, "IGNEUM", f) + gap = gap or int(mark_px * 0.32) + H = max(mark_px, th + 8) + im = Image.new("RGBA", (mark_px + gap + tw + 4, H), (0, 0, 0, 0)) + m = mark(mark_px, mark_color) + im.alpha_composite(m, (0, (H - mark_px) // 2)) + d = ImageDraw.Draw(im) + d.text((mark_px + gap - tl, (H - th) // 2 - tt), "IGNEUM", font=f, fill=rgba(word_color)) + return im + + +def glow(base, mark_px, cx, cy, color=EMBER, spread=1.6, alpha=70): + g = Image.new("RGBA", base.size, (0, 0, 0, 0)) + r = int(mark_px * spread / 2) + ImageDraw.Draw(g).ellipse([cx - r, cy - r, cx + r, cy + r], fill=rgba(color, alpha)) + g = g.filter(ImageFilter.GaussianBlur(mark_px * 0.45)) + base.alpha_composite(g) + + +# ---------------------------------------------------------------- banners +def banner_static(W, H, name, mark_px, word_px, tag_px, sub_px, backdrop=None): + im = Image.new("RGBA", (W, H), rgba(OBSIDIAN)) + if backdrop is not None: + bd = Image.open(backdrop).convert("RGB") + # crop the recording frame to 16:9 and darken it + bw, bh = bd.size + ch = int(bw * H / W) + bd = bd.crop((0, 60, bw, 60 + ch)).resize((W, H), Image.LANCZOS) + bd = bd.filter(ImageFilter.GaussianBlur(W * 0.004)) + bd = Image.blend(Image.new("RGB", (W, H), OBSIDIAN), bd, 0.34) + im.paste(bd, (0, 0)) + scrim = Image.new("RGBA", (W, H), (0, 0, 0, 0)) + sd = ImageDraw.Draw(scrim) + for y in range(H): + a = int(255 * (0.25 + 0.55 * (y / H) ** 1.4)) + sd.line([(0, y), (W, y)], fill=rgba(OBSIDIAN, min(255, a))) + im.alpha_composite(scrim) + lk = lockup(W, mark_px, word_px) + cx = (W - lk.width) // 2 + cy = int(H * 0.40) - lk.height // 2 + glow(im, mark_px, cx + mark_px // 2, cy + lk.height // 2) + im.alpha_composite(lk, (cx, cy)) + d = ImageDraw.Draw(im) + f_tag = font("unbounded-700", tag_px) + tw, th, tl, tt = text_size(d, "Mined by GPUs. Proven by fire.", f_tag) + ty = cy + lk.height + int(H * 0.06) + d.text(((W - tw) // 2 - tl, ty - tt), "Mined by GPUs. Proven by fire.", font=f_tag, fill=rgba(MOLTEN)) + f_sub = font("plex-sans-500", sub_px) + sub = "The GPU-mined layer 1 · igneum.network" + sw, sh, sl, st = text_size(d, sub, f_sub) + d.text(((W - sw) // 2 - sl, ty + th + int(H * 0.035) - st), sub, font=f_sub, fill=rgba(INK2)) + path = os.path.join(OUT, name) + im.convert("RGB").save(path, optimize=True) + return path + + +def banner_overlay(W, H, name, mark_px, word_px, band): + """Transparent overlay for the animated banner: the graph sits between two dark bands + (ffmpeg pads it); the lockup goes in the top band, the tagline in the bottom band.""" + im = Image.new("RGBA", (W, H), (0, 0, 0, 0)) + d = ImageDraw.Draw(im) + lk = lockup(W, mark_px, word_px) + x = int(W * 0.035) + im.alpha_composite(lk, (x, (band - lk.height) // 2)) + f_tag = font("unbounded-700", int(word_px * 0.62)) + tw, th, tl, tt = text_size(d, "Mined by GPUs. Proven by fire.", f_tag) + d.text((x - tl, H - band + (band - th) // 2 - tt), "Mined by GPUs. Proven by fire.", font=f_tag, fill=rgba(MOLTEN)) + f_sub = font("plex-sans-500", int(word_px * 0.5)) + sw, sh, sl, st = text_size(d, "igneum.network", f_sub) + d.text((W - x - sw - sl, H - band + (band - sh) // 2 - st), "igneum.network", font=f_sub, fill=rgba(INK2)) + path = os.path.join(OUT, name) + im.save(path, optimize=True) + return path + + +# ---------------------------------------------------------------- role icons +def role_icons(): + out = {} + spec = { + "founder": dict(color=MOLTEN, box=OBSIDIAN), + "core": dict(color=EMBER_HI, box=OBSIDIAN), + "miner": dict(color=EMBER), + "prover": dict(color=MOLTEN), + "pool-operator": dict(color=EMBER_HI, ring=True), + "node-runner": dict(color=BONE), + "verified-miner": dict(color=EMBER, tick=True), + "early-miner": dict(color=OBSIDIAN, box=MOLTEN), + "builder": dict(color=BONE, box=GRAPHITE), + "researcher": dict(color=ASH), + "community": dict(color=INK2, outline=True), + "bot": dict(color=ASH, box=ROW), + } + for name, s in spec.items(): + size = 64 + W = size * SS + if s.get("outline"): + im = Image.new("RGBA", (W, W), (0, 0, 0, 0)) + d = ImageDraw.Draw(im) + pad = 0.12 + sc = W * (1 - 2 * pad) / 100.0 + o = W * pad + pts = [(o + x * sc, o + y * sc) for x, y in OUTER] + d.line(pts + [pts[0]], fill=rgba(s["color"]), width=int(W * 0.055), joint="curve") + inner = [(o + x * sc, o + y * sc) for x, y in INNER] + d.polygon(inner, fill=rgba(s["color"])) + im = im.resize((size, size), Image.LANCZOS) + else: + im = mark(size, s["color"], cut=(s["box"] if s.get("box") else None), box=s.get("box")) + if s.get("ring"): + big = im.resize((W, W), Image.LANCZOS) + d = ImageDraw.Draw(big) + d.ellipse([W * 0.02, W * 0.02, W * 0.98, W * 0.98], outline=rgba(MOLTEN), width=int(W * 0.05)) + im = big.resize((size, size), Image.LANCZOS) + if s.get("tick"): + big = im.resize((W, W), Image.LANCZOS) + d = ImageDraw.Draw(big) + r = W * 0.19 + cx, cy = W * 0.80, W * 0.80 + d.ellipse([cx - r, cy - r, cx + r, cy + r], fill=rgba(MOLTEN)) + d.line([(cx - r * 0.5, cy), (cx - r * 0.1, cy + r * 0.42), (cx + r * 0.55, cy - r * 0.42)], + fill=rgba(OBSIDIAN), width=int(W * 0.045), joint="curve") + im = big.resize((size, size), Image.LANCZOS) + path = os.path.join(OUT, "role-%s.png" % name) + im.save(path, optimize=True) + out[name] = path + return out + + +# ---------------------------------------------------------------- emoji +def emoji_canvas(size=128): + W = size * SS + return Image.new("RGBA", (W, W), (0, 0, 0, 0)), W + + +def finish(im, size, path): + im.resize((size, size), Image.LANCZOS).save(path, optimize=True) + return path + + +def emoji_set(): + size = 128 + paths = {} + + # 1 the ember + paths["igneum"] = mark(size, EMBER) + paths["igneum"].save(os.path.join(OUT, "emoji-igneum.png"), optimize=True) + paths["igneum"] = os.path.join(OUT, "emoji-igneum.png") + + # 2 a block (the DAG square: rounded outline, ember, dark fill) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + m = W * 0.12 + d.rounded_rectangle([m, m, W - m, W - m], radius=int(W * 0.14), fill=rgba(GRAPHITE), + outline=rgba(EMBER), width=int(W * 0.085)) + paths["block"] = finish(im, size, os.path.join(OUT, "emoji-block.png")) + + # 3 a shard (a tall molten crystal with one lit facet) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + p = [(0.50, 0.06), (0.78, 0.40), (0.62, 0.94), (0.38, 0.94), (0.22, 0.40)] + d.polygon([(x * W, y * W) for x, y in p], fill=rgba(MOLTEN)) + d.polygon([(x * W, y * W) for x, y in [(0.50, 0.06), (0.78, 0.40), (0.62, 0.94), (0.50, 0.40)]], fill=rgba(EMBER)) + paths["shard"] = finish(im, size, os.path.join(OUT, "emoji-shard.png")) + + # 4 a lock (ember body, bone shackle, dark keyhole) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + sw = int(W * 0.09) + d.arc([W * 0.26, W * 0.06, W * 0.74, W * 0.60], 180, 360, fill=rgba(BONE), width=sw) + d.line([(W * 0.26 + sw / 2, W * 0.33), (W * 0.26 + sw / 2, W * 0.50)], fill=rgba(BONE), width=sw) + d.line([(W * 0.74 - sw / 2, W * 0.33), (W * 0.74 - sw / 2, W * 0.50)], fill=rgba(BONE), width=sw) + d.rounded_rectangle([W * 0.14, W * 0.46, W * 0.86, W * 0.94], radius=int(W * 0.10), fill=rgba(EMBER)) + d.ellipse([W * 0.43, W * 0.60, W * 0.57, W * 0.74], fill=rgba(OBSIDIAN)) + d.rounded_rectangle([W * 0.465, W * 0.68, W * 0.535, W * 0.84], radius=int(W * 0.03), fill=rgba(OBSIDIAN)) + paths["lock"] = finish(im, size, os.path.join(OUT, "emoji-lock.png")) + + # 5 a GPU (graphite card, two ember fans, bone bracket) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + d.rounded_rectangle([W * 0.06, W * 0.24, W * 0.94, W * 0.78], radius=int(W * 0.08), fill=rgba(GRAPHITE), + outline=rgba(LINE2), width=int(W * 0.03)) + d.rectangle([W * 0.06, W * 0.78, W * 0.16, W * 0.90], fill=rgba(BONE)) + d.rectangle([W * 0.20, W * 0.74, W * 0.80, W * 0.80], fill=rgba(LINE2)) + for cx in (0.34, 0.66): + r = W * 0.17 + d.ellipse([cx * W - r, W * 0.51 - r, cx * W + r, W * 0.51 + r], outline=rgba(EMBER), width=int(W * 0.045)) + for k in range(6): + a = k * math.pi / 3 + d.line([(cx * W, W * 0.51), (cx * W + math.cos(a) * r * 0.85, W * 0.51 + math.sin(a) * r * 0.85)], + fill=rgba(EMBER), width=int(W * 0.035)) + d.ellipse([cx * W - r * 0.22, W * 0.51 - r * 0.22, cx * W + r * 0.22, W * 0.51 + r * 0.22], fill=rgba(MOLTEN)) + paths["gpu"] = finish(im, size, os.path.join(OUT, "emoji-gpu.png")) + + # 6 the proof tick (ember rounded square, bone tick) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + d.rounded_rectangle([W * 0.08, W * 0.08, W * 0.92, W * 0.92], radius=int(W * 0.18), fill=rgba(EMBER)) + d.line([(W * 0.28, W * 0.52), (W * 0.44, W * 0.68), (W * 0.74, W * 0.34)], fill=rgba(BONE), width=int(W * 0.10), + joint="curve") + paths["proven"] = finish(im, size, os.path.join(OUT, "emoji-proven.png")) + + # 7 the hash glyph (Plex Mono) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + f = font("plex-mono-500", int(W * 0.92)) + tw, th, tl, tt = text_size(d, "#", f) + d.text(((W - tw) / 2 - tl, (W - th) / 2 - tt), "#", font=f, fill=rgba(EMBER)) + paths["hash"] = finish(im, size, os.path.join(OUT, "emoji-hash.png")) + + # 8 the wordmark letter (bone I on an ember square) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + d.rounded_rectangle([W * 0.08, W * 0.08, W * 0.92, W * 0.92], radius=int(W * 0.18), fill=rgba(OBSIDIAN)) + f = font("unbounded-900", int(W * 0.62)) + tw, th, tl, tt = text_size(d, "I", f) + d.text(((W - tw) / 2 - tl, (W - th) / 2 - tt), "I", font=f, fill=rgba(EMBER)) + paths["letter"] = finish(im, size, os.path.join(OUT, "emoji-letter.png")) + + # 9 a flame (ember outer, molten core) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + outer = [(0.50, 0.04), (0.64, 0.22), (0.70, 0.40), (0.82, 0.30), (0.88, 0.58), (0.80, 0.84), (0.62, 0.96), + (0.38, 0.96), (0.20, 0.84), (0.12, 0.58), (0.20, 0.36), (0.32, 0.44), (0.34, 0.24)] + d.polygon([(x * W, y * W) for x, y in outer], fill=rgba(EMBER)) + core = [(0.50, 0.46), (0.62, 0.60), (0.66, 0.78), (0.58, 0.92), (0.42, 0.92), (0.34, 0.78), (0.38, 0.60)] + d.polygon([(x * W, y * W) for x, y in core], fill=rgba(MOLTEN)) + paths["flame"] = finish(im, size, os.path.join(OUT, "emoji-flame.png")) + + # 10 the ladder (two ember rails, bone rungs) + im, W = emoji_canvas() + d = ImageDraw.Draw(im) + rw = int(W * 0.09) + d.line([(W * 0.28, W * 0.06), (W * 0.28, W * 0.94)], fill=rgba(EMBER), width=rw) + d.line([(W * 0.72, W * 0.06), (W * 0.72, W * 0.94)], fill=rgba(EMBER), width=rw) + for k in range(5): + y = W * (0.16 + k * 0.17) + d.line([(W * 0.28, y), (W * 0.72, y)], fill=rgba(BONE), width=int(W * 0.07)) + paths["ladder"] = finish(im, size, os.path.join(OUT, "emoji-ladder.png")) + return paths + + +# ---------------------------------------------------------------- stickers (320x320) +def stickers(): + size = 320 + paths = {} + # 1 the ember, large + m = mark(size, EMBER) + p = os.path.join(OUT, "sticker-ember.png") + m.save(p, optimize=True) + paths["ember"] = p + + # 2 "Proven by fire." badge + im = Image.new("RGBA", (size * SS, size * SS), (0, 0, 0, 0)) + W = size * SS + d = ImageDraw.Draw(im) + d.rounded_rectangle([W * 0.03, W * 0.30, W * 0.97, W * 0.70], radius=int(W * 0.10), fill=rgba(OBSIDIAN), + outline=rgba(EMBER), width=int(W * 0.02)) + f1 = font("unbounded-900", int(W * 0.115)) + f2 = font("unbounded-700", int(W * 0.062)) + tw, th, tl, tt = text_size(d, "PROVEN", f1) + d.text(((W - tw) / 2 - tl, W * 0.37 - tt), "PROVEN", font=f1, fill=rgba(BONE)) + tw2, th2, tl2, tt2 = text_size(d, "by fire.", f2) + d.text(((W - tw2) / 2 - tl2, W * 0.37 + th + W * 0.04 - tt2), "by fire.", font=f2, fill=rgba(MOLTEN)) + p = os.path.join(OUT, "sticker-proven.png") + im.resize((size, size), Image.LANCZOS).save(p, optimize=True) + paths["proven"] = p + + # 3 GPU with the ember rising out of it + im = Image.new("RGBA", (W, W), (0, 0, 0, 0)) + d = ImageDraw.Draw(im) + em = mark(int(size * 0.55), EMBER).resize((int(W * 0.55), int(W * 0.55)), Image.LANCZOS) + im.alpha_composite(em, (int(W * 0.225), int(W * 0.02))) + d.rounded_rectangle([W * 0.06, W * 0.52, W * 0.94, W * 0.86], radius=int(W * 0.07), fill=rgba(GRAPHITE), + outline=rgba(LINE2), width=int(W * 0.02)) + d.rectangle([W * 0.06, W * 0.86, W * 0.16, W * 0.95], fill=rgba(BONE)) + for cx in (0.34, 0.66): + r = W * 0.12 + cy = W * 0.69 + d.ellipse([cx * W - r, cy - r, cx * W + r, cy + r], outline=rgba(EMBER), width=int(W * 0.03)) + for k in range(6): + a = k * math.pi / 3 + d.line([(cx * W, cy), (cx * W + math.cos(a) * r * 0.85, cy + math.sin(a) * r * 0.85)], + fill=rgba(EMBER), width=int(W * 0.025)) + d.ellipse([cx * W - r * 0.22, cy - r * 0.22, cx * W + r * 0.22, cy + r * 0.22], fill=rgba(MOLTEN)) + p = os.path.join(OUT, "sticker-gpu.png") + im.resize((size, size), Image.LANCZOS).save(p, optimize=True) + paths["gpu"] = p + return paths + + +if __name__ == "__main__": + frame = sys.argv[1] if len(sys.argv) > 1 else None + print(banner_static(960, 540, "server-banner-960x540.png", 150, 96, 30, 20)) + print(banner_static(1920, 1080, "invite-background-1920x1080.png", 300, 192, 60, 40, backdrop=frame)) + print(banner_overlay(960, 540, "banner-overlay-960x540.png", 46, 30, 87)) + for k, v in role_icons().items(): + print(k, v, os.path.getsize(v)) + for k, v in emoji_set().items(): + print(k, v, os.path.getsize(v)) + for k, v in stickers().items(): + print(k, v, os.path.getsize(v)) diff --git a/docs/community/discord/make-banner-gif.sh b/docs/community/discord/make-banner-gif.sh new file mode 100755 index 000000000..c166b3fa7 --- /dev/null +++ b/docs/community/discord/make-banner-gif.sh @@ -0,0 +1,11 @@ +#!/bin/sh +# Animated server banner (level 3 perk): nine seconds of the DAG step recording (from 1 s, after the hero fold), graph only, +# padded into two dark bands that carry the lockup and the tagline (banner-overlay-960x540.png). +# Run from the repo root after make-assets.py. Output stays under Discord's 10 MB banner limit. +set -e +A=docs/community/discord/assets +SRC=docs/plans/site-ui-3-shots/after-v2/home-steps-1440-dark.webm +ffmpeg -v error -y -ss 1 -t 9 -i "$SRC" -i "$A/banner-overlay-960x540.png" -filter_complex \ + "[0:v]crop=1340:510:50:118,pad=1340:754:0:122:color=#0C0C0E,scale=960:540,fps=12[b];[b][1:v]overlay=0:0,split[a][c];[a]palettegen=max_colors=160:stats_mode=diff[p];[c][p]paletteuse=dither=bayer:bayer_scale=4:diff_mode=rectangle" \ + "$A/server-banner-960x540.gif" +ls -la "$A/server-banner-960x540.gif" diff --git a/docs/community/discord/structure.md b/docs/community/discord/structure.md new file mode 100644 index 000000000..52766e0bf --- /dev/null +++ b/docs/community/discord/structure.md @@ -0,0 +1,333 @@ +# Discord server structure: the build sheet and the changelog + +Server Igneum (id 1557085229330464808, https://discord.gg/igneum). This file is the structure half of the server; the +cosmetics half (banner, roles ladder, emoji, stickers, server guide, pre-join question, server tag, vanity) is in +README.md. Every item below is a row with a "set / read back" state. A row is set only when it has been read back +from the server after the change. Nothing is posted that names a number our files do not hold. + +The founder, 7 October 2026, 12:0x UK: "is discord fully setup and optimised to house an amazing community?" Cosmetics yes; +structure no. This sheet is the structure. + +## Status, 7 October 2026, 13:1x UK + +| Item | State | +|---|---| +| Chrome profile | confirmed: the signed-in Google account on the tab is the igneum.network login, the Igneum profile; the Discord account is igneum_network (Founder) | +| Discord session | expired at 11:1x UK (nothing typed); the founder signed in at 12:5x UK and the sheet was built in one pass from 12:5x to 13:1x UK | +| Channels | 24 channels in 4 categories, every topic set, 19 pinned first posts, slowmode 10 s on every talk and support channel, threads on, read-only where the sheet says (section 1, every row "set, read back") | +| Moderation | 7 AutoMod rules live (section 2), verification Medium, explicit filter on all members, raid protection 3 of 3, DM protection 5 of 5, prune restricted to admins, #mod-log private with every alert, rules screen on with the four lines | +| Onboarding | pre-join answers re-pointed at the new map, 5 server-guide to-dos, welcome sign rewritten, safety notifications to #mod-log | +| Network feed | LIVE from the box every hour: `DISCORD_WEBHOOK_FEED` created (webhook "Igneum feed" on #network-feed, 13:0x UK), written to `~/.config/igneum/discord`, `install.sh` run with the ruling flag at 13:05 UK; the box's first hourly post `feed:2026-10-07:13` landed at 13:06 UK (message 1557363371605622818) and the next tick was "0 due". The Mac's proof posts: `feed:2026-10-07:11` through the updates webhook (11:30 UK) and `feed:2026-10-07:12-proof` through the new webhook (13:05 UK, message 1557363266689171547) | +| Not done, owed | 2FA for moderation (the founder account's 2FA is off: Discord greys the switch); the office-hour event (Discord has no undated event; the template is section 5, created the day a time is picked). Done at 13:1x UK: post 1's "How this channel works" paragraph edited through the announcements webhook (PATCH 200, edited 12:11:37 UTC); the release webhook moved to #releases | + +## 1. Channel map + +Order top to bottom as the sidebar shows it. "Threads" means Create Public Threads allowed for @everyone and the +channel's own threads kept (auto-archive 3 days). Slowmode is 10 s where set. A pinned post is the channel's first +message, posted from the founder's account (the webhook posts only the bot's numbers), then pinned. + +### What changes from the current server + +| Today | Becomes | Why | +|---|---|---| +| #numbers | #network-feed, read-only, under START HERE's bot row moved to its own place below MINE | one bot channel; the pulse, the digest, the weekly, the hash-origin report and the hourly feed all land here. `DISCORD_WEBHOOK_NUMBERS` keeps working (the webhook follows the channel through a rename); `DISCORD_WEBHOOK_FEED` is set to the same channel's URL (a second webhook named "Igneum feed", or the same URL copied) | +| #first-blocks | #first-block | the brief's name; one block per post, so the singular reads right. ladder.md says #first-blocks; this sheet is the later word | +| #ask | removed | the four support channels and #mining take questions; the pinned FAQ answers the common ones; #ask's messages are read once for anything worth pinning before deletion | +| #wallet | removed | wallet questions go to the support channel of the OS; the wallet page is linked from every support pin | +| #incidents | kept, under START HERE after #releases | the watcher already posts there; cause and fix in public is the ledger's rule | +| #ledger | kept, under BUILD last | criticism with a ledger id and a date, as announcement 1 says | +| #discord-updates | kept, hidden (Founder and Core only) | the CI red watcher and the feed's proof post use its webhook | +| #mining, #devnet, #proving, #start-here, #announcements, #rules | kept, topics and pins set below | | + +### START HERE (read-only for @everyone: Send Messages off on the category; Core and Founder post) + +| Channel | Topic | Pinned first post | Settings | Set / read back | +|---|---|---|---|---| +| #start-here | What Igneum is, what to do first, the ladder. | the welcome post (section 3.3) | read-only; the server guide's first to-do | set, read back | +| #rules | Three rules. Read once. | the rules post (section 2.6, the same words as the rules screen) | read-only | set, read back | +| #announcements | Releases and chain events only. Announcement channel (followable). | announcement 1 is already here (announcement-01.md); edit its "How this channel works" line to: "Releases in #releases, numbers every hour in #network-feed from the labelled bot. Incidents, with cause and fix, in #incidents. Questions in #mining or the support channel for your OS, criticism in #ledger, where it gets a ledger id and a date." | read-only; Announcement channel type | set, read back | +| #releases | One post per release: version, downloads, sha256, what changed. The app updates itself. (The "Igneum" release webhook was moved here from #announcements at 13:13 UK; read back from Discord: channel 1557346271726141471.) | "Every release lands here from the bot: the version, the three downloads with their sha256, the node commit, up to five lines on what changed. The app updates itself over the air at a safe moment; a fresh install is at igneum.network/miner. A release is posted after it has crossed the staging chain, never before." | read-only; `DISCORD_WEBHOOK_ANNOUNCEMENTS` moves here (Channel settings, Integrations, Webhooks, edit the channel of the "Igneum" webhook); #announcements keeps human posts only | set, read back | +| #incidents | What broke, who it affects, what is being done. Then the cause and the fix. | "An incident is posted when it opens and when it resolves: the UTC time, what happened, who is affected per tier, what is being done; then the cause, the fix and how long it lasted. Three are automatic from the public API: finality paused over five minutes, proving over fifteen minutes behind, the live numbers stale over three minutes. Everything else a person wrote." | read-only | set, read back | + +### MINE + +| Channel | Topic | Pinned first post | Settings | Set / read back | +|---|---|---|---|---| +| #mining | Mining talk: cards, rates, settings, what your card is doing. | "Mining questions go here. Say the card, the OS and the app version; the Cards page shows all three. Every rate the project publishes has a row in the bench table (igneum.network/miners) with the command and the hardware. Nothing here is estimated earnings. No price talk: there is no market and nothing is for sale." | slowmode 10 s; threads on | set, read back | +| #rig-photos | Your rig, your card, your first block card. Photos only, a line of text. | "Post the rig. One photo or the saved block card, one line: the cards, the OS, the rate the app shows. No serial numbers, no machine names, no payout addresses in the shot. Threads for the replies, so the photos stay a wall." | threads on; slowmode 10 s; Attach Files on for @everyone in this channel only | set, read back | +| #first-block | Every first block, posted by the bot. Your reply under it. | "When a key finds its first blue block the bot posts it here: the short key id and the block link, and the card if the miner switched 'Make my page public' on in the app. Reply in the thread under it. The next rungs are in #start-here." | threads on; Send Messages off for @everyone, Send Messages in Threads on; the ladder bot posts (section 4.2) | set, read back | +| #benchmarks | Your card's rate and watts, the command, the app version. The bench table is built from rows like these. | "A benchmark is a row: card, driver, OS, app version, MH/s, W, and the command or the screen it came from. The project's own rows are at igneum.network/miners with the hardware named. Say the watts; a row without them is not used." | slowmode 10 s; threads on | set, read back | +| #support-windows | Windows: install, SmartScreen, the firewall prompt, drivers. | the FAQ post (section 1.5) with the Windows line first: "SmartScreen shows 'Windows protected your PC' on a new build: More info, then Run anyway. The firewall prompt comes 20 to 50 seconds in; it is the app opening its port." | slowmode 10 s; threads on by default | set, read back | +| #support-mac | macOS: Gatekeeper, Open Anyway, Apple silicon. | the FAQ post with the Mac line first: "macOS refuses an app it has not seen: System Settings, Privacy and Security, Open Anyway. Apple silicon mines; it proves on the CPU, slowly." | slowmode 10 s; threads on by default | set, read back | +| #support-linux-hiveos | Linux and HiveOS: the tarball, the flight sheet, drivers. | the FAQ post with the Linux line first: "The Linux and HiveOS tarball and the flight sheet are at igneum.network/miner. Say the distribution and the driver version with every question." | slowmode 10 s; threads on by default | set, read back | +| #pools | Pools: the project's pool-0 when it opens, and every outside pool with a signed statement. | "Until the public testnet every machine mines solo on its own keys, and a card runs several. Pools come with the testnet; the project runs pool-0 at 1 percent, the same as the optional software fee, and an outside pool is listed here once it publishes a signed key list. A pool never holds your vote weight: the member's own vote key is in every header." | slowmode 10 s; threads on | set, read back | + +### #network-feed (its own row under MINE; the bot's only voice) + +| Channel | Topic | Pinned first post | Settings | Set / read back | +|---|---|---|---|---| +| #network-feed | Numbers from the public API, every hour. Read-only. | "Every hour: height, hash rate, keys and the last lock, from igneum.network/api/live. Four times a day the fuller pulse, at 09:00 UK the daily digest, Monday the weekly numbers, daily the hash-origin report (who found the blocks). Milestones once each. The bot never replies; questions go to #mining." | Send Messages off for @everyone and every role; webhooks "Igneum" (numbers) and "Igneum feed" (feed) | set, read back; two feed posts in the channel at 13:05 and 13:06 UK | + +### BUILD + +| Channel | Topic | Pinned first post | Settings | Set / read back | +|---|---|---|---|---| +| #devnet | The devnet: resets, activations, what the node is doing. | "The devnet has mined since 3 October 2026. Coins on it have no value and the chain may be reset. A consensus change flips when 95 percent of mining weight signals it, with a floor height as the backstop; it is announced here first. The staging chain crosses first, every time." | slowmode 10 s; threads on | set, read back | +| #proving | Proving: shards, the proof pool, what your card can prove. | "Every block is proven in shards by miners' cards and paid from the block. The Prove page of the app says in one sentence what your card can do: the full shard needs a 24 GB NVIDIA card, a 32 GB card mines and proves at once, Apple silicon proves on the CPU. Proof lag and shards paid are in #network-feed." | slowmode 10 s; threads on | set, read back | +| #node-runners | Running a node: sync, peers, the RPC, the snapshot. | "A node runner's channel. Say the version, the height and the peer count; the node prints all three. A node that pauses finality reports it itself. Snapshots are refused below the node's tip; a reorg never resets execution. Node problems that look like consensus go to #devnet." | slowmode 10 s; threads on; the pre-join "I run a node" lands here | set, read back | +| #dev | Building on or with Igneum: the client, the API, the explorer, tools. | "For people writing code. The public API is igneum.network/api/stats, /api/live and /api/supply, every field named. The repository opens with the public testnet. A claim about another chain cites the repo and file or is labelled approximate." | slowmode 10 s; threads on; the pre-join "I build" lands here | set, read back | +| #spec | The spec, line by line. An issue on the spec is the way to report a flaw. | "The litepaper is at igneum.network/litepaper and the spec pages under it. Quote the line you mean. A flaw goes to hello@igneum.network or an issue on the spec; it gets a ledger id and a date in #ledger." | slowmode 10 s; threads on | set, read back | +| #ledger | Every criticism, with a ledger id and a date, and what was done. | "Criticism lands here and at igneum.network/ledger with an id and a date. Nothing is deleted; a resolved item says how. The founder is one person, pseudonymous, building with AI systems; say so if that is your criticism, it has an entry." | slowmode 10 s; threads on | set, read back | + +### COMMUNITY + +| Channel | Topic | Pinned first post | Settings | Set / read back | +|---|---|---|---|---| +| #general | Everything else about Igneum. | "General talk. The three rules: be kind, no seed phrases ever, nobody from Igneum will DM you first. No price talk: there is no market and nothing is for sale. Regional threads open here when a language has ten people asking for one." | slowmode 10 s; threads on | set, read back | +| #off-topic | Not Igneum. GPUs, games, the weather. | "Anything but Igneum and anything but prices. Same three rules." | slowmode 10 s | set, read back | + +### Hidden (Founder and Core) + +| Channel | Topic | Settings | Set / read back | +|---|---|---|---| +| #mod-log | AutoMod alerts and moderation notes. | private; every AutoMod rule's alert channel | set, read back | +| #discord-updates | CI red runs, the feed's proof posts, tooling notes. | private; unchanged; holds the `DISCORD_WEBHOOK_UPDATES` webhook | exists | + +Regional threads: not now. A regional thread opens in #general when ten members ask for one language; it is a thread, +not a channel, until it carries a week of talk (the no-empty-channels rule applies to channels, not threads). + +### 1.5 The support FAQ pin (the same post in the three support channels, the OS line first) + +From the miner page's "Before you start" section, verbatim where it is quoted: + +``` +Before you start. The questions worth asking. + +Does this website use my GPU to mine? +No. Mining happens only in the app you install, and only when you press Start. + +Does my card mine and prove? +Every card mines. Proving the full shard needs a 24 GB NVIDIA card; a 32 GB card does both at once. Apple silicon proves on the CPU, slowly. The Prove page of the app says in one sentence what your card can do. + +Is the devnet paying real money? +No. Devnet coins have no value and the chain may reset. The app's pounds row reads 0.00 on devnet and says why. + +Is there a fee? +Not in the protocol: no dev fund, no fee to any team. The app takes an optional 1% software fee, the norm for GPU miners, and one flag turns it off. + +Can I run it on a rig or in a pool? +The Linux and HiveOS tarball is on the miner page with the flight sheet. Pools are part of the public testnet; until then every machine mines solo on its own keys, and a card runs several. + +Where do the numbers come from? +Every rate has a row in the bench table and an entry in the engineering log with the command and the hardware. Nothing is estimated earnings. + +Ask here with the card, the OS and the app version. Nobody from Igneum will DM you first. igneum.network/miner +``` + +## 2. Moderation + +| Setting | Value | Where | Set / read back | +|---|---|---|---| +| Verification level | Medium (was already Medium) | Safety Setup, DM and Spam Protection | read back | +| Explicit image filter | Filter messages from all members (was already on) | Safety Setup, AutoMod, Sensitive content filters | read back | +| 2FA requirement for moderation | off: the switch is greyed until the founder account enables 2FA | Server Settings, Safety Setup, Permissions | OWED (needs the founder) | +| @everyone role | Mention @everyone, @here and All Roles: off. Also off: Manage Messages, Manage Threads, Create Private Threads, Use External Emoji stays on, Create Invite on | Server Settings, Roles, Default Permissions | set, read back | +| Bot role | View Channels, Send Messages, Embed Links, Attach Files, Read Message History. Nothing else (no Manage, no Mention Everyone, no Administrator). Webhooks are not members and carry no role; this role is for the ladder bot's user only until that bot gets its own role (section 4.2) | Server Settings, Roles, Bot | set, read back | +| #mod-log | private channel, Founder and Core; the alert channel of every AutoMod rule | Channel create | set, read back | +| Rules screen | Server Rules on (Access tab), four lines: the three rules and the no-price plus report-a-flaw line | Server Settings, Access, Server Rules | set, read back | +| DM spam | DM and Spam Protection 5 of 5 on; Raid Protection and CAPTCHA 3 of 3 on; activity alerts to #discord-updates; member prune restricted to admins (set today) | Safety Setup | read back | + +### 2.1 to 2.5 AutoMod rules, as built (Server Settings, Safety Setup, AutoMod; every alert to #mod-log; Core exempt; #mod-log and #discord-updates exempt where a channel field exists) + +Discord's keyword rule takes words and wildcards; the regex field was not needed. Seven rules are live: + +| # | Rule (Discord name) | Trigger | Action | Read back | +|---|---|---|---|---| +| 1 | Invite and spam links (14 words) | `*discord.com/invite/*, *discord.gg/*, *discordapp.com/invite/*, *discord.com/invite*, *bit.ly/*, *tinyurl.com/*, *cutt.ly/*, *t.me/*, *wa.me/*, *.xyz/*, *.top/*, *.click/*, *.buzz/*, *.icu/*` (the old "Igneum words and invites" rule, renamed and rewritten; its price words moved to rule 3) | block, alert #mod-log | enabled | +| 2 | Seed phrases and wallet scams (19 words) | `seed phrase, seed phrases, recovery phrase, secret phrase, 12 words, 24 words, private key, send to, send me, dm me, message me first, validate your wallet, sync your wallet, connect your wallet, claim your, airdrop, giveaway, support ticket, open a ticket` | block, alert, time out 10 min | enabled | +| 3 | Price pumping (alert only) (22 words) | `100x, 1000x, to the moon, wen moon, pump, pumping, buy now, buy the dip, price prediction, price target, listing soon, when binance, wen binance, wen lambo, presale, ico, ido, wen listing, wtb, wts, for sale, otc` | alert only, no block (a miner asking is a conversation; a mod answers with the pin) | enabled | +| 4 | Impersonation of the team (10 words) | `igneum team, igneum support, official igneum, igneum admin, igneum mod, igneum staff, from igneum, igneum official, igneum helpdesk, igneum customer service` | block, alert | enabled | +| 5 | Block Words in Member Profile Names | `*igneum*, *admin*, *moderator*, *support*, *official*, *helpdesk*, *team*` in display names | block member interactions, alert | enabled | +| 6 | Block Commonly Flagged Words (Discord preset) | Severe Profanity, Insults and Slurs, Sexual Content, all three lists | block, alert | enabled | +| 7 | Block Suspected Spam Content (Discord preset) | Discord's spam model | block, alert | enabled | +| 8 | Block Mention Spam (Discord preset) | was already on | block | enabled | + +Owed: the test from a non-Core account (one blocked message per rule in #mod-log, one legitimate message passing: a payout address, a sha256, "2x per joule"). The founder's account is Core-exempt and the server has one member, so the test waits for a second account. + +### 2.6 The rules text (the rules screen and #rules, the same words) + +``` +Three rules. + +1. Be kind. Argue the claim. +2. No seed phrases ever. Not yours, not anyone's, not in a DM, not "to check". +3. Nobody from Igneum will DM you first. Anyone who does is not from Igneum. + +No price talk: there is no market and nothing is for sale. + +Report a flaw: hello@igneum.network or an issue on the spec. Nobody from Igneum will ask for your seed. +``` + +## 3. Onboarding + +### 3.1 Server guide to-dos (Server Settings, Onboarding, Server Guide), aligned with the map + +| # | To-do | Channel | +|---|---|---| +| 1 | Read what Igneum is and the ladder | #start-here | +| 2 | Read the three rules | #rules | +| 3 | Pick your lane: Miner, Node runner, Builder (the question you answered on joining; change it in Channels and Roles) | #mining | +| 4 | Post your first block when it lands | #first-block | +| 5 | Follow releases | #releases | + +As built: to-do 1 "Read what Igneum is and the ladder" in #start-here (visit), 2 "Say hello in mining: your card, the OS, the app version" in #mining (message), 3 "Post your first block when it lands" in #first-block (visit), 4 "Follow releases: version, downloads, what changed" in #releases (visit), 5 "Read the rules" (Discord's built-in). Welcome sign: "Welcome. Three rules in #rules: be kind, no seed phrases ever, nobody from Igneum will DM you first. #start-here has the ladder: your first block lands in #first-block. Nothing is for sale and devnet coins have no value." Author igneum_network. The guide banner is the one in README.md. + +### 3.2 The pre-join question (Server Settings, Onboarding, Default Channels and Questions) + +Question "What do you mine with?" stays. Answers and what each hands out: + +| Answer | Role | Channels joined | +|---|---|---| +| NVIDIA | Miner | #mining, #first-block, #rig-photos, #support-windows, #support-linux-hiveos | +| AMD | Miner | #mining, #first-block, #rig-photos, #support-windows, #support-linux-hiveos | +| Apple | Miner | #mining, #first-block, #rig-photos, #support-mac | +| I run a node | Node runner | #node-runners, #devnet | +| I build | Builder | #dev, #spec, #proving | + +Multiple answers allowed, not required. As built (13:0x UK): the five answers re-pointed exactly as the table above; Discord reports 22 of 22 public channels assignable and no public channel missing from Questions and Default Channels (22 default channels, unchanged). + +### 3.3 The welcome post in #start-here (pinned, from the founder's account) + +``` +Welcome to Igneum. + +A proof-of-work chain built for graphics cards. The miners also prove every block and are paid for it from the block. No premine, no stake, no fee to any team in the protocol. One founder, pseudonymous, building with AI systems; every criticism we know of is at igneum.network/ledger. + +Start here +1. Install the miner: igneum.network/miner. Windows, macOS, Linux and HiveOS. +2. Press Start. The app says what your card can do. +3. Your first block lands in #first-block. Reply under it. + +The ladder. The chain computes it, nobody hands it out. +First block: one blue block with your key. The bot posts it in #first-block. +Your key has a vote: 100 blocks in the 30-day window (the dust line). The Voter role. +Your signature is in a checkpoint: the first lock carrying your vote. +Full window: 30 of 30 days with blocks. The Window role. +Rank: your place by weight among all keys, on igneum.network/live. +Your card proved a shard: a paid shard record. The Prover role. + +Questions in #mining or the support channel for your OS. Numbers every hour in #network-feed. Rules in #rules; there are three. +Devnet coins have no value and the chain may be reset. Nothing is for sale. +``` + +The rung names and rules are reinvent.md section 3.7 and ladder.md; on the devnet the dust line is the chain's +`params.dust` (5 today), and the bot's rung 1 post says the number it read, never the constant. + +## 4. Bots + +Two bots. Neither replies, neither mentions, both post from the public API only, both go through the forbidden-string +guard in `tools/community/discord-hooks.mjs` (the founder's name, hosts, machine ids, paths, IPs, 32-hex tokens, +webhook URLs, any mention). + +### 4.1 The network feed bot (webhook; BUILT and LIVE from the box since 13:06 UK, 7 October 2026) + +What it is: `tools/community/discord-hooks.mjs feed`, added 7 October 2026 beside pulse, digest and weekly. A webhook +needs no bot user, no token and no Discord permission beyond the webhook itself (Channel settings, Integrations, +Webhooks, "Igneum feed" on #network-feed, or the existing "Igneum" webhook's URL copied into the key). + +| Post | When | Exact shape | +|---|---|---| +| Network feed | every hour, on the London clock, through `tick` | title "Network feed" linking igneum.network/live; line 1 "igneum-devnet. Devnet coins have no value. https://igneum.network/live"; fields Height (`state.height`, blocks/s over the hour from `block_count`), Hash rate (`state.hashes_per_second_estimate`, difficulty), Keys (`state.miners_10m` "active in 10 min (a card runs several)", `finality.weights.voters` "voters in the 30-day window"), Last lock (the newest locked checkpoint: index, share of weight, age, voters); footer the UK time with UTC in brackets and "every hour from /api/live; this channel is read-only, questions go to #mining" | +| Hash origin, daily | in the first feed of the day that sees a new `state.hash_origin.date` (the launch pack's job writes it at 08:30 UTC) | one extra field "Hash origin, ": "N keys found a block, M above dust, ten largest X% of blocks, project fleet Y%, P attested pools. Full report in #numbers." A field the report lacks is left out, never estimated | +| Milestone | once each, when a feed crosses it | title "Milestone": every 100,000 chain blocks ("Chain block 100,000. igneum.network/block/100000"), every 10,000 locks, every 10,000 paid shards, the first crossing of 100, 250, 500, 1,000, 2,500, 5,000, 10,000 vote keys active at once, the first crossing of 1, 10, 100 GH/s and 1, 10, 100 TH/s. The first feed seeds and posts none | + +Read back today (7 October 2026, 11:30 UK, dry run against the live API, then one live post through the updates +webhook as the proof of the path): "Height 162,099, 1.47 blocks/s last 60 s; Hash rate 444.7 MH/s, difficulty +210,368,365; Keys 17 active in 10 min, 16 voters in the 30-day window; Last lock checkpoint 8,723 at 72.1% of weight, +16 s ago, 16 voters". 413 characters. Tests: 37 pass (`node --test tools/community/discord-hooks.test.mjs`). + +What the numbers mean per tier (the consequences rule): 17 keys and 444.7 MH/s is the project's own machines on the +devnet, so the feed names no outside miner yet; a home miner with one 8 GB card at the measured rates sees a first +block inside the hour at this size, and the Keys line is the one that tells them when that stops being true (the +pool is the answer from about 1 TH/s, reinvent.md 3.5). + +Turned on 7 October 2026, 13:05 UK: the webhook "Igneum feed" was created on #network-feed (Channel settings, +Integrations, Webhooks), its URL copied straight from Discord's button into `~/.config/igneum/discord` as +`DISCORD_WEBHOOK_FEED` (the clipboard was cleared after; the URL was never printed), then +`IGNEUM_SECRET_ON_BOX_OK=1 infra/build-server/discord-hooks/install.sh` copied the new script and the file to the box. +The box's tick posted `feed:2026-10-07:13` at 13:06 UK (height 163,299, 310.5 MH/s, 14 keys active, 12 voters, lock +8,910 at 80.3 percent) and the next tick read "0 due". Two webhooks now post to #network-feed: "Igneum" (numbers: +pulse, digest, weekly, hash-origin) and "Igneum feed" (the hour and milestones). + +What the numbers mean per tier (the consequences rule): 14 keys and 311 MH/s is the project's own machines on the +devnet, so the feed names no outside miner yet; a home miner with one 8 GB card at the measured untuned rates finds a +first block inside the hour at this size, and the Keys line is the one that tells them when that stops being true +(the pool is the answer from about 1 TH/s, reinvent.md 3.5). + +### 4.2 The ladder bot (a bot user; SPECIFIED, not built) + +What it posts, from ladder.md (the shapes are fixed there; the words are repeated here so this file stands alone): + +| Post | Channel | Trigger | Exact shape | +|---|---|---|---| +| First block (rung 0) | #first-block | a key's `blocks` goes 0 to 1 in `finality.weights.keys[]` and a block in `/api/live blocks[]` names it | "First block: key 6ad0e117" / "Block 1,284,117 · igneum.network/block/" / "RTX 4070 (the miner chose to show the card)". Without the opt-in the third line is absent. Embed: ember, title "First block", fields Key and Block, UK footer | +| The vote (rung 1) | #first-block | `keys[].voter` goes false to true | "Your key has a vote: 6ad0e117" / "100 blocks in the window (the line is 100) · the key now signs every checkpoint"; the number is `params.dust` as read | +| The ladder, yesterday | #network-feed | 09:00 UK beside the digest | the seven-line summary in ladder.md (first blocks, votes, signatures, full window, rank 1, signing streak, shards); a line whose field the node does not expose is left out | +| Roles | | daily read of `getFinalityWeights` through `/api/live` | Voter granted when a message signed with the vote key names a key whose `voter` is true; revoked at a daily read where `voter` is false. Window when `keys[].daysMined` spans the window (owed from the node; by hand until then). Prover when a paid shard record names the key; never revoked | + +Opt-in, per miner: the key id and the block link post for every key (a chain fact); the card model and the "(you)" +link only when the miner switched "Make my page public" on in the app (`settings.profile_public`). The Discord role +needs the miner to prove the key: a `/key ` slash command, the signature over a nonce the bot gives, +verified against `getFinalityWeights`; the app's "prove my key" button is owed (ladder.md). + +Permissions the bot user needs, minimal: View Channels; Send Messages and Embed Links in #first-block and #network-feed +only (channel overrides, not server-wide); Read Message History; Manage Roles, with the bot's role placed above Voter, +Window and Prover and below everything else; `applications.commands` scope for the slash command. Not: Administrator, +Mention Everyone, Manage Channels, Manage Webhooks, Moderate Members. + +Rungs 2 to 5 and P are never posted singly; they are counted in the daily summary (one a minute at scale). + +### 4.3 The two webhooks that exist and where they point + +| Key | Channel | Used by | +|---|---|---| +| DISCORD_WEBHOOK_NUMBERS | #network-feed (the channel was renamed; the webhook followed) | pulse, digest, weekly, the hash-origin report | +| DISCORD_WEBHOOK_ANNOUNCEMENTS | #releases (moved 7 Oct 2026, 13:13 UK; the webhook keeps its URL and name "Igneum") | release posts | +| DISCORD_WEBHOOK_INCIDENTS | #incidents | incident open and resolve, the watcher | +| DISCORD_WEBHOOK_UPDATES | #discord-updates (hidden) | the CI red watcher; the feed's proof post today (`feed --via updates`) | +| DISCORD_WEBHOOK_FEED | #network-feed, webhook "Igneum feed" (created 13:0x UK) | the hourly feed and milestones | + +## 5. Events + +One template, "Devnet office hour", weekly. Discord cannot hold an event without a start time, so nothing is created on the server until the founder picks a day and an hour; the fields below are the template, created in one minute on that day. + +| Field | Value | +|---|---| +| Name | Devnet office hour | +| Where | a voice channel "office-hour" under COMMUNITY, created with the first event (not before: no empty channels) | +| Description | "An hour on the devnet, every week. Bring the card, the log line or the question. Numbers from the public API only; nothing is for sale and there is no price." | +| Recurrence | weekly, same day and hour, UK time | +| Needs the founder | the day and the hour | + +## 6. What needs the founder + +| Item | Why | +|---|---| +| A day and an hour for the office hour | section 5; Discord has no undated event | +| 2FA on the founder account, then the "Require 2FA for moderator actions" switch | Discord greys the switch until the account has 2FA; one click after that | +| The hosting word for the ladder bot | a bot token with Manage Roles is a secret the box would hold; the 6 October exception covers webhook URLs only. Options: the box under a second exception, or a separate small host that holds only the bot token and reads the public API | +| A second account for the AutoMod test | the founder's account is Core-exempt; the seven rules are enabled but untested against a real message | + +## Changelog + +| When (UK) | What | +|---|---| +| 7 Oct 2026, 11:1x | Sheet opened on branch discord-structure. Chrome profile confirmed as the igneum.network login. Discord session found expired; stopped at the log-in form, nothing typed | +| 7 Oct 2026, 11:2x | `feed` subcommand, milestones, the daily hash-origin field, `--via updates`, `DISCORD_WEBHOOK_FEED` (optional) and the tick wiring added to tools/community/discord-hooks.mjs; six tests added, 37 pass | +| 7 Oct 2026, 11:30 | One live feed posted through the updates webhook: key `feed:2026-10-07:11`, message id 1557339585166581846, 413 characters | +| 7 Oct 2026, 12:5x | Founder signed in. Categories renamed INFO, CHAIN, LEDGER, TALK to START HERE, MINE, BUILD, COMMUNITY. #ask read (no messages beyond the welcome; the r/igneum FAQ line is in the support pins) and renamed to #off-topic; #finality read (no messages) and renamed to #first-block; #proving read (no messages) and renamed to #rig-photos; #devnet (no messages) renamed to #benchmarks; #breaks (no messages) renamed to #spec; #numbers renamed to #network-feed (both webhooks follow). Created #releases, #mod-log (private, Core), #support-windows, #support-mac, #support-linux-hiveos, #pools, #devnet, #proving, #node-runners; #dev moved to BUILD. Every topic and slowmode set; #first-block Send Messages denied, threads allowed; #network-feed Send Messages denied. The 0.3.15 and 0.3.16 posts and the two incidents stay where they were | +| 7 Oct 2026, 12:2x to 12:3x | 19 first posts sent from the founder's account and pinned: start-here (the welcome and ladder), releases, incidents, network-feed, mining, rig-photos, first-block, benchmarks, support-windows, support-mac, support-linux-hiveos (the FAQ, OS line first), pools, devnet, proving, node-runners, dev, spec, ledger, off-topic | +| 7 Oct 2026, 12:4x | AutoMod: seven rules enabled (section 2), prune restricted to admins, safety notifications to #mod-log | +| 7 Oct 2026, 12:5x | Onboarding: the five answers re-pointed, four to-dos rewritten, welcome sign rewritten; Server Rules screen on with four lines; Bot role set to View Channels, Send Messages, Embed Links, Attach Files, Read Message History (read back 13:1x UK: exactly those five on, 46 off) | +| 7 Oct 2026, 13:05 | Webhook "Igneum feed" created on #network-feed, key written, box installed; 13:06 the box's first hourly feed | +| 7 Oct 2026, 13:1x | Post 1's "How this channel works" line edited by webhook PATCH (message 1557154683779547138); the "Igneum" release webhook moved from #announcements to #releases (Channel settings, Integrations, Webhooks, Channel), read back from each webhook's own endpoint: announcements → 1557346271726141471 (#releases), numbers and feed → 1557089967807926322 (#network-feed) | diff --git a/docs/plans/build-server.md b/docs/plans/build-server.md index 06d5cd8b6..24c5ca04d 100644 --- a/docs/plans/build-server.md +++ b/docs/plans/build-server.md @@ -357,3 +357,23 @@ service. The layer tracks the repo branch `master`; until this work merges, the tree, so install writes a drop-in pinning `CAP_REPO_BRANCH=box-capacity` and removes it once `master` carries `infra/build-server/capacity/run.sh` (self-healing after the merge). `--no-start` enables without starting; `--smoke ` installs then runs one job's 10-minute smoke and prints the summary. + +## 7. Spill-over between the boxes (7 October 2026, 15:0x UK) + +the project lead's reading at 15:02 UK: build-1 at load 139 / 114 / 90 with both slots held and a queue (the horizon lane waited 1 h 40 min) +while build-2 read 4.5 / 27 / 46 with both slots free. The class router (section 6) pinned each class to its box with no +spill-over. Now (lib.sh `bs_route_spill`, master from this commit): + +- The class is a PREFERENCE: a build, check or gate prefers box 1, a suite, bench or attack row box 2, a proving crate box 3. +- Before a run, the preferred box is read with one ssh (free slots of its slot count, 1-minute load). It takes the job when it + has a free slot and its load is at or under 64 (`BS_SPILL_LOAD`). Otherwise the other box (1 and 2 swap; 3 falls to 1) takes it + when THAT one qualifies; when neither does, the job queues on its own box. A box without a host file is never chosen; an + unreachable box reads as "down" and is skipped. +- The decision is the first route line of the run ("route: class suite prefers box 2; box 2 (free=0 slots=3 load1=70) is full or + over load 64: spilled to box 1 (free=1 slots=2 load1=20)"), the slot label carries "; spilled from box N", and the JSONL row + carries `"route": {"preferred", "box", "spilled", "reason"}` for the dashboard's job card. +- build-2 has THREE slots (its `slots` file reads 3 since 14:0x UK; provision.sh defaults a `-2` hostname to 3). Everything that + lands on box 2 runs at the bounded class, nice 10 on a 32-core band with -j 32, builds and gates included, so a suite beside + them keeps its number; since this commit a bounded run takes the band its slot owns (slot 0 the last 32 cores, slot 1 the 32 + below, slot 2 the 32 below that), so three bounded runs never share a core. A gate still takes its slot ahead of queued suites. +- `--box N` still pins. Self-test: tools/ci/route-spill-check.sh (thirteen cases through `BS_ROUTE_STATE_`, no ssh), in the gate. diff --git a/docs/plans/counter-asic-3-gate/class-v4-20261006-rehearsal-PASS.json b/docs/plans/counter-asic-3-gate/class-v4-20261006-rehearsal-PASS.json new file mode 100644 index 000000000..84d8d87fd --- /dev/null +++ b/docs/plans/counter-asic-3-gate/class-v4-20261006-rehearsal-PASS.json @@ -0,0 +1,86 @@ +{ + "gate": "P1 rehearsal: the class v4 activation on a fleet of real boxes (Counter ASIC 3.0)", + "verdict": "PASS", + "date": "2026-10-06", + "network": "igneum-devnet-400 (fleet-only, from the devnet genesis state)", + "object": { + "file": "docs/plans/counter-asic-3-gate/override-v4-rehearsal-1bps.json", + "fields": 17, + "pow_epoch_blocks": 600, + "pow_epoch_lead": 100, + "program_class_v4_signal_window_daa": 600, + "program_class_v4_activation_daa": 2400, + "threshold_bps": 9500, + "consensus_digest_on_devnet_400": "a15db4f0d6a5cc891582760ef5593e69014a5133261def84647cb7617528764f" + }, + "binaries": { + "igneumd": "847ddfd1ba376009 (PC 2 job build-20261006-174823, the signalling fork 0562a7f2)", + "igneum-miner": "37178aeb09bc3a24", + "worker_first": "0.3.14 hive igneum-worker-cuda 1.0 (4 October): refused the generator-4 pack, the fleet stopped at the flip", + "worker_resume": "Linux generator-4 igneum-worker-cuda from the release tree 563485b, sha256 97e036e23f4ace66..., from 19:15:47Z" + }, + "boxes": { + "mining": 15, + "seed": 1, + "stale_old_binary": 1, + "wave_pods_joined_as_v4_miners": 37, + "signalling_nodes_with_the_flip_line": 52 + }, + "timeline_utc": { + "first_block": "18:41:10", + "flip_daa_1202": "19:00:5x", + "stall_at_flip_old_worker_s": 90, + "fleet_stopped_old_worker": "19:04:14", + "resume_new_worker": "19:15:47", + "floor_daa_2400": "19:33:2x", + "sweep": "19:34:54" + }, + "flip_line": "Program class v4 by miner signal: epoch 2 (share 10000 bps over 600 DAA ending at seed block f0606e203183798a728488ba8ce38ad5f552f53e3a7ac7b5e65d41c23fac5bf3, threshold 9500 bps, 599 of 599 blue blocks)", + "program_ids": { + "epoch_1_v3": "b237a661a3c7f7c1", + "epoch_2_v4": { + "pack": "24304f0788ea9408", + "cli_v4": "24304f0788ea9408", + "cli_v3": "d8927052c764f00b" + }, + "epoch_3_v4": { + "pack": "cc266b4f5dbc3447", + "cli_v4": "cc266b4f5dbc3447", + "cli_v3": "de3a34f1f2130228" + }, + "epoch_4_v4": { + "pack": "634018bab5e5f283", + "cli_v4": "634018bab5e5f283", + "cli_v3": "170e3aa4b2f69d60" + } + }, + "checks": { + "flip_by_signal_identical_line_on_every_node": true, + "one_program_id_per_epoch_across_boxes_equal_cli_v4_differs_v3": true, + "pow_rejected_on_every_node": 0, + "miner_mismatched": 0, + "blocks_on_v4_on_every_box": true, + "stale_box_refused_by_digest": { + "refusing_peer_lines": 11, + "digest_mismatch_lines": 22, + "ever_a_peer": false, + "old_digest": "507f802b" + }, + "stale_box_on_full_file": "refuses at parse (unknown field program_class_v4_activation_daa) and exits", + "floor_crossed_with_v4_in_force": true, + "sweep_19_34_54": { + "heights": "2502 to 2509", + "blue": "2432 to 2440", + "sinks_moving_with_height": 4, + "fork": false + }, + "g2_serve_mode_epoch_2_pack": { + "found": 1024, + "distinct": 1024, + "digest": "7bf77506546730973a708ebfcf7d1f908f58ff9687b529e9ccca1d022f81e3e6", + "mac_recheck": "MATCH 1024 of 1024" + } + }, + "cut_critical": "an old worker refuses a generator-4 pack by design, so publish 2 (the sixteen-field file) waits until every node AND every worker in the fleet is 0.3.15's; a 0.3.13 node given the file exits at parse; publish 1 carries no handshake split under the digest-compat rule", + "live_devnet_side_effect": "11 live miners at about half rate 18:42Z to 19:04Z (their GPUs shared with the rehearsal worker); no box left the live devnet" +} \ No newline at end of file diff --git a/docs/plans/counter-asic-3-public-text-2026-10-07.md b/docs/plans/counter-asic-3-public-text-2026-10-07.md new file mode 100644 index 000000000..c72a29649 --- /dev/null +++ b/docs/plans/counter-asic-3-public-text-2026-10-07.md @@ -0,0 +1,33 @@ +# The chip claim, public text (7 October 2026, 14:3x UK, on the project lead's "this needs updating with all of our updates"; served since 11:03 UK on master 9162c847 with main's two cuts: no mention of the disclosure prize until the publish word, and row 17 in evidence.md's eight-column shape) + +Three texts and one ledger row, written by the Counter ASIC lane, which owns the chip model. Every number carries its label: measured (a card or a chain we ran, with the date), modelled (arithmetic on cited parts), claimed (a vendor's figure, never measured by us), designed (a rule in a class, not yet measured). Sources: `docs/analysis/chip-model-v3.md` sections 5 and 6, `docs/analysis/latency-shadow-2026-10-06.md`, `docs/plans/counter-asic-3-status.md`, `docs/analysis/attack-pass/f8-uniform.md` and `f4-weakday.md` (branch attack-pass), `docs/design/class-v5-stored-state.md`, the datacentre and market-cap rows of 7 October (lanes 3 and the fleet), the cryptanalysis plan in `docs/plans/funding.md`. + +## 1. The home page's chip line (replaces the hero sentence served since 6 October 16:21Z) + +Built for graphics cards. In our public model the strongest chip reaches 5x to 9x per joule against an RTX 5090 today; class v4, now on the vote, brings that to 2.1x to 3.9x, and class v5 makes the dataset the chain's own state, so a chip that stores it or recomputes it is wrong on every item. The model and every measurement are public. + +## 2. The litepaper's chip section (replaces the paragraph that begins "The chip model: 5x to 9x per joule") + +The chip model. We price the strongest chip we can design against an RTX 5090 and publish the arithmetic. The honest card: an RTX 5090 mines class v3 at 136 MH/s on 350 W in the bench and 290 W in the app (measured, 6 October 2026); an Apple M5 Max at 27 MH/s on 21 W (measured, 6 October 2026); an H100 SXM at 249 MH/s, 98 percent of its random-read ceiling like the 5090, 1.78x the 5090's hash at 1.15x the tuned 5090's hash per watt and a third of the hash per rented dollar (measured, 7 October 2026), so datacentre silicon does not change the chip question. The CPU verifier takes 2.33 ms per warp of 32 hashes on one M5 Max core under class v4 (measured, 6 October 2026), against a gate of 10 ms. + +| The chip and the class | Edge over an RTX 5090 per joule | Label and date | +|---|---|---| +| A memory-controller chip that stores the whole dataset (the Ethash class), class v3 | 5x to 9x (5.1x on GDDR7, 9.2x on eight HBM3 stacks; the Ethash chips of this class reached 2.1x to 4.8x) | modelled, 6 October 2026; the precedent measured by others, 2020 to 2022 | +| The same chip under class v4 (about 100,000 integer ops per hash in the latency shadow, so the chip carries a GPU-class datapath beside its memory) | 2.1x with a core as costly per op as the GPU's (k = 1); 3.9x with the core Bitmain claimed for its Antminer X9 (k about 0.33), a product withdrawn before any unit shipped | modelled on measured card watts, 6 October 2026; the X9 figure claimed, never measured | +| The same chip at the ladder's second rung (about 200,000 ops per hash) | about 2.8x | modelled, 7 October 2026 | +| Any chip under class v5, where the dataset is the chain's own state | a stateless or stale chip is wrong on every item, so the stored-dataset chip and the recompute chip are removed as categories; the verifier pays 0.2 ms more per warp | designed, 7 October 2026 | +| A chip caching the hottest 0.1 percent of items (about 1 MB of SRAM) | bounded at 1.067x at the ceiling, 1.005x on about half the hours and 1.048x on 5 percent | measured census of 1,024 programs, 7 October 2026; the source rule in the next class | +| A per-day FPGA that recomputes the dataset with cheap multipliers on a weak day | at most 12 percent more hash rate on 12 days a century, nothing on the other days and nothing for any chip | measured census of 2^24 days, 7 October 2026; the rule in the next class | +| When a stored-dataset chip pays for itself | at about USD 100 M of market cap in the first two years, not before | modelled, 7 October 2026 | + +What a miner sees from this. Class v4 costs a 5090 about 80 W more for 0.2 percent of rate, an M5 Max 16 W more for 1.5 percent, an RX 9070 XT and an RTX 4070 nothing (all measured, 6 October 2026). The ladder that sets how much work rides in the shadow starts at rung 0 at the testnet genesis and climbs by miner signal; its third rung is inadmissible today because a server core verifies it in 10.85 ms, over the gate (measured, 7 October 2026). The next test of the model is not ours: the cryptanalysis plan buys three external lots against the mixer, the chained cache and the acceptance rule. + +## 3. The miner page's line + +Your card against the strongest chip we can price: an RTX 5090 at 136 MH/s on 350 W (measured 6 October 2026), the chip 5x to 9x per joule in the public model today, 2.1x to 3.9x under class v4 (modelled on measured watts), and under class v5 wrong on every item because the dataset is the chain's own state (designed); the model and the measurements are public. + +## 4. The ledger row (docs/evidence.md row 17, in the table's eight columns as served) + +| # | Claim | Where it is made | Status | Version or commit | Reproducible test | Result, date, machine | Independent verification | +|---|---|---|---|---|---|---|---| +| 17 | The chip resistance claim: the strongest chip in the public model reaches 5x to 9x per joule against an RTX 5090 today; class v4 brings it to 2.1x (k = 1) to 3.9x (k about 0.33) and its second rung to about 2.8x; class v5 makes the dataset the chain's state so a stateless or stale chip is wrong on every item; the hot-set cache is bounded at 1.067x at the ceiling and the weak-day FPGA at 12 percent on 12 days a century, both routed to the next class; datacentre silicon does not change the question; a stored-dataset chip pays for itself only at about USD 100 M of market cap in two years | the home page's chip line, the litepaper's chip section (/litepaper#chip-model), the miner page's line | tested by the team (every card, the verifier, the two attack-pass bounds, the H100), the chip itself modelled, class v5 and the ladder designed, the X9 core claimed and never measured | `docs/analysis/chip-model-v3.md` 5 and 6; `docs/analysis/latency-shadow-2026-10-06.md`; `docs/plans/counter-asic-3-status.md`; `docs/analysis/attack-pass/f8-uniform.md`, `f4-weakday.md`, `docs/analysis/ca3-v4-uniform.md`; `docs/design/class-v5-stored-state.md`; the H100 and market-cap rows of 7 October; `docs/plans/funding.md` (the three lots) | the chip model's arithmetic in its file; the card rows by the benchmark package; the attack-pass harnesses `tools/attack/f8-uniform` and the F4 census; the verifier by `igneum-pow bench` | 136 MH/s at 350 W (5090, bench) and 290 W (app); 27 MH/s at 21 W (M5 Max); 249 MH/s (H100 SXM) at 98 percent of its read ceiling, 1.78x hash, 1.15x MH/W, a third per rented dollar; 2.33 ms per warp; 5.1x to 9.2x; 2.1x, 3.9x, 2.8x; 1.067x at the ceiling; 12 percent on 12 days a century; 10.85 ms at rung 3; USD 100 M; 6 and 7 October 2026, the M5 Max, PC 2's RTX 5090, PC 1's RX 9070 XT and RTX 4070, a rented H100 SXM, igneum-build-1 | none yet; the three cryptanalysis lots are the next test | diff --git a/docs/plans/counter-asic-3-status.md b/docs/plans/counter-asic-3-status.md index 6ba33681e..6158ed191 100644 --- a/docs/plans/counter-asic-3-status.md +++ b/docs/plans/counter-asic-3-status.md @@ -84,7 +84,9 @@ Consequence per tier (interim): the M5 Max at 21 W is the per-joule best honest | 199,600 | 24.25 (-10.4%) | 38.2, 1.58 | 128.67 (-2.7%) | 431, 1,753, 3.35 | 2.43 | | 330,700 | 21.39 (-21%) | 40.1, 1.88 | 86.39 (-35%, compute-bound at the capped clock, 28.6 T op/s) | 431, 1,834, 4.99 | 2.62 (worst cold 2.77) | -Where each card leaves the latency bound (the 5 percent rule): M5 Max about 130,000 ops; RTX 5090 about 210,000 at its 431 W cap (the cap binds from 102,100 ops and the governor lowers the clock); RX 9070 XT OWED. The verifier's law: 2.06 ms + 3.2 microseconds per 1,000 shadow instructions per warp, so 330,700 ops add 0.56 ms (about 1.4 ms on a 2019-class core): it fits every pairing's headroom (x8 7.8 / 4.6 ms, dr368 7.1 / 2.8, dr736 5.1 / none), and the node never binds before the cards. Marginal ALU energy per counted op: the 5090 10 to 13 pJ at its shipping clock (twice the 5.5 pJ the item 1 model assumed), the M5 Max 6.9 pJ. Power caps: `-pl` below 400 W cannot be set, the 5 October sweep rows re-used (302 to 316 W at every cap); the clock rows are OWED (nvidia-smi refused `-lgc` without rights; the job did not ask; an elevated job is a decision for the project lead, section 6). Item 1's denominator: the 5090 at the hash is 290 W in the app and 350 W in the bench, not 326; the f = 1 rows move 2 to 11 percent. +Where each card leaves the latency bound (the 5 percent rule): M5 Max about 130,000 ops; RTX 5090 about 210,000 at its 431 W cap (the cap binds from 102,100 ops and the governor lowers the clock); RX 9070 XT OWED. The verifier's law: 2.06 ms + 3.2 microseconds per 1,000 shadow instructions per warp, so 330,700 ops add 0.56 ms (about 1.4 ms on a 2019-class core): it fits every pairing's headroom (x8 7.8 / 4.6 ms, dr368 7.1 / 2.8, dr736 5.1 / none), and the node never binds before the cards. The verifier on a SLOWER core, measured 7 October 08:46 UK by the node lane on igneum-build-1 (an EPYC 9454P core at 3.66 GHz under schedutil, the measure hold, load 6.1; the ladder worktree's igneum-pow 59ae70cf; 50 warps averaged, the cold warp beside it) for the testnet's latency ladder (its rungs are item 8's shadow packs): rung 2 = 199,566 counted ops (the sh256x53 pack) 8.99 ms loaded (9.25 cold), ADMISSIBLE under the 10 ms gate; rung 3 = 330,740 ops (sh256x88) 5.95 ms alone (9.04 cold), 10.11 ms with the sibling loaded (10.85 cold), OVER the gate by 0.85 ms, so the testnet freezes that rung FALSE. Reading against the M5 Max's law (2.06 ms + 3.2 microseconds per 1,000 shadow instructions: 2.62 ms at 330,700): the server core is 2.3x slower alone and 3.9x loaded, so the 2.5x rule's "about 6.5 ms" for a slower core was right alone and short under load; the candidate at 100,000 ops sits well inside the gate on this core by the same ratios (about 5.3 ms loaded, approximate, not measured), and the 2019-class laptop core (O-1.14) stays the owed row. Consequence per tier: a pool core or a node on a server-class CPU verifies the candidate class inside the gate with room; the ladder's top rung is out for any core slower than an M5 Max under load, which is why the testnet ships it false. + +Marginal ALU energy per counted op: the 5090 10 to 13 pJ at its shipping clock (twice the 5.5 pJ the item 1 model assumed), the M5 Max 6.9 pJ. Power caps: `-pl` below 400 W cannot be set, the 5 October sweep rows re-used (302 to 316 W at every cap); the clock rows are OWED (nvidia-smi refused `-lgc` without rights; the job did not ask; an elevated job is a decision for the project lead, section 6). Item 1's denominator: the 5090 at the hash is 290 W in the app and 350 W in the bench, not 326; the f = 1 rows move 2 to 11 percent. Chip side (approximate: the f = 1 stored-dataset chip of item 1 plus an ALU core at k times the 5090's measured 11 pJ per op): at N = 100,000 its per-joule edge over the 5090 falls from 5.6x (shadow empty, 350 W) to 2.1x on GDDR7 and 2.3x on one HBM3 stack at k = 1, 1.5x at k = 1.5, 3.2x at k = 0.5, 4.1x at k = 0.3; over the M5 Max from 1.6x to 0.9x at k = 1. The chip needs a 14,000-lane ALU array (about 30 mm^2 at N5, 150 W at k = 1) at 100,000 ops and 22,600 lanes (60 to 100 mm^2, 500 W) at 331,000; at 28 nm the array is reticle-class. That is the project lead's test as a number: with the shadow filled the chip must carry the memory system and a GPU-class datapath, and its edge is the ratio k of its datapath's energy per op to the GPU's. @@ -226,12 +228,12 @@ Two preconditions on the cut, from main (17:0x UTC, both from today's incident), | # | Precondition | What passes it | State | |---|---|---|---| -| P1 | The cut rehearses first on the rented fleet as a staging network (the fleet agent owns the boxes; the node lane supplies the v4 override object and the rehearsal plan `docs/plans/counter-asic-3-rehearsal.md`) | a fleet-only chain crosses the v4 activation with every box switched: zero rejected blocks, blocks on both sides, the G4 id assertion live on every box, one sink, one digest; the stale-box case refused at the handshake with no fork | PLAN WRITTEN (ca3-v4-node f39a8eb, merged): fleet-only chain igneum-devnet-400 from its own genesis state, 12 or more mining boxes, a seed box, one stale 0.3.13 box; the signal flip at DAA 7,200 (the first full 3,600-DAA window) with the floor at 14,400 not reached; ten steps, the report fields and pass rules; the id assertion from the boxes' miner lines. Two objects as files in `docs/plans/counter-asic-3-gate/`: the publish object (the live 13 fields plus `program_class_v4_activation_daa` = N6, the floor, tip + 14,400 rounded up, 219,600 at the 16:57Z DAA of 202,919, and `program_class_v4_signal_window_daa` = 86,400; digest ac8e60ce...) and the rehearsal object (every earlier switch at 0, window 3,600, floor 14,400; digest bc2142b1...); the no-file devnet digest on this binary 7f2e49be... (3c505021 superseded: the window field joined the digest). THE RUN ITSELF IS OPEN: the fleet agent runs it; no live-devnet date until it passes | +| P1 | The cut rehearses first on the rented fleet as a staging network (the fleet agent owns the boxes; the node lane supplies the v4 override object and the rehearsal plan `docs/plans/counter-asic-3-rehearsal.md`) | a fleet-only chain crosses the v4 activation with every box switched: zero rejected blocks, blocks on both sides, the G4 id assertion live on every box, one sink, one digest; the stale-box case refused at the handshake with no fork | PASSED 19:33Z (the run's record in section 5a's P1 cell below the table and `docs/plans/counter-asic-3-rehearsal.md`). PLAN WRITTEN (ca3-v4-node f39a8eb, merged): fleet-only chain igneum-devnet-400 from its own genesis state, 12 or more mining boxes, a seed box, one stale 0.3.13 box; the signal flip at DAA 7,200 (the first full 3,600-DAA window) with the floor at 14,400 not reached; ten steps, the report fields and pass rules; the id assertion from the boxes' miner lines. Two objects as files in `docs/plans/counter-asic-3-gate/`: the publish object (the live 13 fields plus `program_class_v4_activation_daa` = N6, the floor, tip + 14,400 rounded up, 219,600 at the 16:57Z DAA of 202,919, and `program_class_v4_signal_window_daa` = 86,400; digest ac8e60ce...) and the rehearsal object (every earlier switch at 0, window 3,600, floor 14,400; digest bc2142b1...); the no-file devnet digest on this binary 7f2e49be... (3c505021 superseded: the window field joined the digest). THE RUN STARTED 18:22Z (the fleet agent): igneum-devnet-400 from the devnet genesis with the re-cut 1-block/s object `override-v4-rehearsal-1bps.json` (600-DAA epochs, lead 100, window 600, the flip at epoch 2 = DAA 1,200, the floor at 2,400; node digest d23394e7...; the file written byte for byte on every box) and the signalling fork's Linux binaries from PC 2 job build-20261006-174823 (igneumd 847ddfd1..., igneum-miner 37178aeb..., verified on the Mac and every box); the seed on the RunPod pod dn2-seed (public p2p 213.173.110.229:11927, no miner); 15 mining boxes beside their live-devnet nodes on separate ports with fresh appdirs and 1-thread CPU miners (dn2-1, dn2-2, dn2-3, hub-1, 3080, 4070, 4090, 5090, A5000, 3090-2, 3090-3, 4070-1, 4090-1b, 4090-3, the 8x 4090 rig); the stale box p2-3090-4 on 0.3.13's igneumd d6350586 with the same file and no miner, started last; the 38 wave pods join about 18:50Z. The clock from the seed's genesis at about 18:23Z: the window full 18:41Z, the flip about 18:43Z, the floor about 19:03Z (run to the floor so its line is exercised). A sampler on every box every 5 minutes; the id lines go to the node lane for the CLI check; the report in section 4's table plus rehearsal-