gnoman 0.1.0

package/docs/wiki/user-guide.md

@@ -0,0 +1,73 @@
+@@ -109,57 +109,59 @@ The renderer surfaces the core workflows through a set of tabs defined in
+  `GET /api/safes/:address/owners` and `GET /api/safes/:address/transactions/held`
+  to populate data and to surface aggregated hold counters plus the effective
+  policy (global defaults + Safe override).
+- Tune Safe-specific hold duration and enable/disable flags directly from the
+  page. Changes are persisted to SQLite (`holds.sqlite`) and mirrored back via
+  `POST /api/safes/:address/hold`.
+- Held transactions reflect entries tracked by the SQLite-backed hold service in
+  `backend/services/transactionHoldService.ts`, complete with live countdowns
+  and manual release controls.
+
+### 4.4 Sandbox
+- Toggle between the legacy Safe callStatic form and the advanced sandbox panel
+  in `modules/sandbox/ui/SandboxPanel.tsx`.
+- Upload or paste ABIs, select contract functions, provide parameters, and run
+  simulations via `POST /api/sandbox/contract/simulate`.
+- Replay previous simulations pulled from `GET /api/sandbox/contract/history`
+  and optionally run them against a local fork started with
+  `POST /api/sandbox/fork/start` (defaults to the `anvil` command).
+- Provide a `forkRpcUrl` to execute simulations against a remote Hardhat/Anvil
+  fork when no managed local fork is available—the backend automatically falls
+  back to standard RPC calls if neither option is configured.
+- Use the Safe-focused tab to call `POST /api/sandbox/call-static` for quick
+  guard checks.
+
+### 4.5 Keyring
+- Lists secrets registered through the Electron IPC bridge (`window.gnoman.invoke('keyring:list')`).
+- Proxies every request to the backend AES keyring service (`/api/keyring/*`),
+  which stores encrypted payloads under `.gnoman/keyrings/<service>.json`.
+- Reveals a selected secret via `keyring:get`, which maps to `POST /api/keyring/get`.
+  If the `keyring` module cannot load (for example, inside a sandbox), the backend
+  switches to an in-memory store and logs a warning so you know the data is
+  ephemeral.
+- Encrypt, reveal, and delete secrets entirely inside the renderer. Each UI action
+  forwards to `/api/keyring/*`, guaranteeing parity with the legacy CLI while
+  capturing an auditable activity feed for operators.
+- Switch between keyring services (for example `production`, `staging`, or
+  `aes`) without leaving the UI. The currently active service is displayed in the
+  global header and sidebar so you never lose track of your namespace.
+- The backend still falls back to an in-memory store if the native `keyring`
+  module is unavailable. The UI highlights this state and keeps secrets scoped to
+  the session, while the CLI bridge remains for legacy automation only.
+
+### 4.6 License & Settings
+- The activation screen uses the preload bridge (`window.safevault`) to run the
+  Python verifier (`backend/licenses/verify_license.py`) entirely offline.
+- Successful validation writes `.safevault/license.env` with the raw token and a
+  `VALIDATED_AT` timestamp. The preload re-verifies this token on every launch.
+- Settings exposes the stored license metadata, the global transaction hold
+  toggle/duration (persisted in the AES keyring via `SAFE_TX_HOLD_ENABLED`), and a
+  vanity wallet generator surface with live job dashboards.
+- Vanity jobs are executed in worker threads, persisted to `.gnoman/vanity-jobs.json`
+  for auditability, and only expose mnemonic aliases so secrets stay in the
+  secure store.
+- For automation, the backend still accepts `POST /api/license`, which stores a
+  JSON record in `.gnoman/license.json`. This endpoint exists for legacy flows
+  that expect the previous storage format.
+
+### 4.7 Wiki Guide
+- Renders Markdown content from `docs/wiki/`, including the mirrored developer
+  and licensing guides.
+
+---
+
+## 5. Offline licensing quick reference
+
+| Task | Command |
+
+### 4.8 Integrations & Runtime Features (Settings)
+- Settings now includes a dedicated **Integrations & Runtime Features** section that surfaces one-glance enablement + reason status for `safe`, `etherscan`, and `robinhood`.
+- Status values come from `GET /api/runtime/capabilities`, which reflects backend runtime decisions instead of UI guesses.
+- Robinhood credential management is grouped under **Integration Configuration: Robinhood Crypto Trading API** to keep integration setup separate from license/hold/vanity controls.
+- Runtime diagnostics remain available under **Runtime Diagnostics** for detailed ABI cache activity, secrets source status, Safe runtime state, and Robinhood request telemetry.

