mirror of
https://github.com/pezkuwichain/pezkuwi-telegram-miniapp.git
synced 2026-08-05 11:05:41 +00:00
pezkuwichain
2ed7ae3cf9
@pezkuwichainBot answers nothing today, for two independent reasons. Its webhook points at vbhftvdayqfmcgmzdxfv.supabase.co — the old Supabase Cloud project — which now returns 500, so /start never reaches this function at all. And even once that is repointed, routing picked the bot from a ?bot= query param and defaulted to `main`, whose mini app URL is telegram.pezkuwichain.io: the testnet domain whose DNS record was removed on 2026-07-12. An unqualified webhook call would have answered /start with a link that cannot resolve. The other two slots were both dead. `krd` held the real mainnet bot and the correct six-language welcome, but TELEGRAM_BOT_TOKEN_KRD was never set. `dks` was @DKSKurdistanBot, whose token was revoked on 2026-07-19. So: one token, one mini app URL (telegram.pezkiwi.app), one welcome — the six-language one that was written for this bot and never ran. Removes the AI chat path with it, which only the dks bot used; the same knowledge base lives on in the `ask` function, which is the assistant still being served. Adds the PEX.network link to that welcome and to /help. The button existed only in the dks welcome, so it has never actually been shown to anyone. 805 -> 292 lines.
Pezkuwi Telegram Mini App
Telegram Mini App for Pezkuwichain - Forum, Announcements, Rewards, and Wallet integration.
Tech Stack
- Frontend: React 18 + TypeScript + Vite
- Styling: Tailwind CSS + shadcn/ui patterns
- State: TanStack Query (React Query)
- Backend: Supabase (PostgreSQL + Auth + Edge Functions)
- Testing: Vitest + Testing Library
- CI/CD: GitHub Actions
Getting Started
Prerequisites
- Node.js >= 18
- npm >= 9
- Supabase account
Installation
# Clone the repo
git clone https://github.com/pezkuwichain/pezkuwi-telegram-miniapp.git
cd pezkuwi-telegram-miniapp
# Install dependencies
npm install
# Copy environment template
cp .env.example .env
# Add your Supabase credentials to .env
Development
# Start dev server
npm run dev
# Run tests
npm run test
# Type check
npm run typecheck
# Lint
npm run lint
# Format code
npm run format
# Full validation (typecheck + lint + test + build)
npm run validate
Build
npm run build
Output will be in dist/ directory.
Project Structure
src/
├── contexts/ # React contexts (Auth)
├── hooks/ # Custom hooks (Supabase, Telegram)
├── lib/ # Utilities (env, supabase client)
├── sections/ # Main app sections
│ ├── Announcements.tsx
│ ├── Forum.tsx
│ ├── Rewards.tsx
│ └── Wallet.tsx
├── test/ # Test setup
├── types/ # TypeScript types
├── App.tsx # Main app component
└── main.tsx # Entry point
Database Schema
Tables (prefixed with tg_ to avoid conflicts):
tg_users- Telegram userstg_announcements- Admin announcementstg_announcement_reactions- Like/dislike reactionstg_threads- Forum threadstg_thread_likes- Thread likestg_replies- Thread repliestg_reply_likes- Reply likes
Environment Variables
| Variable | Description |
|---|---|
VITE_SUPABASE_URL |
Supabase project URL |
VITE_SUPABASE_ANON_KEY |
Supabase anon/public key |
Telegram Setup
- Create bot via @BotFather
- Enable Mini App in bot settings
- Set Mini App URL to deployment URL
- Deploy
telegram-authEdge Function to Supabase
License
MIT