Developers
+Qortium Core inspection and settings through Qortium Home.
+{copied === 'unavailable' ? 'Clipboard unavailable. Select the code and copy it manually.' : copied ? `Copied ${copied} example.` : 'Code examples can be selected for manual copying.'}
+Host and authority
+Node is a Qortium-only app published as APP/Node/Node. It inspects the active Qortium Core route selected in Home; it is not a Qortal node manager. The public app bundle and this reference contain no live node settings, credentials or wallet data.
Use SHOW_ACTIONS and IS_USING_PUBLIC_NODE to discover the current host. Node’s write UI requires an update action, a node not reported as public, and writable metadata for each app-allowed field. An unknown public-node flag is not authority: Home independently requires a trusted local or authenticated route and a per-request approval. Switching node or API-key trust while approving invalidates the write.
Home owns the connection and credentials. Apps must not ask users to paste API keys or private keys, embed them in QDN assets, or use a direct browser request to bypass Home approval. Viewing Developers or copying examples performs no settings mutation or restart.
+The standalone development adapter reads http://127.0.0.1:24891 (configurable at build time with VITE_QORTIUM_NODE_API_URL). It permits GET/HEAD and does not advertise update/restart actions. The reference remains available when Core is offline. A developer browser fallback is not an authenticated admin route.
Status and peers
+GET_NODE_STATUS returns a direct status object, with optional sync phase/percent, height/target/remaining blocks, minting possibility, connection counts and reachability fields. Missing fields stay unknown. FETCH_NODE_API returns an envelope with ok, HTTP status, contentType, body and parsed data. Node accepts direct objects from older adapters too; independent consumers should check response success and validate data before use.
- {NODE_READ_PATHS.map(([path, meaning]) =>
{path}- {meaning}
Chain peers and QDN/data peers are separate connections, with IP/I2P and inbound/outbound breakdowns. Node IDs can overlap between the two networks: a connection count is not a unique-node count. Diagnostic availability, backoff, connectability and an I2P session being up describe different conditions; none alone proves end-to-end QDN transfer. Peer addresses, IDs and settings may identify a device: inspect before sharing a diagnostic export.
+Refresh loads a new snapshot. Optional reads can fail independently and fall back to empty/unknown displays; that is not proof the corresponding node data is empty. Node does not publish these reads to QDN. /admin/settings describes the current loaded settings object. Core reloads this object on save; its values do not prove restart-dependent services have adopted the change. Metadata can report differences between the file and that object.
Settings and units
+GET_NODE_SETTINGS_METADATA is preferred; Node also attempts the read-only metadata path when unavailable. normalizeSettingsMetadata supports a plain writable map or JAXB writable.entry records. A top-level writable array is not supported by Node’s current normalizer. Missing or malformed writable metadata leaves fields read-only. Metadata includes per-field type/restartRequired, and may include pendingRestart, fileChanged, fileDiffersFromRuntime and fileComparisonError. Do not depend on a local settings-file path being exposed.
Current app allowlist ({PHASE_1_EDITABLE_SETTING_KEYS.length} fields, in the existing settings order):
+- {PHASE_1_EDITABLE_SETTING_KEYS.map(key =>
{key})}
Core adding a writable key does not automatically expose it in Node. Conversely, being in this allowlist does not make a field writable on every node. Keep editor defaults, validation and ordering consistent when intentionally adding a field.
+-
+
- Storage / retention
maxStorageCapacitydisplays decimal GB ({STORAGE_CAPACITY_GIGABYTE_BYTES.toLocaleString('en-US')} bytes/GB);chatMessageRetentionPerioddisplays hours ({CHAT_RETENTION_HOUR_MS.toLocaleString('en-US')} ms/hour). The current editor accepts at least 1 GB or 1 hour, with up to three decimal places; conversion rounds to safe integer native units. Invalid input does not enter the patch.
+ - Numeric / version fields
- Ports are integers from 1 to 65535. Peer limits are positive integers except minOutboundPeers, which permits zero. The minimum version uses three numeric components, each from 0 to 32767. Core remains the final validator. +
- Enums
- Storage: {STORAGE_POLICY_OPTIONS.join(', ')}. Auto update: {AUTO_UPDATE_MODE_OPTIONS.join(', ')}. Transport selections: {TRANSPORT_SELECTION_OPTIONS.map(x => x.label).join(', ')}. Transport order is not a distinct UI choice; legacy reversed arrays normalize to the combined option. +
relayModeEnabled is intentionally absent: Qortium relays QDN whenever QDN is enabled. Retention policy, capacity, public/private data and push-on-publish remain separate controls. The reference does not add new settings permissions.
Save and restart
+Discover {SETTINGS_BRIDGE_ACTIONS.map((action, i) => {i ? ', ' : ''}{action})} independently. Node sends only changed, valid fields as {'{ action: "UPDATE_NODE_SETTINGS", settings: patch }'}. Home 2 also accepts patch/payload aliases, validates the writable keys before prompting and shows the selected node with current/proposed values. A single request is limited to 64 settings, with key lengths up to 120 characters and bounded display values.
Approval belongs to Home and each request. The response exposes saved and key lists applied, updated, removed, restartRequired; Home 2 removes filesystem paths from the update result. Save is distinct from applying a restart-required value. Re-read both settings and metadata; file comparisons can fail independently.
Current Core retains a pendingRestart marker after a saved value is reverted to its original value. Check fileChanged and fileDiffersFromRuntime separately: these compare the file with the loaded settings object, not every service’s effective configuration. Neither a marker nor an empty file comparison alone proves whether a service needs restart. Node builds patches against its last settings snapshot; Refresh explicitly reloads that snapshot and clears the draft. Do not restart automatically.
There is no expectedRevision contract here. Do not silently retry writes after timeout/disconnection; the change may already have reached Core. Refresh and review the actual state. Denial keeps the draft available. A successful save or explicit Refresh resets Node’s draft; switching tabs and Back/Forward preserves it.
RESTART_NODE is a separate explicit request with its own approval. It acknowledges a restart request, not health or completion. Node displays “restart requested”; subsequent status/metadata reads establish whether the node returned and saved values became effective. Restarting can interrupt node activity; saving does not automatically request it.
Canonical reference route: qdn://APP/Node/Node?view=developers; developer/reference aliases normalize to developers. ?page=settings is preserved while viewing the reference. Returning to Node Status or Core Settings removes reference view/section parameters. Section links retain host parameters, repeated unknown parameters and fragments; Home Back/Forward restores the workspace.
Bridge examples
Examples illustrate the contract, using no live device data. Copying does not execute them. Keep settings changes and restart calls behind an explicit user decision.
+ {Object.entries(REFERENCE_SNIPPETS).map(([key, value]) =>{key}
{value}