package/eslint.config.js

@@ -0,0 +1,85 @@
+import js from '@eslint/js';
+import globals from 'globals';
+import tsParser from '@typescript-eslint/parser';
+import tsPlugin from '@typescript-eslint/eslint-plugin';
+import reactPlugin from 'eslint-plugin-react';
+import eslintConfigPrettier from 'eslint-config-prettier';
+
+export default [
+  {
+    ignores: ['dist/**', 'renderer/dist/**', 'node_modules/**']
+  },
+  {
+    files: ['**/*.{ts,tsx,js,jsx}'],
+    languageOptions: {
+      parser: tsParser,
+      parserOptions: {
+        ecmaVersion: 2020,
+        sourceType: 'module',
+        ecmaFeatures: {
+          jsx: true
+        }
+      },
+      globals: {
+        ...globals.es2021,
+        ...globals.node
+      }
+    },
+    plugins: {
+      '@typescript-eslint': tsPlugin,
+      react: reactPlugin
+    },
+    rules: {
+      ...js.configs.recommended.rules,
+      ...tsPlugin.configs.recommended.rules,
+      ...reactPlugin.configs.recommended.rules,
+      '@typescript-eslint/no-unused-vars': [
+        'error',
+        { argsIgnorePattern: '^_', varsIgnorePattern: '^_' }
+      ],
+      'react/react-in-jsx-scope': 'off'
+    },
+    settings: {
+      react: {
+        version: 'detect'
+      }
+    }
+  },
+  {
+    files: ['**/*.{ts,tsx}'],
+    rules: {
+      'no-undef': 'off'
+    }
+  },
+  {
+    files: ['renderer/**/*.{ts,tsx,js,jsx}'],
+    languageOptions: {
+      globals: {
+        ...globals.es2021,
+        ...globals.browser
+      }
+    }
+  },
+  {
+    files: ['modules/**/*.{ts,tsx,js,jsx}'],
+    languageOptions: {
+      globals: {
+        ...globals.es2021,
+        ...globals.browser
+      }
+    }
+  },
+  {
+    files: ['**/*.d.ts'],
+    rules: {
+      '@typescript-eslint/no-explicit-any': 'off'
+    }
+  },
+  {
+    files: ['**/*.js'],
+    rules: {
+      '@typescript-eslint/no-var-requires': 'off'
+    }
+  },
+  eslintConfigPrettier
+];

package/gnoman2.0/.eslintrc.cjs

@@ -0,0 +1,24 @@
+module.exports = {
+  root: true,
+  parser: '@typescript-eslint/parser',
+  parserOptions: {
+    ecmaVersion: 2020,
+    sourceType: 'module'
+  },
+  env: {
+    node: true,
+    browser: true,
+    es2020: true
+  },
+  plugins: ['@typescript-eslint', 'react'],
+  extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended', 'plugin:react/recommended', 'prettier'],
+  settings: {
+    react: {
+      version: 'detect'
+    }
+  },
+  ignorePatterns: ['dist', 'renderer/dist', 'renderer/node_modules'],
+  rules: {
+    'react/react-in-jsx-scope': 'off'
+  }
+};

package/gnoman2.0/.prettierrc.json

