igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Discord structure built on the server and read back: channel map, pins, AutoMod, rules screen, onboarding, the hourly feed webhook live from the box (7 October 2026, 13:1x UK)

Browse source 
structure.md: every row flipped from waiting to "set, read back" with what the server holds now; the seven AutoMod
rules as built with their word lists; the onboarding answers and to-dos as built; DISCORD_WEBHOOK_FEED created and
installed on the box (first hourly post feed:2026-10-07:13 at 13:06 UK); what still needs the founder (an office-hour
time, 2FA on the account for the moderator switch, the ladder bot's host, a second account for the AutoMod test).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-josh 2026-10-07 13:09:50 +01:00
parent c8bffdea23
commit 6de09994cb
1 changed files with 76 additions and 61 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

137
docs/community/discord/structure.md
View file

@ -8,14 +8,17 @@ from the server after the change. Nothing is posted that names a number our file
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, 11:4x UK
## 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 |
| Discord session | expired. discord.com shows the account chooser with "igneum_network: Please log in again"; the Log in button opens the email and password form. Nothing was typed (rule: never a password, a code or an email code). the founder signs in himself, then every row below is built and read back in one pass |
| Network feed, webhook-only | built and posted once: `feed:2026-10-07:11`, 413 characters, message id 1557339585166581846, through DISCORD_WEBHOOK_UPDATES (`feed --via updates --live`). The hourly schedule starts on the box when `DISCORD_WEBHOOK_FEED` lands in `/srv/discord-hooks/env` (section 4) |
| Every other row | waiting on the sign-in; the words, settings and order are fixed here so the pass is mechanical |
| 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 #announcements post 1 line edit (a webhook message: edit by API with the announcements webhook, message id needed), the office-hour event (Discord has no undated event; the template is section 5, created the day a time is picked) |
## 1. Channel map
@ -40,54 +43,54 @@ message, posted from the founder's account (the webhook posts only the bot's num
| 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 | waiting |
| #rules | Three rules. Read once. | the rules post (section 2.6, the same words as the rules screen) | read-only | waiting |
| #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 | waiting |
| #releases | One post per release: version, downloads, sha256, what changed. The app updates itself. | "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 | waiting |
| #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 | waiting |
| #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. | "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 | waiting |
| #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 | waiting |
| #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) | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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) | waiting; the feed's words are proven (status) |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #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 | waiting |
| #off-topic | Not Igneum. GPUs, games, the weather. | "Anything but Igneum and anything but prices. Same three rules." | slowmode 10 s | waiting |
| #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 | waiting |
| #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,
@ -125,31 +128,31 @@ Ask here with the card, the OS and the app version. Nobody from Igneum will DM y
| Setting | Value | Where | Set / read back |
|---|---|---|---|
| Verification level | Medium (registered on Discord for longer than 5 minutes) | Server Settings, Moderation | waiting |
| Explicit image filter | Filter messages from all members | Server Settings, Moderation | waiting |
| 2FA requirement for moderation | on | Server Settings, Moderation (needs the founder account's 2FA, which it has) | waiting |
| @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 | waiting |
| 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 | waiting |
| #mod-log | private channel, Founder and Core; the alert channel of every AutoMod rule | Channel create | waiting |
| Rules screen | Membership screening on, the rules text in 2.6 | Server Settings, Safety Setup, Rules Screening | waiting |
| DM spam | Server Settings, Safety Setup, "DM and spam protection": Raid protection on, Activity alerts on | | waiting |
| 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 (Server Settings, AutoMod)
### 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 allows six custom keyword rules plus its own presets. Every rule: Block message, Send alert to #mod-log.
Exempt roles: Founder, Core. Exempt channels: #mod-log, #discord-updates.
Discord's keyword rule takes words and wildcards; the regex field was not needed. Seven rules are live:
| # | Rule | Trigger (keywords use Discord's wildcards; regex is Rust-flavoured, under 260 characters) | Action |
|---|---|---|---|
| 1 | Seed phrases and wallet scams | keywords: `seed phrase`, `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`; regex: `(?i)\b(seed|recovery|secret)\s*(phrase|words)\b` | block, alert, time out 10 minutes |
| 2 | Invite links | regex: `(?i)(discord\.gg|discord(app)?\.com/invite|discord\.com/invite)/\S+` | block, alert (Core exempt) |
| 3 | Spam links | regex: `(?i)https?://\S*\.(xyz|top|click|buzz|icu|monster|rest)\b`, `(?i)\b(t\.me|wa\.me|bit\.ly|tinyurl\.com|cutt\.ly)/\S+`; plus Discord's preset "Block suspected spam content" and "Block mention spam" at 5 mentions | block, alert |
| 4 | Price pumping | keywords: `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` | alert only, no block (a miner asking is a conversation; a mod answers with the pin: there is no market and nothing is for sale) |
| 5 | Impersonation of the team | keywords in messages: `igneum team`, `igneum support`, `official igneum`, `igneum admin`, `igneum mod`, `igneum staff`, `from igneum`; member-profile rule (AutoMod "Block words in member profiles"): `igneum`, `admin`, `mod`, `support`, `team`, `official` in display names (Core exempt; the founder's account is named by the server, not by these words) | block, alert; profile rule: block the profile update and alert |
| 6 | Explicit content | Discord's preset keyword lists: Profanity, Sexual content, Slurs and hate speech, all on | block, alert |
| # | 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 |
Read-back for each rule: the rule listed as Enabled, a test message from a non-Core account blocked (the alert in
#mod-log), and one legitimate message passing (a payout address, a sha256, a hash rate "2x per joule").
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)
@ -177,7 +180,7 @@ Report a flaw: hello@igneum.network or an issue on the spec. Nobody from Igneum
| 4 | Post your first block when it lands | #first-block |
| 5 | Follow releases | #releases |
Welcome sign stays; the guide banner is the one in README.md.
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)
@ -191,8 +194,7 @@ Question "What do you mine with?" stays. Answers and what each hands out:
| I run a node | Node runner | #node-runners, #devnet |
| I build | Builder | #dev, #spec, #proving |
Multiple answers allowed, not required. Default channels (everyone, no question): #start-here, #rules,
#announcements, #releases, #network-feed, #general.
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)
@ -227,7 +229,7 @@ Two bots. Neither replies, neither mentions, both post from the public API only,
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, the hourly schedule waits on one key)
### 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,
@ -249,10 +251,18 @@ devnet, so the feed names no outside miner yet; a home miner with one 8 GB card
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).
To turn the hour on: add `DISCORD_WEBHOOK_FEED=<the #network-feed webhook>` to `~/.config/igneum/discord`, then
`IGNEUM_SECRET_ON_BOX_OK=1 infra/build-server/discord-hooks/install.sh` (copies the script and the file to the box;
the tick posts the next hour). Until the key exists the tick logs "feed off (no DISCORD_WEBHOOK_FEED)" once a minute
and posts nothing. The box's copy of the script is the 6 October one until install.sh runs.
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)
@ -289,7 +299,7 @@ Rungs 2 to 5 and P are never posted singly; they are counted in the daily summar
## 5. Events
One template, "Devnet office hour", weekly, unscheduled until the founder picks a time.
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 |
|---|---|
@ -303,10 +313,10 @@ One template, "Devnet office hour", weekly, unscheduled until the founder picks
| Item | Why |
|---|---|
| Sign in to Discord in the Igneum Chrome profile | the session expired; this lane never types a password or a code. After the sign-in every row above is built and read back in one pass and this file's states flip |
| A day and an hour for the office hour | section 5 |
| 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 |
| The webhook for #network-feed | made in Discord after the sign-in (one minute); then the key and `install.sh` (section 4.1). Until then the hour is off and the proof post sits in the hidden channel |
| 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
@ -315,3 +325,8 @@ One template, "Devnet office hour", weekly, unscheduled until the founder picks
| 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 |