Telegram-native Web3 escrow protocol on QIE — AI‑powered dispute arbitration, real‑time dashboards, and on‑chain settlement.
Send a Telegram message. Get an escrow contract. Dispute with AI arbitration. All without leaving the chat.
Try it out: https://t.me/jessy_lynk_bot
Secure peer-to-peer transactions directly inside Telegram with AI-powered dispute arbitration and on-chain settlement.
LYNK eliminates trust issues in Telegram-based commerce by combining smart contract escrow, automated AI arbitration, and seamless chat-based interactions. Users can create and manage escrow agreements without leaving Telegram, while disputes are resolved instantly through AI analysis and executed transparently on-chain.
Peer-to-peer trading on messaging platforms often suffers from a lack of trust:
- Buyers fear paying without receiving goods.
- Sellers fear shipping without guaranteed payment.
- Traditional escrow systems are slow, complicated, and require users to leave the conversation.
- Human arbitration is expensive, delayed, and subjective.
LYNK solves this problem by bringing escrow and dispute resolution directly into Telegram.
Create and manage escrow agreements using simple chat commands:
BUY
STATUS
RELEASE
DISPUTE
TRACKING
HELP
No external Web3 UI required.
Disputes are automatically analyzed using:
- Groq SDK
- Llama 3.3 70B
The AI:
- Reviews chat history and evidence
- Generates human-readable reasoning
- Produces a confidence score
- Issues a binding ruling
Funds are securely:
- Locked in smart contracts
- Released according to agreement
- Settled transparently on the QIE Mainnet
Monitor every component through dedicated dashboards:
- Overview Dashboard
- Escrow Status
- Blockchain Explorer
- Arbitration Pipeline
- Telegram Bot Health
- Developer Tools
Every AI decision includes:
- Evidence analysis
- Generated reasoning
- Confidence metrics
- Fallback mechanisms
Telegram-based commerce currently lacks a reliable trust layer.
- Paying and never receiving goods.
- Delivering goods without payment guarantees.
- Poor UX
- Multiple external applications
- Slow human arbitrators
- High operational costs
LYNK introduces:
- Chat-first escrow
- AI dispute resolution
- On-chain execution
- Real-time monitoring
All within a familiar Telegram experience.
The system follows a simple flow:
Telegram Bot
↓
Webhook API
↓
Next.js Backend
↓
Supabase + Groq
↓
QIE Blockchain
↓
Frontend Dashboards
┌─────────────────────────────────────────────────────┐
│ Telegram Bot │
│ BUY / STATUS / RELEASE / DISPUTE / TRACKING / HELP │
└──────────────────┬──────────────────────────────────┘
│ POST /api/telegram/webhook
▼
┌──────────────────────────────────────────────────────┐
│ Next.js Backend (localhost:3000) │
│ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────┐ │
│ │ Deal Service│ │ AI Arbitrator│ │ Dispute API │ │
│ │ (Supabase) │ │ (Groq 70B) │ │ (REST) │ │
│ └──────┬──────┘ └──────┬───────┘ └──────┬──────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────────────────────────────────────┐ │
│ │ MultiSig Wallet Service │ │
│ │ openDispute / applyRuling / getStatus │ │
│ └──────────────────┬───────────────────────────┘ │
└─────────────────────┼────────────────────────────────┘
│ QIE RPC
▼
┌─────────────────────────────────────────────┐
│ LynkEscrow Smart Contract │
│ QIE Mainnet · Chain ID 1990 │
│ 0x5A871eD6740887f14F31dFB50a4e50486908DfAD │
└─────────────────────────────────────────────┘
▲
│ poll (10s)
▼
┌─────────────────────────────────────────────────────┐
│ Next.js Frontend (localhost:3001) │
│ │
│ Overview │ Escrow │ Telegram │ Developer Tools │
│ Blockchain Explorer │ Arbitration Pipeline │
└─────────────────────────────────────────────────────┘
| Layer | Technology |
|---|---|
| Smart Contracts | Solidity 0.8.28 + Hardhat |
| Backend | Next.js 15 + TypeScript |
| Frontend | Next.js 15 + Tailwind CSS |
| Database | Supabase (PostgreSQL) |
| AI Arbitrator | Groq SDK + Llama 3.3 70B |
| Blockchain | QIE Mainnet (Chain ID 1990) |
| Messaging | Telegram Bot API + Telegraf |
LYNK/
│
├── contracts/
├── backend/
├── frontend/
└── README.md
cd contracts
npm install
npx hardhat run scripts/deploy.ts --network qiecd backend
npm installCreate .env.local
QIE_RPC_URL=
TELEGRAM_BOT_TOKEN=
GROQ_API_KEY=
SUPABASE_URL=
SUPABASE_ANON_KEY=
SUPABASE_SERVICE_ROLE_KEY=Run:
npm run devBackend:
http://localhost:3000
cd frontend
npm installCreate .env.local
NEXT_PUBLIC_BACKEND_URL=
NEXT_PUBLIC_QIE_CONTRACT=Run:
npm run devFrontend:
http://localhost:3001
Expose your backend using:
ngrok http 3000Set the webhook endpoint:
/api/telegram/webhook
Buyer initiates purchase
↓
Escrow contract created
↓
Funds locked on-chain
↓
Seller delivers goods
↓
Buyer releases funds
↓
Transaction completed
Dispute raised
↓
Evidence collected
↓
Groq Llama 3.3 analyzes data
↓
AI generates ruling
↓
Smart contract executes settlement
| Method | Endpoint | Description |
|---|---|---|
GET |
/api/health |
RPC connectivity, wallet, balance, chain ID |
GET |
/api/escrow/status |
Escrow details: buyer, seller, amount, lifecycle |
POST |
/api/escrow/test-buy |
Simulate a buy transaction |
POST |
/api/escrow/release |
Release escrow funds |
POST |
/api/escrow/dispute |
Open on-chain dispute |
GET |
/api/deals |
Recent deals (last 10, descending) |
GET |
/api/disputes?page=1&limit=20 |
Paginated disputes with rulings, sorted by recency |
POST |
/api/telegram/webhook |
Telegram bot entrypoint |
GET |
/api/telegram/status |
In-memory bot telemetry |
{
"success": true,
"data": [
{
"dealId": "deal_1718000000_abc123",
"buyer": 123456789,
"seller": 987654321,
"amount": "100",
"status": "resolved",
"disputeRuling": "BUYER_WINS",
"disputeConfidence": 0.87,
"disputeReasoning": "Buyer provided photo evidence of damage...",
"resolvedAt": "2026-06-08T12:34:56Z"
}
],
"pagination": {
"page": 1,
"limit": 20,
"total": 5,
"totalPages": 1
}
}Escrow creation and command execution.
System-wide monitoring and metrics.
Reasoning, confidence score, and dispute workflow.
On-chain contract state and transaction lifecycle.
Support for:
- Ethereum
- Polygon
- Arbitrum
Secondary human review for:
- Low-confidence AI decisions
- High-value transactions
Enable funding via:
- Debit cards
- Credit cards
- Payment gateways
directly inside Telegram.
Native dispute analysis across global languages.
Network: QIE Mainnet
Chain ID: 1990
Contract Address:
0x5A871eD6740887f14F31dFB50a4e50486908DfAD
Contributions are welcome.
fork → branch → commit → pull request
Please ensure:
- Code quality is maintained.
- Tests pass successfully.
- Documentation remains updated.
MIT License