AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Set up a Gonka node without the command line, and see how your node and the whole network are doing.
Developer toolsJavaScript · CSSGitHub @gonkanetworkonboardinghubOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The Gonka Network Onboarding Tool (GNOT): source available for review. Official builds: github.com/gonkanetworkonboardinghub/gonka-host-setup
Taken from the repository README
Loading the full README.
Read the full README ↗The source code of GNOT, the free Windows and Mac app from The Gonka Network Onboarding Hub that makes taking part in the Gonka network easier.
Source available for review. This code is public so anyone can read it and verify what the app does. It is not open source: all rights are reserved. See LICENSE.
Install it from the Download page. Official builds, their checksums and the install scripts live in gonkanetworkonboardinghub/gonka-host-setup.
GNOT opens on a home screen of tools:
Good places to start reading:
| What | Where |
|---|---|
| Your wallet | src/services/wallet.js, src/services/keys.js |
| Commands run on your server | src/services/scan.js, src/services/fixes.js, src/services/deploy.js, src/services/mynode.js |
| Network facts and endpoints | src/knowledge.js, src/services/netdata.js |
| Updates | src/update.js, src/updater.js |
| Install commands | scripts/install.ps1, scripts/install.sh |
The short version:
The wallet is created and used only on your own computer, never on your
server. Keys are kept in the same encrypted file-keyring format as Gonka's
official inferenced tool, protected by your passphrase. The 24-word
recovery phrase is shown once and never written to disk. Transactions are
signed locally and sent to Gonka network nodes.
Everything the app runs on your server goes over your SSH connection.
The setup's commands appear in the Activity log; Monitor/Vote runs only the
ones you type and the shutdown steps in src/services/mynode.js. Server
passwords and key passphrases are never saved.
No accounts and no tracking. The app talks to Gonka network nodes,
GitHub (the update manifest, releases, Gonka's official repository for
supported configurations, and this repository's data branch for the
network's figures), GitHub Container Registry (to check node images),
four public GNK price sources for "Mine it or buy it?" (GeckoTerminal,
DEX Screener, CoinGecko, CoinPaprika), your own server — and The Gonka
Network Onboarding Hub's website, at most once an hour while it is open, to
say it was opened: a random number made for that computer, the app's version
and whether it is Windows or Mac, nothing else (src/services/usage.js).
That is how the website counts the computers that use the app; the app says
so on its first screen.
One public note on the chain. The transactions your wallet signs in the
app (the permission grant, and the registration or collateral deposit when
the app sends them) carry the memo Set up with GNOT v<version>
(GNOT_MEMO in src/services/keys.js). It says nothing about you. It exists
so anyone can count the nodes GNOT has helped bring into the network, straight
from the chain: scripts/onboarded-snapshot.js finds those transactions and
publishes the count per epoch, with every transaction hash as proof. A vote
cast from Monitor/Vote carries Voted with GNOT v<version> instead, and is
not counted.
Updates and installs are verified. The app and both install scripts
check each download's SHA-256 against manifest.json before running it.
Every published build is signed by GitHub as coming from this source.
The builds are made by this repository's own workflow
(.github/workflows/build.yml), and GitHub attaches a signed record of the
repository, workflow and commit each file came from. Anyone can check a file
they downloaded, without trusting us:
gh attestation verify Gonka-Network-Onboarding-Tool.exe --repo gonkanetworkonboardinghub/gonka-network-onboarding-tool
Requires Node.js 20 or newer.
npm ci
npm start # run the app from source
npx electron-builder --win # Windows installer into dist/ (use --mac on a Mac)
Builds you make yourself won't be byte-identical to the official ones (installers contain timestamps), but running from source lets you see exactly what the code does.
scripts/release.js sets the version and pushes a version tag. The tag
triggers .github/workflows/build.yml in this repository, which builds both
platforms on GitHub's machines and tests them: the wallet against the
official tool, the install scripts, the in-app updater, and updating from an
older version. Its logs are public in the Actions tab. GitHub signs each
file it built, and release.js downloads those exact files — so what people
install is what the public workflow made, not a copy from a laptop.scripts/publish.js checks every build's GitHub signature and SHA-256,
uploads them to the releases repository, and updates manifest.json last, so
a release only goes live once every file is in place and verified.main.js, preload.js Electron main process and the bridge to the UI
renderer/ The interface (home screen, Gonka Host Setup, 11 languages)
src/knowledge.js Gonka network facts, overridable from manifest.json
src/executor/ Local and SSH command runners
src/services/ Health check, fixes, deployment, wallet, network data
src/update.js Is this copy up to date?
src/updater.js Download, verify and install an update
scripts/ Release, publish and install scripts
.github/workflows/ Build and test (build.yml), app screenshots
website/README.md README of the public releases repository
Copyright (c) 2026 The Gonka Network Onboarding Hub. All rights reserved. See LICENSE.
scripts/publish.js runs the same check before it publishes anything, so a
build made on somebody's laptop cannot reach a release.
Known holes are checked every week. .github/workflows/security.yml
fails if the Electron version the app ships stopped getting security fixes or
is behind on patches (scripts/check-electron.js), or if any package the app
ships has a known serious hole. scripts/release.js runs the Electron check
too, so a release can't quietly go out on an unsupported version.