hailin
/
rwadurian
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2,093 Commits 1 Branch 10 Tags 182 MiB
Commit Graph

20 Commits

Author SHA1 Message Date
hailin e7260be219 feat(contribution): 添加系统账户算力来源类型字段 
- 添加 sourceType 字段区分算力来源类型：
  - FIXED_RATE: 固定比例分配（OPERATION 12%、PROVINCE 1%、CITY 2%）
  - LEVEL_OVERFLOW: 层级溢出归总部（上线未解锁该级别）
  - LEVEL_NO_ANCESTOR: 无上线归总部（该级无上线）
  - BONUS_TIER_1/2/3: 团队奖励未解锁归总部
- 添加 levelDepth 字段记录层级深度（1-15级）
- 更新前端表格显示来源类型列

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-21 04:23:50 -08:00
hailin 946978f624 fix(mining-admin): 修复 PostgreSQL NULL 唯一约束导致系统账户数据重复问题 
- 修改 synced_system_contributions 唯一索引使用 COALESCE 处理 NULL 值
- 修改 handleSystemAccountSynced 和 handleSystemContributionUpdated 方法
  使用 findMany 替代 findFirst，自动清理重复记录

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-21 03:29:24 -08:00
hailin 9062346650 refactor(system-accounts): 移除 baseType 字段，使用 accountType+regionCode 复合唯一键 
## 主要变更

### 数据模型简化
- 移除冗余的 baseType 字段，accountType 已包含类型信息
- 使用 accountType (OPERATION/PROVINCE/CITY/HEADQUARTERS) + regionCode (省市代码) 作为复合唯一键
- 所有查询改用 accountType+regionCode，100% 弃用数据库自增 ID

### contribution-service
- SystemAccount 表移除 baseType，改用 accountType+regionCode 唯一约束
- 修改算力分配逻辑，省市账户使用对应 regionCode
- 事件发布增加 regionCode 字段

### mining-service
- SystemMiningAccount 表使用 accountType+regionCode 唯一约束
- API 改为 /system-accounts/:accountType/records?regionCode=xxx 格式
- 挖矿分配逻辑支持按省市细分

### mining-admin-service
- SyncedSystemContribution 表使用 accountType+regionCode 唯一约束
- CDC 同步处理器适配新格式
- API 统一使用 accountType+regionCode 查询

## API 示例
- 运营账户: GET /admin/system-accounts/OPERATION/records
- 广东省: GET /admin/system-accounts/PROVINCE/records?regionCode=440000
- 广州市: GET /admin/system-accounts/CITY/records?regionCode=440100
- 总部: GET /admin/system-accounts/HEADQUARTERS/records

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-20 21:29:01 -08:00
hailin 81b2e7a4c2 refactor(migrations): 合并各服务的 migration 文件为单个 0001_init 
将各服务的多个 migration 文件合并到单一的初始化 migration 中:
- contribution-service: 3→1 (含 region 支持)
- mining-service: 4→1 (含 second 分配和 region 支持)
- mining-admin-service: 4→1 (含 region 和算力明细同步)
- auth-service: 2→1 (含 CDC 幂等)
- trading-service: 9→1 (含销毁系统/做市商/C2C)
- mining-wallet-service: 2→1 (含 SHARE_POOL 拆分)

所有迁移统一使用 TEXT 类型（非 VARCHAR）

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-20 20:34:56 -08:00
hailin 9c816266ac fix(schema): 统一使用 TEXT 类型替代 VARCHAR 
问题：
- 之前 schema 和 migration 中使用了 VARCHAR(n) 限制字段长度
- Prisma 的 String 类型默认映射到 PostgreSQL TEXT
- VARCHAR 和 TEXT 在 PostgreSQL 中性能相同，VARCHAR 限制反而增加风险

修复：
1. contribution-service:
   - schema: 移除 accountType/baseType/regionCode/name 的 @db.VarChar
   - migration: VARCHAR -> TEXT

2. mining-service:
   - schema: 移除 accountType/baseType/regionCode/name 的 @db.VarChar
   - migration: VARCHAR -> TEXT

3. mining-admin-service:
   - migration: VARCHAR -> TEXT (schema 已使用 TEXT)

原则：Prisma String 直接使用，不加 @db.VarChar()

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-20 20:24:01 -08:00
hailin 09b0bc077e feat(system-accounts): 实现系统账户按省市细分算力和挖矿分配 
## 核心功能

### 1. 算力按省市细分分配
- accountType 从枚举改为组合键字符串：PROVINCE_440000, CITY_440100
- 新增 baseType (基础类型) 和 regionCode (区域代码) 字段
- 认种时根据 selectedProvince/selectedCity 分配到具体省市账户
- 无省市信息时归入汇总账户

### 2. 系统账户参与挖矿
- 运营、省、市账户按各自 totalContribution 参与挖矿
- 总部账户(HEADQUARTERS)不直接参与，接收待解锁算力收益
- 待解锁算力 100% 参与挖矿，收益归总部

### 3. 算力来源明细追溯
- 新增 SystemContributionRecord 记录每笔算力来源
- 新增 SystemContributionRecordCreatedEvent 事件同步明细
- 前端新增"算力来源"标签页展示明细

## 修改的服务

### contribution-service
- schema: SystemAccount 新增 baseType, regionCode
- contribution-calculator: 按省市生成组合键
- system-account.repository: 支持动态创建省市账户
- 新增 SystemContributionRecordCreatedEvent 事件

### mining-service
- schema: SystemMiningAccount 从枚举改为字符串
- network-sync: 处理带 baseType/regionCode 的同步事件
- mining-distribution: 系统账户和待解锁算力参与挖矿