@@ -0,0 +1,6 @@
+{
+  "singleQuote": true,
+  "semi": true,
+  "trailingComma": "es5",
+  "printWidth": 100
+}

package/gnoman2.0/CODex_TASKS.md

@@ -0,0 +1,124 @@
+Codex: You are upgrading GNOMAN 2.0 into a fully self-sufficient, multi-platform application.
+
+Your tasks:
+
+────────────────────────────────────────
+1) CORE ARCHITECTURE
+────────────────────────────────────────
+Convert GNOMAN 2.0 into a modular, self-contained system with:
+
+- A unified backend service (Node.js, Python, or Rust — use existing project language)
+- A cross-platform UI layer
+- A shared API layer for all platforms
+- A plugin system for future extensions
+
+Ensure the backend can run:
+- As a local service
+- As a remote server
+- As a bundled embedded service inside desktop/mobile apps
+
+────────────────────────────────────────
+2) CROSS-PLATFORM BUILD TARGETS
+────────────────────────────────────────
+Add build support for:
+
+✔ Windows (x64 + ARM64)
+✔ Linux (x64 + ARM64)
+✔ macOS (Intel + Apple Silicon)
+✔ Android (APK)
+✔ iOS (IPA) — MOST IMPORTANT
+
+Use the following technologies:
+
+Desktop:
+  - Electron OR Tauri (prefer Tauri for smaller footprint)
+Mobile:
+  - React Native OR Flutter (choose whichever integrates best with existing code)
+Backend:
+  - Package backend as a standalone binary AND as a library callable from mobile/desktop.
+
+────────────────────────────────────────
+3) SELF-SUFFICIENCY REQUIREMENTS
+────────────────────────────────────────
+GNOMAN 2.0 must run with:
+
+- No external dependencies except:
+    - Configured APIs (Etherscan, Chainlink, Tenderly, etc.)
+- Local database (SQLite recommended)
+- Local caching layer
+- Built-in update checker
+- Built-in logging + diagnostics
+- Built-in configuration UI
+
+Add:
+- Auto-migration for DB schema
+- Auto-recovery if config is missing or corrupted
+
+────────────────────────────────────────
+4) SERVER MODE
+────────────────────────────────────────
+Add a “server mode” where GNOMAN 2.0 can run as:
+
+- A headless daemon
+- A system service (systemd, Windows service, macOS launchd)
+- A remote API endpoint
+
+Expose:
+- REST API
+- WebSocket events
+- Authentication (token-based)
+
+────────────────────────────────────────
+5) MOBILE (iOS PRIORITY)
+────────────────────────────────────────
+For iOS:
+
+- Use React Native or Flutter with a native bridge to the backend library.
+- Backend must compile to iOS ARM64.
+- Provide a local HTTP or direct native bridge for API calls.
+- Ensure sandbox-safe storage for config + DB.
+- Add offline mode.
+- Add background task support where allowed by iOS.
+
+For Android:
+- Mirror the iOS architecture.
+- Use the same shared backend library.
+
+────────────────────────────────────────
+6) INSTALLERS + PACKAGING
+────────────────────────────────────────
+Generate installers for:
+
+Windows:
+  - MSI or EXE installer
+Linux:
+  - .deb, .rpm, AppImage
+macOS:
+  - .dmg or .pkg
+Android:
+  - .apk
+iOS:
+  - Xcode project + build scripts for IPA generation
+
+────────────────────────────────────────
+7) CONFIG + ENV
+────────────────────────────────────────
+Wire in all existing .env keys and ensure:
+
+- Desktop apps read from local config file
+- Mobile apps use secure storage
+- Server mode uses environment variables
+
+────────────────────────────────────────
+8) VALIDATION
+────────────────────────────────────────
+After implementing:
+
+- Confirm all platforms build successfully
+- Confirm backend runs identically on all platforms
+- Confirm mobile apps can call the backend
+- Confirm server mode works remotely
+- Confirm no breaking changes to existing features
+
+Do NOT redesign existing logic.
+Extend GNOMAN 2.0 to be fully self-sufficient and multi-platform.

