@www.hyperlinks.space/program-kit 1.2.181818 → 7.8.3

package/database/wallets.ts

@@ -0,0 +1,266 @@
+/**
+ * Wallet helpers for the wallets table.
+ * Shared by API routes and bot-side services.
+ */
+import { sql } from './start.js';
+import { normalizeUsername } from './users.js';
+
+export type WalletRow = {
+  id: number;
+  telegram_username: string;
+  wallet_address: string;
+  wallet_blockchain: string;
+  wallet_net: string;
+  type: string;
+  label: string | null;
+  is_default: boolean;
+  source: string | null;
+  notes: string | null;
+  created_at: string;
+  updated_at: string;
+  last_used_at: string | null;
+  last_seen_balance_at: string | null;
+};
+
+export type RegisterWalletInput = {
+  telegramUsername: string;
+  walletAddress: string;
+  walletBlockchain: string;
+  walletNet: string;
+  type: string;
+  label?: string | null;
+  source?: string | null;
+  notes?: string | null;
+  isDefault?: boolean;
+};
+
+function normalizeText(raw: unknown): string {
+  if (typeof raw !== 'string') return '';
+  return raw.trim();
+}
+
+function normalizeLower(raw: unknown): string {
+  return normalizeText(raw).toLowerCase();
+}
+
+function normalizeAddress(raw: unknown): string {
+  return normalizeText(raw);
+}
+
+export async function listWalletsByUsername(
+  telegramUsername: string,
+): Promise<WalletRow[]> {
+  const username = normalizeUsername(telegramUsername);
+  if (!username) return [];
+
+  const rows = await sql<WalletRow[]>`
+    SELECT
+      id,
+      telegram_username,
+      wallet_address,
+      wallet_blockchain,
+      wallet_net,
+      type,
+      label,
+      is_default,
+      source,
+      notes,
+      created_at,
+      updated_at,
+      last_used_at,
+      last_seen_balance_at
+    FROM wallets
+    WHERE telegram_username = ${username}
+    ORDER BY is_default DESC, created_at ASC;
+  `;
+  return rows;
+}
+
+export async function getDefaultWalletByUsername(
+  telegramUsername: string,
+): Promise<WalletRow | null> {
+  const username = normalizeUsername(telegramUsername);
+  if (!username) return null;
+
+  const rows = await sql<WalletRow[]>`
+    SELECT
+      id,
+      telegram_username,
+      wallet_address,
+      wallet_blockchain,
+      wallet_net,
+      type,
+      label,
+      is_default,
+      source,
+      notes,
+      created_at,
+      updated_at,
+      last_used_at,
+      last_seen_balance_at
+    FROM wallets
+    WHERE telegram_username = ${username}
+    ORDER BY is_default DESC, created_at ASC
+    LIMIT 1;
+  `;
+
+  return rows[0] ?? null;
+}
+
+export async function setDefaultWallet(opts: {
+  telegramUsername: string;
+  walletAddress: string;
+  walletBlockchain: string;
+  walletNet: string;
+}): Promise<WalletRow | null> {
+  const username = normalizeUsername(opts.telegramUsername);
+  const walletAddress = normalizeAddress(opts.walletAddress);
+  const walletBlockchain = normalizeLower(opts.walletBlockchain);
+  const walletNet = normalizeLower(opts.walletNet);
+
+  if (!username || !walletAddress || !walletBlockchain || !walletNet) {
+    return null;
+  }
+
+  await sql`
+    UPDATE wallets
+    SET is_default = FALSE,
+        updated_at = NOW()
+    WHERE telegram_username = ${username};
+  `;
+
+  const rows = await sql<WalletRow[]>`
+    UPDATE wallets
+    SET is_default = TRUE,
+        updated_at = NOW()
+    WHERE telegram_username = ${username}
+      AND wallet_address = ${walletAddress}
+      AND wallet_blockchain = ${walletBlockchain}
+      AND wallet_net = ${walletNet}
+    RETURNING
+      id,
+      telegram_username,
+      wallet_address,
+      wallet_blockchain,
+      wallet_net,
+      type,
+      label,
+      is_default,
+      source,
+      notes,
+      created_at,
+      updated_at,
+      last_used_at,
+      last_seen_balance_at;
+  `;
+
+  const selected = rows[0] ?? null;
+  if (!selected) return null;
+
+  await sql`
+    UPDATE users
+    SET default_wallet = ${selected.id},
+        updated_at = NOW()
+    WHERE telegram_username = ${username};
+  `;
+
+  return selected;
+}
+
+export async function registerWallet(
+  input: RegisterWalletInput,
+): Promise<WalletRow | null> {
+  const telegramUsername = normalizeUsername(input.telegramUsername);
+  const walletAddress = normalizeAddress(input.walletAddress);
+  const walletBlockchain = normalizeLower(input.walletBlockchain);
+  const walletNet = normalizeLower(input.walletNet);
+  const walletType = normalizeLower(input.type);
+  const label = normalizeText(input.label ?? '');
+  const source = normalizeText(input.source ?? '');
+  const notes = normalizeText(input.notes ?? '');
+
+  if (
+    !telegramUsername ||
+    !walletAddress ||
+    !walletBlockchain ||
+    !walletNet ||
+    !walletType
+  ) {
+    return null;
+  }
+
+  const rows = await sql<WalletRow[]>`
+    INSERT INTO wallets (
+      telegram_username,
+      wallet_address,
+      wallet_blockchain,
+      wallet_net,
+      type,
+      label,
+      source,
+      notes,
+      is_default,
+      created_at,
+      updated_at
+    )
+    VALUES (
+      ${telegramUsername},
+      ${walletAddress},
+      ${walletBlockchain},
+      ${walletNet},
+      ${walletType},
+      ${label || null},
+      ${source || null},
+      ${notes || null},
+      FALSE,
+      NOW(),
+      NOW()
+    )
+    ON CONFLICT (telegram_username, wallet_address, wallet_blockchain, wallet_net)
+    DO UPDATE SET
+      type = EXCLUDED.type,
+      label = EXCLUDED.label,
+      source = EXCLUDED.source,
+      notes = EXCLUDED.notes,
+      updated_at = NOW()
+    RETURNING
+      id,
+      telegram_username,
+      wallet_address,
+      wallet_blockchain,
+      wallet_net,
+      type,
+      label,
+      is_default,
+      source,
+      notes,
+      created_at,
+      updated_at,
+      last_used_at,
+      last_seen_balance_at;
+  `;
+
+  const wallet = rows[0] ?? null;
+  if (!wallet) return null;
+
+  if (input.isDefault) {
+    return setDefaultWallet({
+      telegramUsername,
+      walletAddress,
+      walletBlockchain,
+      walletNet,
+    });
+  }
+
+  const currentDefault = await getDefaultWalletByUsername(telegramUsername);
+  if (!currentDefault) {
+    return setDefaultWallet({
+      telegramUsername,
+      walletAddress,
+      walletBlockchain,
+      walletNet,
+    });
+  }
+
+  return wallet;
+}