### mining-admin-service
- schema: 新增 SyncedSystemContributionRecord 表
- cdc-sync: 处理 SystemContributionRecordCreated 事件
- system-accounts.service: 新增算力来源明细和统计 API

### mining-admin-web
- 新增 ContributionRecordsTable 组件
- 系统账户详情页新增"算力来源"标签页
- 显示来源认种ID、用户、分配比例、金额

## 数据库迁移
- contribution-service: 20250120000001_add_region_to_system_accounts
- mining-service: 20250120000001_add_region_to_system_mining_accounts
- mining-admin-service: 20250120000001, 20250120000002

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-20 19:55:14 -08:00
hailin e00c81153b docs(migrations): add detailed comments for idempotency tables 
- Add comments explaining unique key composition:
  - CDC events: (source_topic, offset) = Kafka topic + message offset
  - Outbox events: (source_service, event_id) = service name + outbox ID
- Fix contribution-service migration:
  - Extend source_service column from VARCHAR(50) to VARCHAR(100)
  - Set source_service as NOT NULL to match schema
  - Use snake_case for index name consistency
- Clarify that offset/event_id are NOT database auto-increment IDs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 19:44:46 -08:00
hailin 577f626972 fix(cdc): implement idempotent consumer pattern for reliable CDC sync 
- Use (sourceTopic, eventId) as composite unique key in processed_events
- Add sourceTopic to ServiceEvent for globally unique idempotency key
- Wrap all handlers with withIdempotency() for duplicate event detection
- Fix ID collision issue between different service outbox tables

This implements the industry-standard CDC exactly-once semantics pattern.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 13:31:10 -08:00
hailin bfafd6d34c refactor(prisma): consolidate migrations into single init files 
Merge multiple incremental migrations into single init migration for each service:

- auth-service: 3 migrations → 1 (user auth, SMS, KYC)
- contribution-service: 4 migrations → 1 (contribution accounts, 15-level hierarchy, 3-tier bonus)
- mining-admin-service: 6 migrations → 1 (admin, CDC sync tables, prisma relation mode)
- mining-service: 1 migration (no change needed, renamed for consistency)
- mining-wallet-service: 3 migrations → 1 (wallet system, removed blockchain tables)
- trading-service: 1 migration (no change needed, renamed for consistency)

All migrations renamed from timestamp format (20260111000000_*) to sequential format (0001_init)
for cleaner migration history.

Note: Requires clearing _prisma_migrations table before applying to existing databases.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 11:04:24 -08:00
hailin ff3a614804 fix: remove broken data migration files 2026-01-12 10:08:10 -08:00
hailin e71f2aadfc fix: remove incorrect TEAM_BONUS records given to uplines 
TEAM_BONUS should only be given to the adopter themselves, not to their
uplines. This migration deletes all TEAM_BONUS records where
account_sequence != source_account_sequence.

Also updates contribution_accounts totals in contribution-service.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 09:49:44 -08:00
hailin a89f4c829d feat(mining-admin): add migration for distributionSummary column 
Add distributionSummary Text column to synced_adoptions table for storing
distribution details calculated during contribution calculation.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 09:33:58 -08:00
hailin 01ff873264 fix(mining-admin): use Prisma relationMode=prisma for CDC sync tables 
Switch to Prisma's "prisma" relation mode to handle CDC event ordering issues.
This mode emulates foreign key relations at the Prisma Client layer instead of
creating database-level FK constraints, which is the recommended approach for
CDC scenarios where event arrival order cannot be guaranteed.

Reference: https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/relation-mode

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 08:33:21 -08:00
hailin ea789f7fec fix(mining-admin): remove CDC sync table foreign key constraints 
CDC events arrive asynchronously and order is not guaranteed.
Child records (referrals, accounts) may arrive before parent (users).
This follows CDC best practices: destination tables should not have FK constraints.

Reference: https://estuary.dev/blog/cdc-done-correctly/

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 08:24:10 -08:00
hailin 40fbdec47c fix: add migration_lock.toml for prisma migrations 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 08:09:34 -08:00
hailin e337a1dda4 feat(mining-admin): add migration for contribution records and network progress tables 
- Add synced_contribution_records table for tracking contribution ledger
- Add synced_network_progress table for tracking network-wide stats
- Revert Dockerfile to use prisma migrate deploy

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 08:07:16 -08:00
hailin 180e5ad057 feat(mining-admin): 重构算力构成展示，添加解锁状态 
- 后端添加 unlockedBonusTiers 字段同步
- 前端算力构成卡片展示层级解锁(L1-15)和团队奖励解锁(3档)状态
- 移除无用的系统运营/省级/市级字段

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 04:59:51 -08:00
hailin 7b310c554b fix(migrations): 修复数据库迁移脚本语法 
- 移除 IF NOT EXISTS，使用标准 Prisma 迁移格式
- 确保 full-reset 能正确执行迁移

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 03:07:14 -08:00
hailin 4635fea693 chore(migrations): 添加数据库迁移脚本 
- auth-service: 20260112110000_add_nickname_to_synced_legacy_users
  - synced_legacy_users 表添加 nickname 字段

- mining-admin-service: 20260112110000_add_referral_adoption_nickname
  - synced_users 表添加 nickname 字段
  - 创建 synced_referrals 表 (推荐关系)
  - 创建 synced_adoptions 表 (认种记录)
  - 相关索引和外键约束

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-12 03:02:55 -08:00
hailin 51456373a9 feat(2.0-services): 添加所有服务的初始Prisma migrations 
使用 prisma migrate diff 生成初始数据库迁移脚本：
- mining-admin-service: 管理后台相关表及CDC同步表
- auth-service: 用户认证相关表
- trading-service: 交易相关表
- mining-wallet-service: 钱包相关表

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-11 00:06:46 -08:00