package/gnoman2.0/LICENSE.md

@@ -0,0 +1,164 @@
+# **PROPRIETARY LICENSE AGREEMENT — GNOMAN 2.0 SECURITY & ADMINISTRATION PLATFORM**
+
+**Version:** 1.0  **Effective Date:** 10.26.2025
+
+**Licensor:** **C. Hirschauer**, an individual residing in Iowa (“Licensor”)
+
+**Licensee:** The purchaser, recipient, or authorized operator of a valid GNOMAN 2.0 license (“Licensee”).
+
+---
+
+## 1. Definitions
+
+1.1 **“Software”** means the GNOMAN 2.0 desktop application, associated executables, libraries, Electron/React renderer, backend services, modules, APIs, plug-ins, data stores, simulation tools, key-management utilities, documentation, and any updates, patches, or derivatives provided by Licensor (including object and source code).
+1.2 **“Documentation”** means all user guides, technical manuals, wiki pages, and other written or electronic materials accompanying the Software.
+1.3 **“Personal License”** means a non-transferable license limited to one natural person for personal or educational use only.
+1.4 **“Business License”** means a non-exclusive license to deploy and operate the Software for the internal operations of one legal entity (including its employees and contractors under NDA), subject to this Agreement.
+1.5 **“License Fee”** means the non-refundable payment required to obtain a License.
+1.6 **“License Token”** means a digitally-signed activation string generated by Licensor’s Ed25519 private key and verified by the Software offline using its embedded public key.
+
+---
+
+## 2. Grant of License — Limited and Conditional
+
+2.1 **Personal License.** Upon full payment and acceptance of this Agreement, Licensor grants Licensee a limited, non-transferable, non-sublicensable, revocable license to install and use one copy of the Software solely for personal, non-commercial purposes on a single device.
+2.2 **Business License.** Upon full payment and compliance, Licensor grants Licensee a limited, non-transferable (except as provided in §16), non-sublicensable, revocable license to use the Software solely for internal business operations on the number of devices or environments purchased.
+2.3 **Reservation of Rights.** All rights not expressly granted remain with Licensor. The Software and Documentation are licensed, not sold.
+
+---
+
+## 3. Prohibited Uses — Zero Tolerance
+
+Licensee shall not, and shall not permit others to:
+a) Copy, distribute, rent, lease, sell, sublicense, or transfer the Software or Documentation;
+b) Reverse-engineer, decompile, disassemble, or modify the Software (except as required by law after notice to Licensor);
+c) Use the Software to offer third-party services (e.g., hosting, SaaS, multi-tenant management) without a separate commercial agreement;
+d) Remove or obscure any copyright or proprietary markings;
+e) Bypass, disable, or tamper with license-verification or cryptographic controls, including Ed25519 signature checks or token validation;
+f) Combine the Software with open-source components in a manner that would require disclosure of its source; or
+g) Use the Software in violation of any law or third-party rights.
+
+---
+
+## 4. Delivery, Activation, and Fees
+
+4.1 **Delivery.** The Software is delivered electronically after receipt of payment and identity verification (if applicable).
+4.2 **Fees.** License Fees are non-refundable unless expressly agreed in writing. Failure to pay when due constitutes material breach.
+4.3 **Activation.** Each license requires a valid offline License Token digitally signed by Licensor. The Software verifies the token using its embedded public key without internet communication. Tampering with this mechanism voids the License.
+
+---
+
+## 5. Ownership and Intellectual Property
+
+Licensor retains all title, ownership, and intellectual-property rights in the Software and Documentation. This Agreement conveys only the limited rights expressly granted.
+
+---
+
+## 6. Audit and Verification
+
+Licensor may request reasonable evidence of proper license activation or valid License Token(s). Licensee must cooperate by providing token files or logs on request. Non-compliance is a material breach.
+
+---
+
+## 7. Support and Updates
+
+Support or maintenance is not included unless purchased separately. Licensor may release updates at its sole discretion. Nothing herein obligates Licensor to continue development or compatibility.
+
+---
+
+## 8. Confidentiality
+
+Licensee shall treat the Software, Documentation, and licensing utilities as confidential, using no less care than for its own confidential information.
+
+---
+
+## 9. Warranties and Disclaimers
+
+9.1 **Limited Warranty.** For thirty (30) days after delivery, Licensor warrants the Software will substantially conform to the Documentation. Remedy: repair or replacement at Licensor’s option.
+9.2 **Disclaimer.** EXCEPT AS SET FORTH ABOVE, THE SOFTWARE IS PROVIDED “AS IS.” ALL OTHER WARRANTIES, EXPRESS OR IMPLIED (INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE), ARE DISCLAIMED TO THE MAXIMUM EXTENT PERMITTED BY LAW.
+
+---
+
+## 10. Indemnification
+
+Licensee shall indemnify and hold Licensor harmless from all claims, damages, or expenses (including attorneys’ fees) arising from Licensee’s use or breach of this Agreement.
+
+---
+
+## 11. Limitation of Liability
+
+TO THE MAXIMUM EXTENT PERMITTED BY LAW, LICENSOR WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF PROFITS OR DATA). TOTAL LIABILITY WILL NOT EXCEED THE LICENSE FEE PAID BY LICENSEE.
+
+---
+
+## 12. Remedies and Equitable Relief
+
+12.1 **Injunctive Relief.** Breach of Sections 3, 5, or 8 causes irreparable harm. Licensor may seek injunction or specific performance without bond.
+12.2 **Liquidated Damages.** Each intentional breach of Sections 3 or 8 incurs liquidated damages of USD $50,000 (or greater actual damages proven), plus costs and attorneys’ fees.
+
+---
+
+## 13. Enforcement and Attorneys’ Fees
+
+The prevailing party in any enforcement action arising from this Agreement is entitled to recover reasonable attorneys’ fees and costs, including appeals and collection.
+
+---
+
+## 14. Termination
+
+Upon any material breach, this Agreement terminates immediately. Licensee must cease all use, destroy all copies, and certify destruction in writing. Licensor may invalidate tokens or disable verification where legally permitted.
+
+---
+
+## 15. Export and Compliance
+
+Licensee shall comply with all export, import, and sanctions laws. The Software shall not be exported to prohibited regions or persons.
+
+---
+
+## 16. Transfer and Assignment
+
+Licenses are non-transferable without Licensor’s written consent. Business License assignment to a successor in interest requires Licensor’s prior approval and assumption of this Agreement.
+
+---
+
+## 17. Severability
+
+If any provision is held invalid, the remainder remains in force. The parties shall replace invalid terms with ones closest in intent and effect.
+
+---
+
+## 18. Governing Law and Venue
+
+This Agreement is governed by the laws of [STATE/COUNTRY OF RESIDENCE]. Exclusive venue for disputes shall be the state or federal courts of that jurisdiction. Each party waives objection to inconvenient forum.
+
+---
+
+## 19. Notices
+
+All notices must be in writing and sent to the addresses listed in the invoice or order. Notices take effect upon receipt.
+
+---
+
+## 20. Entire Agreement and Amendment
+
+This document is the entire agreement regarding the Software and supersedes all prior understandings. Amendments require a written instrument signed by both parties.
+
+---
+
+## 21. Miscellaneous
+
+21.1 **No Implied Licenses.** None are granted by implication or estoppel.
+21.2 **Publicity.** Licensee shall not use Licensor’s name or trademarks without written consent.
+21.3 **Survival.** Ownership, confidentiality, indemnity, liability, and other provisions that by their nature should survive termination will do so.
+
+---
+
+## 22. Signature and Acceptance
+
+By installing, activating, or using GNOMAN 2.0, Licensee acknowledges having read and agreed to be bound by this Agreement.
+Activation of the Software with a valid Ed25519-signed License Token constitutes electronic acceptance of this Agreement.
+
+---
+
+*(End of Agreement — GNOMAN 2.0 v1.0 — Licensor: C. Hirschauer, Individual)*