package/eslint.config.cjs

@@ -0,0 +1,10 @@
+// https://docs.expo.dev/guides/using-eslint/
+const { defineConfig } = require('eslint/config');
+const expoConfig = require('eslint-config-expo/flat');
+
+module.exports = defineConfig([
+  expoConfig,
+  {
+    ignores: ['dist/*'],
+  },
+]);

package/fullREADME.md

@@ -4,23 +4,31 @@
 
 <u>**In progress, contribute!**</u>
 
-This program is built upon [React Native](https://reactnative.dev/) by Meta and [Expo](https://expo.dev) multiplatform technologies, Windows build and executable creation achieved with [Electron Builder](https://www.electron.build/) and [Electron Forge](https://www.electronforge.io/), working in Telegram with help of [Telegram Mini Apps React SDK](http://telegram-mini-apps.com/) and [Bot API](https://core.telegram.org/bots). AI is backed by [OpenAI API](https://openai.com/ru-RU/api/), blockchain data is processed from [Swap.Coffee API](https://docs.swap.coffee/eng/user-guides/welcome).
-
-## Program Kit
-
-To give value for other developers we decided to launch an npm package that provides a ready starter for creating a multiplatform program in one command.
-
-```bash
-npx @www.hyperlinks.space/program-kit ./new-program
-```
-
-Link to the package: https://www.npmjs.com/package/@www.hyperlinks.space/program-kit
+This program is built upon [React Native](https://reactnative.dev/) by Meta and [Expo](https://expo.dev) multiplatform technologies, Windows build and executable creation achieved with [Electron Builder](https://www.electron.build/) and [Electron Forge](https://www.electronforge.io/), working in Telegram with help of [Telegram Mini Apps React SDK](http://telegram-mini-apps.com/), [Bot API](https://core.telegram.org/bots) and [Grammy](https://grammy.dev/). AI is backed by [OpenAI API](https://openai.com/ru-RU/api/), blockchain info is processed from [Swap.Coffee API](https://docs.swap.coffee/eng/user-guides/welcome). DB for the best user's experience we host on [Neon](https://neon.tech/).
 
 ## Program design
 
 Access [Figma](https://www.figma.com/design/53lDKAD6pRv3e0uef1DP18/TECHSYMBAL-Inc.?node-id=754-71&t=v3tmAlywNgXkTWMd-1) in real time for contributing. Contact [Seva](t.me/sevaaignatyev) in Telegram to discuss and implement.
 
-Copying fully or partially, usage as an inspiration for other developments are unpleasant, participation in our projects is appreciated. All core materials are available publicly for instant access worldwide and our project availability for newcomers.
+All core materials are available publicly for сгккуте hyperlinks.space team members' instant and easy access worldwide and our project's availability for newcomers' research only.
+
+## Structure
+
+- [`app`](./app) - Expo/React Telegram Mini App client (web/mobile screens, navigation, UI logic).
+- [`ui`](./ui) - shared UI layer (components, theme tokens, and font configuration used by the app).
+- [`bot`](./bot) - TypeScript Telegram bot service and runtime entrypoints.
+- [`database`](./database) - database startup/migration/service scripts.
+- [`ai`](./ai) - AI assistant service logic and model integration points.
+- [`api`](./api) - backend API handlers and server-side endpoints.
+- [`blockchain`](./blockchain) - TON/blockchain interaction logic and related helpers.
+- [`telegram`](./telegram) - Telegram-specific integration utilities and adapters.
+- [`windows`](./windows) - Electron desktop shell, NSIS installer config, and auto-update flow.
+- [`scripts`](./scripts) - developer/ops scripts (local run, migration, release helpers).
+- [`docs`](./docs) - project and operational documentation (architecture, releases, security reference, tooling).
+- [`research`](./research) - exploratory notes, investigations, and proposals not yet promoted to `docs/`.
+- [`backlogs`](./backlogs) - short-term planning notes and prioritized work items.
+- [`assets`](./assets) - static assets used by app, installer, and branding.
+- [`dist`](./dist) - generated web build output (export artifacts).
 
 ## How to fork and contribute?
 
@@ -64,15 +72,36 @@ git switch -c new-branch-for-next-update # Create and switch to a new feature br
 
 **Move in loops starting from the step 3.**
 
-## Pull requests and commits requirements
+## Local deploy
 
-- Give pull requests and commits a proper name and description
-- Dedicate each pull request to an understandable area or field, each commit to a focused logical change
-- Check file changes in every commit pulled, no arbitrary files modifications should persist such as LF/CRLF line-ending conversion, broken/garbled text diffs, BOM added or removed, accidental "invisible" corruption from text filters
-- Add dependecies and packages step by step for security
-- An issue creation or following an existing before a pull request would be a good practice
+`npm` package note: `.env.example` is included in the published package so you can use it as a reference for establishing your testing environment with `.env` file.
+
+Before local deploy / cloud deploy, prepare these env-backed services:
+
+1. **Neon PostgreSQL (`DATABASE_URL`)**
+   - Create an account/project at [Neon](https://neon.tech/).
+   - Create a database and copy the connection string.
+   - Put it into `.env` as `DATABASE_URL=...`.
+2. **OpenAI API (`OPENAI_API_KEY`)**
+   - Create an account at [OpenAI Platform](https://platform.openai.com/).
+   - Create an API key in the API Keys page.
+   - Put it into `.env` as `OPENAI_API_KEY=...`.
+3. **Telegram bot token (`BOT_TOKEN`)**
+   - In Telegram, open [@BotFather](https://t.me/BotFather), create a test bot with `/newbot`.
+   - Copy the bot token and put it into `.env` as `BOT_TOKEN=...`.
+4. **Vercel project envs (for comfortable deploy/testing)**
+   - Create a [Vercel](https://vercel.com/) account and import this repository as a project.
+   - In Project Settings -> Environment Variables, set at least:
+     - `DATABASE_URL`
+     - `OPENAI_API_KEY`
+     - `BOT_TOKEN` (or `TELEGRAM_BOT_TOKEN`)
+   - Pull envs locally when needed with `vercel env pull .env.local`.
+
+Copy env template locally:
 
-## Local deploy
+```bash
+cp .env.example .env
+```
 
 To start the full local stack, run:
 
@@ -82,67 +111,31 @@ npm run start
 
 This runs Expo dev server, the Telegram bot (polling mode), and local Vercel API (`vercel dev`).
 
+After `npm run start`, you can test the app on real phones with Expo Go:
+
+- Install **Expo Go** from Google Play (Android) or App Store (iOS).
+- Make sure your phone and development machine are on the same network.
+- Open Expo Go and scan the QR code shown in the terminal/Expo UI.
+- The app will launch on the device and hot-reload on code changes.
+
 Isolated/local run options:
 
 - Expo only (no bot, no Vercel): `npm run start:expo`
 - Bot only (polling mode): `npm run bot:local`
 - Vercel API only: `npm run dev:vercel`
 
-## Milestone snapshot package (npm)
-
-NPM release and snapshot details were moved to `docs/npm-release.md`.
-
-### Local env setup
-
-1. **Copy the example file** (from the repository root):
-   ```bash
-   cp .env.example .env
-   ```
-2. **Edit `.env`** and set at least:
-   - **`BOT_TOKEN`** – if you run the Telegram bot locally (`npm run bot:local`).
-3. **Expo app** – `npx expo start` reads env from the environment; for app-only env vars you can also put them in `.env` and use an Expo-compatible loader if you add one, or set them in the shell before running:
-   ```bash
-   export BOT_TOKEN=your_token
-   npx expo start
-   ```
-4. **Bot local** – `npm run bot:local` loads `.env` from the project root (optional; you can also set `BOT_TOKEN` in the shell).
-
-The `.env` file is gitignored; do not commit it.
-
 ## GitHub Actions
 
 Current Actions workflows include:
 
-- `Vercel Deploy Test` (`.github/workflows/vercel-deploy-test-envs.yml`) - manual web deploy to Vercel.
-- `NPM Package Release` (`.github/workflows/npm-package-release.yml`) - npm/GitHub Packages release workflow.
-- `Electron EXE Release` and `Electron Forge EXE Release` - manual Windows release pipelines.
-- `EXPO Publish` (`.github/workflows/expo-publish.yml`) - manual OTA publish with EAS CLI.
-- `Lint errors check` (`.github/workflows/lint-errors-check.yml`) - manual lint check.
-
-## Expo Workflows
-
-This project uses two automation layers:
-
-- [EAS Workflows](https://docs.expo.dev/eas/workflows/get-started/) for Expo update/build/deploy flows (triggered via npm scripts from [`package.json`](./package.json)).
-- GitHub Actions for CI/CD tasks stored in `.github/workflows` (manual release/deploy jobs and checks).
-
-### Previews
+- [`Vercel Deploy Test`](./.github/workflows/vercel-deploy-test-envs.yml) - manual web deploy to Vercel.
+- [`Electron Forge EXE Release`](./.github/workflows/electron-forge-exe-release.yml) - manual Windows release pipeline.
+- [`Electron EXE Release`](./.github/workflows/electron-exe-release.yml) - manual Windows release pipeline.
+- [`Lint errors check`](./.github/workflows/lint-errors-check.yml) - manual lint check.
+- [`EXPO Publish`](./.github/workflows/expo-publish.yml) - manual OTA publish with EAS CLI.
+- [`NPM Package Release`](./.github/workflows/npm-package-release.yml) - npm/GitHub Packages release workflow.
 
-Run `npm run draft` to [publish a preview update](https://docs.expo.dev/eas/workflows/examples/publish-preview-update/) of your project, which can be viewed in Expo Go or in a development build.
-
-### Development Builds
-
-Run `npm run development-builds` to [create a development build](https://docs.expo.dev/eas/workflows/examples/create-development-builds/). Note - you'll need to follow the [Prerequisites](https://docs.expo.dev/eas/workflows/examples/create-development-builds/#prerequisites) to ensure you have the correct emulator setup on your machine.
-
-### Production Deployments
-
-Run `npm run deploy` to [deploy to production](https://docs.expo.dev/eas/workflows/examples/deploy-to-production/). Note - you'll need to follow the [Prerequisites](https://docs.expo.dev/eas/workflows/examples/deploy-to-production/#prerequisites) to ensure you're set up to submit to the Apple and Google stores.
-
-## Hosting
-
-Expo offers hosting for websites and API functions via EAS Hosting. See the [Getting Started](https://docs.expo.dev/eas/hosting/get-started/) guide to learn more.
-
-### Deploy web build to Vercel
+## Deploy to Vercel
 
 From the repository root, deploy the static web build to Vercel production:
 
@@ -152,7 +145,7 @@ vercel --prod
 
 Deploying from repository root makes this folder the project root, so `api/bot` is deployed and no Root Directory setting is needed. The project is configured so Vercel runs `npx expo export -p web` and serves the `dist/` output. Link the project first with `vercel` if needed.
 
-## Telegram bot (Grammy)
+## Telegram bot
 
 The bot is extended beyond a basic "Hello" and "Start program" responder and now supports AI streaming and threads.
 
@@ -174,6 +167,84 @@ The bot is extended beyond a basic "Hello" and "Start program" responder and now
 - Run full local stack (Expo + bot + Vercel): `npm run start`
 - Keep production and local bot tokens separate when possible to avoid webhook/polling conflicts.
 
-## Where to discuss the project?
+## Pull requests and commits requirements
+
+- Give pull requests and commits a proper name and description
+- Dedicate each pull request to an understandable area or field, each commit to a focused logical change
+- Check file changes in every commit pulled, no arbitrary files modifications should persist such as LF/CRLF line-ending conversion, broken/garbled text diffs, BOM added or removed, accidental "invisible" corruption from text filters
+- Add dependecies and packages step by step for security
+- An issue creation or following an existing before a pull request would be a good practice
+
+## Expo Workflows
+
+[EAS Workflows](https://docs.expo.dev/eas/workflows/get-started/) are here for Expo update/build/deploy flows (triggered via npm scripts from [`package.json`](./package.json)).
+
+## Previews
+
+Run `npm run draft` to [publish a preview update](https://docs.expo.dev/eas/workflows/examples/publish-preview-update/) of your project, which can be viewed in Expo Go or in a development build.
+
+## Development Builds
+
+Run `npm run development-builds` to [create a development build](https://docs.expo.dev/eas/workflows/examples/create-development-builds/). Note - you'll need to follow the [Prerequisites](https://docs.expo.dev/eas/workflows/examples/create-development-builds/#prerequisites) to ensure you have the correct emulator setup on your machine.
+
+## Expo envs setup
+
+**Expo app** – `npx expo start` reads env from the environment; for app-only env vars you can also put them in `.env` and use an Expo-compatible loader if you add one, or set them in the shell before running:
+   ```bash
+   export BOT_TOKEN=your_token
+   npx expo start
+   ```
+
+## GitLab access
+
+GitHub and GitLab repositories are identical. If you want to contribute through GitLab, get access from [@staindart](https://github.com/staindart).
+
+If you can push to **both** [GitHub](https://github.com/HyperlinksSpace/HyperlinksSpaceProgram) and [GitLab](https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram) directly, we ask you to configure Git so pushes keep **both** hosts in sync: the repositories are the same; avoid updating only one side.
+
+1. **Keep `origin` on GitHub for fetch and the first push URL.** If you cloned from GitHub, this is already true: `origin` is where `git pull` / `git fetch origin` get updates. We standardize on GitHub for **incoming** history from `origin` so your local `main` tracks `origin/main` on GitHub.
+
+2. **Register GitLab as a second push URL on `origin`.** Git allows multiple **push** URLs per remote name, but only one **fetch** URL. Adding GitLab here means a single `git push origin <branch>` (or the IDE **Sync** push step) sends the same commits to **both** GitHub and GitLab without a second command.
+
+   ```bash
+   git remote set-url --add --push origin https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git
+   ```
+
+   Run this once per clone; it does not change where you fetch from.
+
+3. **Add a separate remote named `gitlab`.** Because `origin`’s fetch URL stays on GitHub, `git fetch origin` never downloads refs from GitLab. The extra remote lets you run `git fetch gitlab` when you need to compare or merge with the GitLab copy (for example if CI or another contributor updated GitLab only).
+
+   ```bash
+   git remote add gitlab https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git
+   ```
+
+   Note, that GitHub and GitLab URL's are a little different :)
+
+   If `gitlab` already exists with a wrong URL, use `git remote set-url gitlab https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git` instead.
+
+4. **Verify** with `git remote -v`. You should see GitHub on fetch/push for `origin`, GitLab as the second `origin` push line, and `gitlab` for fetch/push to GitLab:
+
+   ```text
+   gitlab  https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git (fetch)
+   gitlab  https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git (push)
+   origin  https://github.com/HyperlinksSpace/HyperlinksSpaceProgram.git (fetch)
+   origin  https://github.com/HyperlinksSpace/HyperlinksSpaceProgram.git (push)
+   origin  https://gitlab.com/hyperlinks.space/HyperlinksSpaceProgram.git (push)
+   ```
+
+**GitLab HTTPS access:** GitLab.com does not use **fine-grained** personal access tokens for Git-over-HTTPS (`git push` / `git fetch`). Create a **legacy** personal access token under GitLab → **Edit profile** → **Access tokens** with scopes **`read_repository`** and **`write_repository`**, as described in the official guide: [Personal access tokens](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html). Use your GitLab username and the token as the password when Git prompts. GitHub authentication stays separate (for example `gh auth login` or your existing GitHub credential).
+
+## Program Kit
+
+To make it easier for developers to create multiplatform programs with us, we decided to launch an npm package that provides a ready starter for creating such a program basis in one command.
+
+```bash
+npx @www.hyperlinks.space/program-kit ./new-program
+```
+
+Link to the package: https://www.npmjs.com/package/@www.hyperlinks.space/program-kit
+
+The **npm registry page** shows a separate package-oriented description: [`npmReadMe.md`](./npmReadMe.md) in the repo root. At publish time the [NPM Package Release](.github/workflows/npm-package-release.yml) workflow copies the main [`README.md`](./README.md) to `fullREADME.md`, then replaces `README.md` with the contents of `npmReadMe.md` so `npm pack` / `npm publish` ship the shorter readme as the package readme (npm always surfaces `README.md` from the tarball). Snapshot channels, tags, and local `npm pack` checks are in [`docs/npm-release.md`](./docs/npm-release.md).
+
+## Project discussions
 
 This repository has [GitHub Discussions](https://github.com/HyperlinksSpace/HyperlinksSpaceProgram/discussions) opened, as well you can join our [Telegram Chat](https://t.me/HyperlinksSpaceChat) and [Channel](https://t.me/HyperlinksSpace).

package/index.js

@@ -0,0 +1,3 @@
+// Earliest bundle entry: polyfill Node `Buffer` before expo-router loads route modules (@ton/* uses it at load time).
+import "./polyfills/buffer";
+import "expo-router/entry";

package/npmReadMe.md

@@ -33,12 +33,17 @@ registry and token.
 
 ## After Scaffold
 
+Copy `npmrc.example` to `.npmrc` so installs match this repo (`legacy-peer-deps`; npm does not ship a real `.npmrc` in the tarball for security):
+
 ```bash
 cd new-program
+cp npmrc.example .npmrc
 npm install
 npm run start
 ```
 
+If you prefer not to use a `.npmrc`, you can run **`npm install --legacy-peer-deps`** instead of the copy step.
+
 Then open the project **`fullREADME.md`** for details (env vars, bot setup, build
 and release commands).
 
@@ -49,5 +54,5 @@ and release commands).
 
 ## Notes
 
-- Published directly from the `app/` folder.
-- Package tarball is filtered to include only required project files.
+- Published from the repository root; the pack includes everything except patterns in [`.npmignore`](./.npmignore) (no `files` whitelist in `package.json`).
+- `.npmrc` cannot be published on npm; `npmrc.example` is included so you can copy it locally.

package/npmrc.example

@@ -0,0 +1 @@
+legacy-peer-deps=true

package/package.json

@@ -8,39 +8,15 @@
   "bin": {
     "program-kit": "scripts/program-kit-init.cjs"
   },
-  "files": [
-    "README.md",
-    "fullREADME.md",
-    "npmReadMe.md",
-    "app",
-    "api",
-    "app.json",
-    "assets",
-    "blockchain",
-    "bot",
-    "database",
-    "docs",
-    "!docs/debug.log",
-    "!docs/issue.md",
-    "eas.json",
-    "eslint.config.js",
-    "global.css",
-    "package-lock.json",
-    "scripts",
-    "telegram",
-    "tsconfig.json",
-    "vercel.json",
-    "windows"
-  ],
   "publishConfig": {
     "access": "public"
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/HyperlinksSpace/HyperlinksSpaceBot.git"
+    "url": "https://github.com/HyperlinksSpace/HyperlinksSpaceProgram.git"
   },
-  "main": "expo-router/entry",
-  "version": "1.2.181818",
+  "main": "index.js",
+  "version": "7.8.3",
   "type": "module",
   "engines": {
     "node": ">=18 <=22"
@@ -161,6 +137,10 @@
     "@react-navigation/native": "^7.1.6",
     "@swap-coffee/sdk": "^1.5.4",
     "@tma.js/sdk-react": "^3.0.16",
+    "@ton/core": "^0.63.1",
+    "@ton/crypto": "^3.3.0",
+    "@ton/ton": "^16.2.3",
+    "buffer": "^6.0.3",
     "electron-updater": "^6.8.3",
     "expo": "~54.0.0",
     "expo-blur": "~15.0.8",

package/polyfills/buffer.ts

@@ -0,0 +1,9 @@
+/**
+ * Load before any module that touches Node's `Buffer` at evaluation time (e.g. @ton/*).
+ * Browsers and Telegram WebView do not define `globalThis.Buffer`.
+ */
+import { Buffer } from "buffer";
+
+if (typeof globalThis !== "undefined" && !(globalThis as { Buffer?: unknown }).Buffer) {
+  (globalThis as { Buffer: typeof Buffer }).Buffer = Buffer;
+}