基于08-区块链生态基础设施开发指南的全面审计,修复以下问题: ## SDK 补全(对齐指南 §7.2-7.4) - **JS SDK**: 新增 SettlementModule (settlement.ts),实现 executeSwap() 合约交互 和 onSwapExecuted() 事件监听,补齐指南 §7.2 要求的 settlement 模块 - **Go SDK**: 新增 ExecuteSwap() 函数 (settlement.go),完整实现 ABI 编码 → nonce 获取 → gas 估算 → 签名 → 广播 → receipt 等链上交易全流程 - **Dart SDK**: 新增统一事件订阅接口 subscribeEvents(EventFilter),匹配指南 §7.4 规范;新增 EventFilter 模型类,支持 newHeads/logs 两种订阅类型 ## Enterprise API 加固(对齐指南 §3.2/§3.4) - 新增 TierThrottlerGuard 分层限流守卫,按 API tier 区分速率限制: public 60/min, institutional 600/min, regulatory/internal unlimited - WebSocket 网关增加完整认证:API Key 通过 query param 或 header 传递, 最低要求 institutional 级别,未认证连接自动拒绝 ## 删除无用的 wallet-service(架构纠正) - 删除 blockchain/wallet-service/ 整个目录(13个文件,875行代码) 该服务架构设计有误:钱包操作(用户钱包、机构操作、治理多签)已由现有 后端微服务处理(user-service:3001、issuer-service:3002、trading-service:3003、 clearing-service:3004),无需在 blockchain/ 目录下另建独立服务 - docker-compose.yml: 移除 wallet-service 服务定义和端口 3021 映射 - chain-ci.yml: 从 NestJS 生态服务 CI matrix 中移除 wallet-service - 08-指南: 删除第4节(钱包体系 §4.1-4.3),移除部署清单中 MPC签名服务:3021, 更新生态全景图,章节重新编号 (12→11章) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| backend | ||
| blockchain | ||
| docs | ||
| frontend | ||
| .gitignore | ||
| README.md | ||
README.md
Global Coupon Exchange
Website: gogenex.com
Brand Naming Strategy
This project adopts a regional branding strategy, using different brand names for different markets while maintaining brand family consistency.
Brand Structure
| Market | Brand | Abbr | Description |
|---|---|---|---|
| Western (US/Europe) | Genex | GNX | Derived from Generation + Exchange, familiar Western naming style |
| Asian (including China) | Gensen / 券信 | GS | "Gensen" from Cantonese pronunciation of Chinese characters "券信" |
Unified Domain
- gogenex.com - Single global domain for all markets
- Subdomains or paths for regional content (e.g., gogenex.com/cn, gogenex.com/asia)
Naming Logic
Genex (Western Markets)
- Gen = Generation / Generic / Genesis
- ex = Exchange
- Natural pronunciation, similar to well-known Western brands like FedEx, Amex
- Professional, modern, and trustworthy fintech image
Gensen / 券信 (Asian Markets)
- 券 (Quan) = Coupon / Voucher
- 信 (Xin) = Trust / Credit
- Gensen = Romanization of Cantonese pronunciation "gyun seon"
- Use Chinese characters "券信" in Mainland China
- Use romanized "Gensen" in other Asian regions
- Two characters conveying core values: coupon trading + trust guarantee
Brand Consistency
Genex ←── "Gen-" prefix ──→ Gensen
↑ ↑
└─────── Same brand family ────┘
↓
券信 (Chinese localization)
- Genex and Gensen share the "Gen-" prefix, establishing brand family recognition
- Gensen directly transliterates to 券信, providing seamless connection
- Global users can recognize these as regional versions of the same platform
Usage Scenarios
| Scenario | Western Markets | Asian Markets (non-China) | China Market |
|---|---|---|---|
| Company Name | GoGenex Inc. | Gensen Asia Ltd. | 券信科技有限公司 |
| App Name | Genex | Gensen | 券信 |
| Domain | gogenex.com | gogenex.com/asia | gogenex.com/cn |
| Social Media | @gogenex | @gensen_official | @券信official |
Note on Company Structure:
- Inc. (Corporation) for Western markets: Better for VC funding, stock issuance, and potential IPO
- Ltd. (Limited) for Asian markets: Common structure in Asia-Pacific region
- Social media handles use variations to avoid conflicts with existing accounts
Legal & Operations
Due to varying financial regulations across countries, each regional brand will:
- Operate as an independent legal entity
- Comply with local regulatory requirements
- Share core technology platform and philosophy
- Establish brand association through parent company
Project Overview
Global Coupon Exchange (GCX) is a coupon asset trading platform designed to provide users with secure and convenient trading services for digital assets such as coupons, gift cards, and vouchers.
Core Features
- Coupon asset listing and trading
- Secure transaction matching mechanism
- Multi-currency settlement support
- User credit system
Tech Stack
TBD
Documentation
For detailed development documentation, please refer to the docs directory.
License
TBD