package/gnoman2.0/README.md

@@ -0,0 +1,95 @@
+![Sheen Banner](https://github.com/74Thirsty/74Thirsty/blob/main/assets/gnoman.svg)
+
+GNOMAN 2.0 is a cross-platform Electron desktop application that combines a local Express API with a React
+renderer to manage Gnosis Safe workflows from a single secured workspace. The project is written entirely
+in TypeScript and ships with tooling for simulating Safe transactions, managing wallets, and enforcing
+offline license policies before operators can act on production Safes.
+
+## Graphical-first operations
+
+The graphical client is the primary control plane. Every historic `gnoman` CLI capability now maps to a
+dedicated UI workflow—keyring management, wallet administration, Safe tooling, sandbox orchestration, and
+configuration live behind buttons, panels, and activity feeds. The CLI continues to exist for legacy
+automation, but receives no new features and is treated as a fallback transport only.
+
+## Tech stack
+
+- **Electron 28** for the desktop shell, preload isolation, and IPC keyring bridge (`main/`).
+- **Electron 28** for the desktop shell, preload isolation, and IPC keyring bridge (`main/`). Legacy IPC
+  handlers remain for backwards compatibility but all user journeys originate in the renderer.
+- **Express** with TypeScript for the local API that powers wallet, Safe, sandbox, and license flows
+  (`backend/`).
+- **React + Tailwind (Vite)** for the renderer UI (`renderer/`).
+- **Better SQLite3** for persisting transaction holds and vanity job history under a local
+  `.gnoman/` directory.
+- **Ethers v6** for wallet creation, encryption, and contract simulation utilities.
+
+## Repository layout
+
+```
+/ (root)
+├── backend/              # Express API, services, and route handlers
+├── main/                 # Electron entrypoint, preload, and AES keyring integration
+├── modules/sandbox/      # Shared sandbox engine, ABI parser, local fork helper, and UI panel
+├── renderer/             # React renderer bundled with Vite
+├── scripts/              # Build utilities for packaging renderer output and launching Electron
+├── docs/                 # Markdown documentation surfaced in the app and project wiki
+├── tests/                # API smoke tests and fixtures
+├── package.json          # Root npm scripts and dependencies
+└── tsconfig*.json        # TypeScript project references for each process
+```
+
+## Prerequisites
+
+| Requirement | Notes |
+@@ -155,47 +163,48 @@ The sandbox writes JSON logs to `modules/sandbox/logs/` and coordinates optional
+
+Validated tokens are re-verified at startup through the preload bridge and persist as a simple
+`.safevault/license.env` file that contains the raw token and a timestamp indicating when the
+desktop client last confirmed the signature. The REST endpoint continues to mirror metadata to
+`.gnoman/license.json` for legacy automation that reads the old format.
+
+### Offline license workflow (developer tooling)
+
+| Purpose | Command | Output |
+| --- | --- | --- |
+| Generate keypair (one-time) | `python backend/licenses/make_keys.py` | `license_private.pem`, `license_public.pem` |
+| Generate license token | `python backend/licenses/gen_license.py --id "Customer"` | Signed token (raw + Base32) |
+| Embed public key | Ship the checked-in `backend/licenses/license_public.pem` alongside the backend build | Used by verifier |
+| Validate offline | `python -c "from backend.licenses.verify_license import verify_token; print(verify_token('backend/licenses/license_public.pem', '<token>', 'GNOMAN', '2.0.0'))"` | Prints `True`/`False` |
+
+## Desktop application features
+
+- **Dashboard** – high-level overview of stored wallets and the currently connected Safe.
+- **Wallets** – generate encrypted wallets with optional aliases, hidden flag, and password overrides, then
+  list stored metadata.
+- **Safes** – connect to a Safe, review owners/modules, audit hold policy summaries, and monitor queued
+  transactions with live countdowns.
+- **Sandbox** – switch between the legacy Safe callStatic form and the advanced sandbox panel powered by
+  `modules/sandbox/ui`. Upload or paste ABIs, choose functions, provide parameters, replay historical
+  simulations, and manage an optional local fork.
+- **Keyring** – interact with the Electron IPC bridge (`window.gnoman`) to list and reveal secrets stored
+  in the AES keyring service (with a logged warning and in-memory fallback when the `keyring` module is unavailable).
+- **Keyring** – encrypt, reveal, switch, and audit secrets directly inside the UI. Requests flow through
+  the local REST API so every operation is recorded in the on-screen activity log. The CLI bridge remains
+  available for legacy scripts but no longer surfaces new behavior.
+- **Settings** – activate offline licensing, configure global hold defaults, launch vanity generators, and
+  jump to the in-app wiki.
+- **Wiki Guide** – render Markdown documentation from `docs/wiki` directly inside the renderer.
+
+## Data directories & security
+
+- Transaction-hold records and vanity job ledgers are stored under `.gnoman/` in the project working
+  directory (`holds.sqlite`, `vanity-jobs.json`), while validated license tokens live in
+  `.safevault/license.env`.
+- Sandbox logs persist to `modules/sandbox/logs/` for replay and auditing purposes.
+- Wallet private keys stay encrypted in-memory using AES-256-GCM with PBKDF2 key derivation. Exported
+  keystores require the caller-supplied password.
+- The Electron preload exposes a minimal `window.gnoman.invoke` surface to keep privileged operations
+  isolated from the renderer context.
+
+## Documentation
+
+Additional guides live under `docs/`. Start with `docs/user-guide.md` for a comprehensive walkthrough,
+`docs/license-dev-guide.md` for offline licensing workflows, and `docs/wiki/` for content surfaced in the
+in-app knowledge base.

package/gnoman2.0/backend/controllers/contractController.ts

@@ -0,0 +1,49 @@
+import asyncHandler from 'express-async-handler';
+import type { Request, Response } from 'express';
+import { addContract, listContracts, removeContract } from '../services/contractRegistryService';
+import { abiResolver } from '../utils/abiResolver';
+import { getBalance } from '../services/rpcService';
+
+export const listContractsHandler = asyncHandler(async (_req: Request, res: Response) => {
+  const records = listContracts();
+  const balances = await Promise.all(records.map((record) => getBalance(record.address)));
+  res.json(
+    records.map((record, index) => ({
+      ...record,
+      balance: balances[index]
+    }))
+  );
+});
+
+export const addContractHandler = asyncHandler(async (req: Request, res: Response) => {
+  const { address, name, network, tags, type, abi } = req.body as {
+    address: string;
+    name?: string;
+    network?: string;
+    tags?: string[];
+    type?: string;
+    abi?: string;
+  };
+  const record = addContract({ address, name, network, tags, type, abi });
+  res.status(201).json(record);
+});
+
+export const removeContractHandler = asyncHandler(async (req: Request, res: Response) => {
+  const removed = removeContract(req.params.id);
+  if (!removed) {
+    res.status(404).json({ message: 'Contract not found' });
+    return;
+  }
+  res.json(removed);
+});
+
+
+export const resolveContractAbiHandler = asyncHandler(async (req: Request, res: Response) => {
+  const { chainId, address, contractName } = req.body as { chainId?: number; address?: string; contractName?: string };
+  if (!address?.trim()) {
+    res.status(400).json({ message: 'address is required.' });
+    return;
+  }
+  const result = await abiResolver.resolve(Number(chainId) || 1, address, contractName);
+  res.json(result);
+});