Settings
the operator panel.
Settings is Token Forge's operator panel. There is no login and no server: it edits the settings of the install you are running. This page goes through every section in the order the screen shows them.
01Day-one order
- Your RPC endpoints: add your own devnet endpoint.
- Branding and support: your brand name and links.
- Jobs your team can pick and Vocabulary: fit the forge to your business.
- Effective configuration: check for problems.
- Only when you are ready for real tokens: Network → Allow mainnet.
Anyone who can open the app can open Settings; there are no roles or passwords. Treat a deployed build like a tool on your own machine, and host a web build only where your team can reach it. The forge holds no key, so Settings can never move funds.
02Network
Devnet / Mainnet chooses the cluster for every later call: reads, simulations, rent quotes and explorer links. The choice is saved as the default cluster. The same choice is on the cluster chip in the header.
Allow mainnet is off by default. While it is off, mainnet cannot be selected anywhere and the app starts on devnet. Turning it off again switches the app back to devnet.
On mainnet a transaction is offered for signing only after a preflight simulation against mainnet has run and succeeded. Still: make every token on devnet first.
03Your RPC endpoints
Set the devnet endpoint, Set the mainnet endpoint, then Save endpoints. Both are validated before either is saved: https:// only, except localhost / 127.0.0.1 for a local validator. Clear removes both and the app falls back to the public endpoint, and says so.
Devnet, in use and Mainnet, in use show the endpoint with its path and query hidden. Two banners can appear here: Public endpoint in use (no endpoint of your own for this cluster) and Keystore unavailable (the OS store could not be read, see Troubleshooting). Setup steps: Installation.
04Transactions
| Setting | Default | Effect |
|---|---|---|
| Priority fee, micro-lamports per compute unit | 0 | Added to every transaction as SetComputeUnitPrice when above zero. Up to 1,000,000. The panel shows what it costs in SOL at the default 200,000-unit limit. |
| Compute units requested | 200,000 | Added as SetComputeUnitLimit. Up to 1,400,000. Raise it if the cluster rejects a mint with a long metadata URI or many custom fields for lack of compute. |
Both show up in the numbered instruction list on the review step, because that list is built from the same values.
05Jobs your team can pick
Seven checkboxes, one per preset: Membership, Licence, Loyalty points, API credits, Pass / ticket, Reward token, Whitelist token. They control which cards step 1 of the build offers. At least one must stay on. A gym that only issues memberships can hide the rest.
06Vocabulary
Preset chips (Plain, Points, Credits, Licences, Memberships, Passes) and a field for each word the product uses, such as holder, holders, unit, units, the issue verb, the revoke verb, the supply label and the expiry noun. Changing them changes labels only. test/vocabulary_changes_no_number_test.dart renders every figure under every preset and requires identical numbers.
07Branding and support
Brand name (shown in the header, under 60 characters), Support email, Website, Documentation URL, Terms URL. Each field says what is wrong if the value is not valid. In this version only the brand name appears outside Settings; the four links are stored and listed in Effective configuration. The app name under the icon and in the browser tab is set at build time; see Rebranding.
08Maintenance mode
A switch and a Message. When it is on, the whole app, Settings included, is replaced by This instance is closed and your message. The switch refuses to turn on while the message is empty.
Because Settings is hidden too, maintenance mode cannot be switched off from inside the same install. The closed screen has no button to re-pull a published config either. The way back is to clear the app's stored data: on the web, clear site data for the forge's address in the browser; on other platforms, remove and reinstall the app. Clearing resets all settings, the venue checks and the local audit trail (export the audit CSV first). Your keystore endpoints are separate and may remain. Test this on devnet before relying on it.
09Published configuration
Config URL (must be https://), Pull it now (fetch and apply, then report problems in what arrived) and Remember it (save the URL without pulling). Last pulled and From show the latest pull. A pull replaces the whole settings document; fields missing from the file return to defaults. File format: Configuration.
10Venue-check register
Your own record of how a wallet, exchange or aggregator treated your token when you tried it. Record a check: venue (as you name it), surface, outcome, cluster, the mint you checked against, and what you saw. Each check is dated on save. Edit re-dates it (an edited check is a new claim), Remove deletes it, Export CSV takes it away.
Recorded checks appear beside the unverified lines on the consequences step and in the console's Compatibility tab. After 90 days a check is marked for rechecking. The product ships with no venue names in any finding (test/venue_checks_test.dart).
11Effective configuration
Every value the app is running on, with its origin (default, set here or published config), plus product, version, token program and Keys held by this app: none. It lists any problem in the whole config, including settings that contradict each other. Copy it out opens the values as copyable text, each with its origin, for a support request. Your keystore endpoints are left out of it.