This website requires JavaScript.
6497b2ef0a
feat: script fix
2025-11-07 02:23:13 +08:00
6086eeb2ad
feat: script fix
2025-11-07 02:16:29 +08:00
5f949afd29
Add Terms of Service (#656 ) * Add Privacy Policy * Add Terms of Service
2025-11-07 03:16:05 +09:00
b93b029d99
feat: crypto script fix
2025-11-07 02:10:42 +08:00
44a60d12c0
feat：migrate for crypto
2025-11-07 01:57:00 +08:00
e570793d40
Add Privacy Policy (#655 )
2025-11-07 02:54:25 +09:00
3a23167d31
fix(web): restore ESLint, Prettier, and Husky code quality tools (#648 ) ## Problem PR #647 accidentally removed all code quality tools when adding test dependencies: - ❌ ESLint (9 packages) - code linting - ❌ Prettier - code formatting - ❌ Husky - Git hooks - ❌ lint-staged - pre-commit checks - ❌ Related scripts (lint, format, prepare) This significantly impacts code quality and team collaboration. ## Root Cause When adding test dependencies (vitest, @testing-library/react), the package.json was incorrectly edited, removing all existing devDependencies. ## Solution Restore all code quality tools while keeping the new test dependencies: ### ✅ Restored packages: - @eslint/js - @typescript-eslint/eslint-plugin - @typescript-eslint/parser - eslint + plugins (prettier, react, react-hooks, react-refresh) - prettier - husky - lint-staged ### ✅ Kept test packages: - @testing-library/jest-dom - @testing-library/react - jsdom - vitest ### ✅ Restored scripts: ``json { "lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0", "lint:fix": "eslint . --ext ts,tsx --fix", "format": "prettier --write \"src/**/*.{ts,tsx,css,json}\"", "format:check": "prettier --check \"src/**/*.{ts,tsx,css,json}\"", "test": "vitest run", "prepare": "husky" } `` ### ✅ Restored lint-staged config ## Impact This fix restores: - Automated code style enforcement - Pre-commit quality checks - Consistent code formatting - Team collaboration standards ## Testing - [x] npm install succeeds - [x] npm run build succeeds - [x] All scripts are functional Related-To: PR #647 Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-07 01:30:13 +08:00
336ae195d6
Merge branch 'feature/crypto' of github.com:NoFxAiOS/nofxos into origin/beta # Conflicts: # config.json.example # config/config.go
2025-11-07 01:28:47 +08:00
03313fffda
update link
2025-11-07 01:24:44 +08:00
e73e427e35
feat: crypto for key
2025-11-07 01:25:18 +08:00
43561a4ad7
fix(web): resolve TypeScript type error in crypto.ts and add missing test dependencies (#647 ) `` src/lib/crypto.ts(66,32): error TS2345: Argument of type 'Uint8Array<ArrayBuffer>' is not assignable to parameter of type 'ArrayBuffer'. ` arrayBufferToBase64 function expected ArrayBuffer but received Uint8Array.buffer. TypeScript strict type checking flagged the mismatch. 1. Update arrayBufferToBase64 signature to accept ArrayBuffer | Uint8Array 2. Pass result directly instead of result.buffer (more accurate) 3. Add runtime type check with instanceof ` error TS2307: Cannot find module 'vitest' error TS2307: Cannot find module '@testing-library/react' `` Install missing devDependencies: - vitest - @testing-library/react - @testing-library/jest-dom ✅ Frontend builds successfully ✅ TypeScript compilation passes ✅ No type errors Related-To: Docker frontend build failures
2025-11-07 01:19:48 +08:00
2ac48e20a4
refactor(crypto): simplify to local encryption only (remove KMS) ## 🎯 簡化方案（社區友好） ### 移除雲端 KMS - ❌ 刪除 crypto/aliyun_kms.go - ❌ 不包含 GCP KMS - ✅ 僅保留本地 AES-256-GCM 加密 ### 更新 SQLite 驅動 - ✅ modernc.org/sqlite（純 Go，無 CGO） - ✅ 與上游保持一致 ## 📦 保留核心功能 ✅ crypto/encryption.go - RSA + AES 加密 ✅ crypto/secure_storage.go - 數據庫加密層 ✅ api/crypto_handler.go - API 端點 ✅ web/src/lib/crypto.ts - 前端加密 ✅ scripts/migrate_encryption.go - 數據遷移 ## 🚀 部署方式 ``bash # 僅需一個環境變量 export NOFX_MASTER_KEY=$(openssl rand -base64 32) go run main.go `` ## ✅ 優點 - ✅ 零雲服務依賴 - ✅ 簡單易部署 - ✅ 適合社區用戶 - ✅ 保持核心安全功能
2025-11-06 23:58:27 +08:00
feeaa14050
feat(security): add end-to-end encryption for sensitive data ## Summary Add comprehensive encryption system to protect private keys and API secrets. ## Core Components - crypto/encryption.go: RSA-4096 + AES-256-GCM encryption manager - crypto/secure_storage.go: Database encryption layer + audit logs - crypto/aliyun_kms.go: Optional Aliyun KMS integration - api/crypto_handler.go: Encryption API endpoints - web/src/lib/crypto.ts: Frontend two-stage encryption - scripts/migrate_encryption.go: Data migration tool - deploy_encryption.sh: One-click deployment ## Security Architecture `` Frontend: Two-stage input + clipboard obfuscation ↓ Transport: RSA-4096 + AES-256-GCM hybrid encryption ↓ Storage: Database encryption + audit logs ` ## Features ✅ Zero breaking changes (backward compatible) ✅ Automatic migration of existing data ✅ <25ms overhead per operation ✅ Complete audit trail ✅ Optional cloud KMS support ## Migration `bash ./deploy_encryption.sh # 5 minutes, zero downtime ` ## Testing `bash go test ./crypto -v `` Related-To: security-enhancement
2025-11-06 21:01:47 +08:00
7ce7c64fa8
feat: improve model/exchange deletion and selection logic - Add soft delete support for AI models * Add deleted field to ai_models table * Implement soft delete with sensitive data cleanup * Filter deleted records in queries - Replace browser confirm dialogs with custom styled modals * Create DeleteConfirmModal component with Binance theme * Add proper warning messages and icons * Improve user experience with consistent styling - Fix duplicate model/exchange display in selection dropdowns * Use supportedModels/supportedExchanges for modal selectors * Use configuredModels/configuredExchanges for panel display * Remove redundant selectableModels/selectableExchanges logic - Enhance data management * Refresh data after deletion operations * Proper state cleanup after modal operations * Clear sensitive data during soft delete 🤖 Generated with [Claude Code](https://claude.ai/code ) Co-Authored-By: tinkle-community <tinklefund@gmail.com >
2025-11-06 22:05:21 +08:00
bbf34e70c2
feat: improve model/exchange deletion and selection logic - Add soft delete support for AI models * Add deleted field to ai_models table * Implement soft delete with sensitive data cleanup * Filter deleted records in queries - Replace browser confirm dialogs with custom styled modals * Create DeleteConfirmModal component with Binance theme * Add proper warning messages and icons * Improve user experience with consistent styling - Fix duplicate model/exchange display in selection dropdowns * Use supportedModels/supportedExchanges for modal selectors * Use configuredModels/configuredExchanges for panel display * Remove redundant selectableModels/selectableExchanges logic - Enhance data management * Refresh data after deletion operations * Proper state cleanup after modal operations * Clear sensitive data during soft delete 🤖 Generated with [Claude Code](https://claude.ai/code ) Co-Authored-By: tinkle-community <tinklefund@gmail.com >
2025-11-06 22:05:21 +08:00
8dc543b1cf
fix(web): 修正 FAQ 翻译文件中的错误信息 (#552 ) - 删除 OKX 虚假支持声明（后端未实现） - 补充 Aster DEX 的 API 配置说明 - 修正测试网说明为暂时不支持
2025-11-06 21:59:10 +08:00
900323b386
Fix: 提示词, 竞赛数据接口在管理员模式下转为公开 (#607 ) * 提示词, 竞赛数据接口在管理员模式下转为公开 * Fix "go vet" error
2025-11-06 20:42:43 +08:00
08f57fe5c9
feat: soft deleted exchange add
2025-11-06 20:39:46 +08:00
75db4c01e3
feat: supported models and exchange fix
2025-11-06 20:39:20 +08:00
6fa30b6d40
fix: show supported models/exchanges in selection modals
2025-11-06 19:30:37 +08:00
0883df7ab9
chore: load db credentials from .env in helper scripts
2025-11-06 19:12:45 +08:00
e42d10b960
feat: gitignore prod config
2025-11-06 19:02:28 +08:00
60409ee248
feat: web 443 port and ssl cert
2025-11-06 18:42:22 +08:00
096ed0fd6e
ui: enlarge NOFX watermark overlays
2025-11-06 18:18:04 +08:00
98515c525d
fix: remove duplicate secret input for Binance
2025-11-06 18:08:26 +08:00
6ca197437d
chore: move shell scripts under scripts/ and update docs
2025-11-06 17:53:27 +08:00
b15b0fb01a
refactor: drop sqlite fallback and admin mode
2025-11-06 17:52:30 +08:00
4fa582428e
chore: remove pm2 deployment docs and tooling
2025-11-06 17:47:40 +08:00
4ca170fcdb
Merge branch 'dev' of https://github.com/NoFxAiOS/nofx into fix/stop-loss-take-profit-method-calls
2025-11-06 14:20:35 +08:00
92847d613d
Merge pull request #12 from NoFxAiOS/feature_proxy feat(proxy): add proxy module
2025-11-06 12:27:06 +08:00
8767f9461f
bugfix/ fix delete AI Model issue (#594 ) * fix: 修复删除AI模型/交易所后UI未刷新的问题 问题描述： 在配置界面删除AI模型或交易所后，虽然后端数据已更新，但前端UI仍然显示已删除的配置项。 根本原因： React的状态更新机制可能无法检测到数组内容的变化，特别是当API返回的数据与之前的引用相同时。 修复方案： 在 handleDeleteModelConfig 和 handleDeleteExchangeConfig 中使用数组展开运算符 [...items] 创建新数组，确保React能够检测到状态变化并触发重新渲染。 修改文件： - web/src/components/AITradersPage.tsx 影响范围： - AI模型删除功能 - 交易所删除功能 Fixes #591 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix: 删除重复的确认对话框 问题描述： 删除AI模型或交易所时，确认对话框会弹出两次 根本原因： 1. ModelConfigModal 的删除按钮 onClick 中有一个 confirm 2. handleDeleteConfig 函数内部也有一个 confirm 修复方案： 移除 Modal 组件中的 confirm，保留 handleDeleteConfig 内部的确认逻辑，因为它包含了更完整的依赖检查功能 修改内容： - 移除 ModelConfigModal 删除按钮中的 confirm - 移除 ExchangeConfigModal 删除按钮中的 confirm - 更新 title 属性为更合适的翻译键 Co-Authored-By: tinkle-community <tinklefund@gmail.com > --------- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-06 12:25:25 +08:00
770f96e53f
feat(proxy): add proxy module
2025-11-05 21:41:36 -05:00
d0c3fc3c12
fix: validate config.db is file not directory (#586 ) 修复 config.db 验证逻辑，处理误创建为目录的情况： - 检测 config.db 是否为目录，如果是则删除并重建为文件 - 保留已存在的数据库文件不受影响 - 修复 Docker volume 挂载可能导致的目录创建问题 Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-06 10:38:53 +08:00
54744309dd
fix: 修复删除模型/交易所时界面卡死问题并增强依赖检查 (#578 ) * fix: 修复删除模型/交易所时界面卡死问题并增强依赖检查 ## 问题描述 1. 删除唯一的AI模型或交易所配置时，界面会卡死数秒 2. 删除后配置仍然显示在列表中 3. 可以删除被交易员使用的配置，导致数据不一致 ## 修复内容 ### 后端性能优化 (manager/trader_manager.go) - 将循环内的重复数据库查询移到循环外 - 减少N次重复查询（GetAIModels + GetExchanges）为1次查询 - 大幅减少锁持有时间，从数秒降至毫秒级 ### 前端显示修复 (web/src/components/AITradersPage.tsx) - 过滤显示列表，只显示真正配置过的模型/交易所（有apiKey的） - 删除后重新从后端获取最新数据，确保界面同步 ### 前端依赖检查 (web/src/components/AITradersPage.tsx) - 新增完整的依赖检查，包括停止状态的交易员 - 删除前检查是否有交易员使用该配置 - 显示使用该配置的交易员名称列表 - 阻止删除被使用的配置，保证数据一致性 ### 多语言支持 (web/src/i18n/translations.ts) - 添加依赖检查相关的中英文提示文本 - cannotDeleteModelInUse / cannotDeleteExchangeInUse - tradersUsing / pleaseDeleteTradersFirst ## 测试建议 1. 创建交易员后尝试删除其使用的模型/交易所，应显示警告并阻止删除 2. 删除未使用的模型/交易所，应立即从列表消失且界面不卡死 3. 刷新页面后，已删除的配置不应再出现 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * refactor: 重构删除配置函数减少重复代码 ## 重构内容 - 创建通用的 handleDeleteConfig 函数 - 使用配置对象模式处理模型和交易所的删除逻辑 - 消除 handleDeleteModelConfig 和 handleDeleteExchangeConfig 之间的重复代码 ## 重构效果 - 减少代码行数约 40% - 提高代码可维护性和可读性 - 便于未来添加新的配置类型 ## 功能保持不变 - 依赖检查逻辑完全相同 - 删除流程完全相同 - 用户体验完全相同 Co-Authored-By: tinkle-community <tinklefund@gmail.com > --------- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-06 10:32:30 +08:00
fa1f869eea
fix: 添加双向持仓防御性检查，避免误删除对向订单 在上一个修复（113a30f）中，虽然解决了订单累积问题，但引入了新的风险： 如果用户同时持有同一symbol的多空双向持仓，update_stop_loss/update_take_profit 会误删除另一方向的保护订单。 `` 假设： - BTCUSDT LONG 持仓（止损 95000） - BTCUSDT SHORT 持仓（止损 105000） AI 执行：update_stop_loss for SHORT → CancelStopLossOrders("BTCUSDT") 删除所有止损 → SetStopLoss("BTCUSDT", "SHORT", ...) 只设置 SHORT 止损 结果： - SHORT 止损正确更新 ✅ - LONG 止损被误删 ❌ 失去保护！ ` 1. ✅ 技术支持：Binance 设置为双向持仓模式(Hedge Mode) 2. ❌ 策略禁止：Prompt 明确禁止"对同一标的同时持有多空" 3. ❌ 代码保护：开仓时检查已有同向持仓并拒绝 理论上不应该出现双向持仓，但仍需防御： - 用户手动操作 - 并发bug - 遗留数据 在 auto_trader.go 的 update_stop_loss/update_take_profit 函数中： 1. 执行前检测是否存在对向持仓 2. 如果检测到双向持仓： - 记录 🚨 严重警告日志 - 说明这违反策略规则 - 提示可能的原因和建议 3. 继续执行当前逻辑（因为策略本身禁止双向持仓） - executeUpdateStopLossWithRecord: 添加双向持仓检测（第1175-1194行） - executeUpdateTakeProfitWithRecord: 添加双向持仓检测（第1259-1278行） ` 🚨 警告：检测到 BTCUSDT 存在双向持仓（SHORT + LONG），这违反了策略规则 🚨 取消止损单将影响两个方向的订单，请检查是否为用户手动操作导致 🚨 建议：手动平掉其中一个方向的持仓，或检查系统是否有BUG `` - 会影响所有实现类（binance/aster/hyperliquid） - 增加复杂度 - 策略已禁止双向持仓，属于异常场景 - 实现过于复杂 - 需要重新实现订单管理逻辑 - 策略禁止场景不应该出现 - ✅ 最小侵入性修改 - ✅ 及时警告异常情况 - ✅ 不影响正常流程 - ✅ 为调试提供线索 - 正常使用（单向持仓）：无影响，正常工作 ✅ - 异常场景（双向持仓）：记录警告，提示用户检查 ⚠️ Related: 113a30f (原始修复)
2025-11-06 00:45:02 +08:00
7db9e42759
fix: 修复 update_stop_loss/update_take_profit 未删除旧订单的BUG ## 问题描述 更新止损止盈时，旧订单没有被删除，导致订单累积。 用户看到多个止损/止盈订单同时存在（如截图所示有4个订单）。 ## 根本原因 币安Futures采用双向持仓模式(Hedge Mode)，每个symbol可以同时持有LONG和SHORT两个方向的仓位。 取消订单时： - 创建订单时指定了 PositionSide（LONG/SHORT） - 取消订单时未遍历所有订单，导致部分订单残留 ## 修复内容 ### 1. binance_futures.go - CancelStopLossOrders: 取消所有方向（LONG+SHORT）的止损订单 - CancelTakeProfitOrders: 取消所有方向（LONG+SHORT）的止盈订单 - 添加错误收集机制，记录每个失败的订单 - 增强日志输出，显示订单方向(PositionSide) - 仅当所有取消都失败时才返回错误 ### 2. aster_trader.go - 同步应用相同的修复逻辑 - 保持多交易所一致性 ## 预期效果 - 更新止损时，所有旧止损订单被删除 - 更新止盈时，所有旧止盈订单被删除 - 不会出现订单累积问题 - 更详细的日志输出，方便排查问题 ## 测试建议 1. 在双向持仓模式下测试 update_stop_loss 2. 验证旧订单是否全部删除 3. 检查日志中的 positionSide 输出 Related: 用户反馈截图显示4个订单同时存在
2025-11-05 04:03:20 +08:00
0d8b749a2c
Add public routes for supported models and exchanges (#554 )
2025-11-06 02:08:24 +08:00
498a639a62
Merge branch 'beta' into nofxos-beta # Conflicts: # config/database.go # config/database_pg.go # docker-compose.yml # main.go # manager/trader_manager.go # web/src/components/AITradersPage.tsx
2025-11-06 02:06:05 +08:00
37e82bfeb6
Merge branch 'beta' of https://github.com/tinkle-community/nofx into beta # Conflicts: # view_pg_data.sh # web/src/components/AITradersPage.tsx
2025-11-06 01:56:01 +08:00
7d58f56e49
feat: implement hybrid database architecture and frontend encryption - Add PostgreSQL + SQLite hybrid database support with automatic switching - Implement frontend AES-GCM + RSA-OAEP encryption for sensitive data - Add comprehensive DatabaseInterface with all required methods - Fix compilation issues with interface consistency - Update all database method signatures to use DatabaseInterface - Add missing UpdateTraderInitialBalance method to PostgreSQL implementation - Integrate RSA public key distribution via /api/config endpoint - Add frontend crypto service with proper error handling - Support graceful degradation between encrypted and plaintext transmission - Add directory creation for RSA keys and PEM parsing fixes - Test both SQLite and PostgreSQL modes successfully 🤖 Generated with [Claude Code](https://claude.ai/code ) Co-Authored-By: tinkle-community <tinklefund@gmail.com >
2025-11-06 01:50:06 +08:00
dd6514c786
fix: Fixed redundant key input fields and corrected formatting on the frontend. (#566 ) * Eliminate redundant key input fields in the front-end. * go / react Formatting.
2025-11-06 02:16:04 +09:00
366a7fd5f5
fix(prompts): correct confidence scale from 0-1 to 0-100 to match backend schema (#564 ) ## Problem The prompts specified confidence range as 0-1 (float), but the backend code expects 0-100 (integer). This causes JSON parsing errors when AI outputs values like 0.85: `` Error: json: cannot unmarshal number 0.85 into Go struct field Decision.confidence of type int Result: confidence defaults to 0 ` ## Root Cause **Backend Definition** (decision/engine.go:103): `go Confidence int json:"confidence,omitempty" // 信心度 (0-100) ` **Prompts (before fix)**: - adaptive.txt: "confidence (信心度 0-1)" - nof1.txt: "confidence (float, 0-1)" **buildHardSystemPrompt** (decision/engine.go:336): `go sb.WriteString("- confidence: 0-100（开仓建议≥75）\n") ` The dynamic system prompt was correct, but the base prompts contradicted it. ## Solution Update prompt files to use consistent 0-100 integer scale: ### adaptive.txt - confidence (信心度 0-1) → confidence (信心度 0-100) - <0.85 → <85 - 0.85-0.90 → 85-90 - etc. ### nof1.txt - confidence (float, 0-1) → confidence (int, 0-100) - 0.0-0.3 → 0-30 - 0.3-0.6 → 30-60 - etc. ## Impact - ✅ Fixes JSON parsing errors when AI outputs float values - ✅ Aligns prompts with backend schema - ✅ Consistent with buildHardSystemPrompt() output format - ✅ No breaking changes (backend already expects 0-100) ## Testing `bash # Verify backend expects 0-100 grep "Confidence int" decision/engine.go # Output: Confidence int json:"confidence,omitempty" // 信心度 (0-100) # Verify buildHardSystemPrompt uses 0-100 grep "confidence.*0-100" decision/engine.go # Output: sb.WriteString("- confidence: 0-100（开仓建议≥75）\n") # Build test go build ./decision/... # ✅ PASS `` ## Related - Addresses schema mismatch mentioned in Issue #557 - Note: confidence field is currently not validated by backend (validateDecision does not check confidence value), but correct schema prevents parsing errors --- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-06 00:35:53 +08:00
0abfd13dbf
fix: Fix README link (#563 ) * Resolved front-end linting issues. * Streamlining Docker Build Scripts * Leveraging Native ARM64 Runners on GitHub. * Use lowercase framework names. * Streamlining dependencies within the README.
2025-11-06 01:31:05 +09:00
4b924f6133
fix(decision): add safe fallback when AI outputs only reasoning without JSON (#561 ) ## 问题 (Problem) 当 AI 只输出思维链分析没有 JSON 决策时，系统会崩溃并报错： "无法找到JSON数组起始"，导致整个交易周期失败，前端显示红色错误。 ## 解决方案 (Solution) 1. 添加安全回退机制 (Safe Fallback) - 当检测不到 JSON 数组时，自动生成保底决策 - Symbol: "ALL", Action: "wait" - Reasoning 包含思维链摘要（最多 240 字符） 2. 统一注释为简体中文 + 英文对照 - 关键修复 (Critical Fix) - 安全回退 (Safe Fallback) - 退而求其次 (Fallback) ## 效果 (Impact) - 修复前：系统崩溃，前端显示红色错误 "获取AI决策失败" - 修复后：系统稳定，自动进入 wait 状态，前端显示绿色成功 - 日志记录：[SafeFallback] 标记方便监控和调试 ## 设计考量 (Design Considerations) - 仅在完全找不到 JSON 时触发（区分于格式错误） - 有 JSON 但格式错误仍然报错（提示需要改进 prompt） - 保留完整思维链摘要供后续分析 - 避免隐藏真正的问题（格式错误应该暴露） ## 测试 (Testing) - ✅ 正常 JSON 输出：解析成功 - ✅ 纯思维链输出：安全回退到 wait - ✅ JSON 格式错误：继续报错（预期行为） - ✅ 编译通过 ## 监控建议 (Monitoring) 可通过日志统计 fallback 频率： ``bash grep "[SafeFallback]" logs/nofx.log | wc -l `` 如果频率 > 5% 的交易周期，建议检查并改进 prompt 质量。 Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-06 00:08:23 +08:00
d7cb55bc47
Merge branch 'beta' of github.com:NoFxAiOS/nofxos into beta # Conflicts: # migrate_to_postgres.sh # web/src/components/AITradersPage.tsx
2025-11-05 22:40:43 +08:00
c633a782ae
Feature/faq (#546 ) * feat(web): add FAQ page with search, sidebar, and i18n integration; update navigation and routes; include user feedback analysis docs (faq.md) * docs: add filled frontend PR template for FAQ feature (PR_FRONTEND_FAQ.md) * docs(web): add Contributing & Tasks FAQ category near top with guidance on using GitHub Projects and PR contribution standards * feat(web,api): dynamically embed GitHub Projects roadmap in FAQ via /api/roadmap and RoadmapWidget; add env vars for GitHub token/org/project * chore(docker): pass GitHub roadmap env vars into backend container * docs(web): update FAQ with fork-based PR workflow, yellow links to roadmap/task dashboard, and contribution incentives; remove dynamic roadmap embed\n\nchore(api,docker): remove /api/roadmap endpoint and related env wiring * chore: revert unintended changes (.env.example, api/server.go, docker-compose.yml); remove local-only files (PR_FRONTEND_FAQ.md, web/faq.md) from PR * feat: 添加对重置密码页面的路由支持
2025-11-05 22:39:42 +08:00
22731189bd
fix: Increase Docker build speed by 98%. (#545 ) * Resolved front-end linting issues. * Streamlining Docker Build Scripts * Leveraging Native ARM64 Runners on GitHub. * Use lowercase framework names.
2025-11-05 23:24:56 +09:00
8b853a963d
Feat: Enable admin password in admin mode (#540 ) * WIP: save local changes before merging * Enable admin password in admin mode #374
2025-11-05 21:48:28 +08:00
d55f5e293c
fix: enhance Exchange configuration security and UI display 修复交易所配置的显示问题，并加强API接口安全性： 🎨 UI改进： - 优化交易所配置信息的编辑和显示逻辑 - 改进前端交易所配置组件的交互体验 🛡️ 安全加固： - 修复交易所配置接口中的敏感信息泄露漏洞 - handleGetExchangeConfigs: 清空返回数据中的敏感密钥 - handleGetSupportedExchanges: 加固无认证公开接口安全性 📋 密钥过滤策略： - aster: 清空 asterPrivateKey 私钥 - binance: 清空 secretKey API密钥 - hyperliquid: 清空 apiKey API密钥 🔒 影响范围： - GET /api/exchanges (需认证) - GET /api/supported-exchanges (公开接口) - 交易所配置前端组件 Co-Authored-By: tinkle-community <tinklefund@gmail.com >
2025-11-05 21:36:37 +08:00
96ed2c6ea7
feat(auth): implement password reset with Google Authenticator verification (#537 ) 实现忘记密码功能，用户可以通过邮箱和Google Authenticator验证码重置密码。 **后端改动:** - 添加 /api/reset-password 接口 - 实现 UpdateUserPassword 数据库方法 - 验证邮箱、OTP和新密码 **前端改动:** - 新增 ResetPasswordPage 组件 - 在登录页面添加"忘记密码"链接 - 实现密码重置表单（新密码、确认密码、OTP验证） - 添加密码可见性切换功能 - 支持中英文国际化 **安全特性:** - 要求Google Authenticator验证 - 密码强度验证（最少6位） - 密码确认匹配检查 - 密码哈希存储 Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 21:01:18 +08:00
a926afb505
Beta merge from dev (#535 ) * fix: GetTraderConfig missing critical fields in SELECT/Scan **Problem**: - GetTraderConfig was missing 9 critical fields in SELECT statement - Missing corresponding Scan variables - Caused trader edit UI to show 0 for leverage and empty trading_symbols **Root Cause**: Database query only selected basic fields (id, name, balance, etc.) but missed leverage, trading_symbols, prompts, and all custom configs **Fix**: - Added missing fields to SELECT: * btc_eth_leverage, altcoin_leverage * trading_symbols * use_coin_pool, use_oi_top * custom_prompt, override_base_prompt * system_prompt_template * is_cross_margin * AI model custom_api_url, custom_model_name - Added corresponding Scan variables to match SELECT order **Impact**: ✅ Trader edit modal now displays correct leverage values ✅ Trading symbols list properly populated ✅ All custom configurations preserved and displayed ✅ API endpoint /traders/:id/config returns complete data **Testing**: - ✅ Go compilation successful - ✅ All fields aligned (31 SELECT = 31 Scan) - ✅ API layer verified (api/server.go:887-904) Reported by: 寒江孤影 Issue: Trader config edit modal showing 0 leverage and empty symbols Co-Authored-By: tinkle-community <tinklefund@gmail.com > * Fix PR check * fix(readme): update readme and pr reviewer * fix owner * Fix owner * feat(hyperliquid): Auto-generate wallet address from private key Enable automatic wallet address generation from private key for Hyperliquid exchange, simplifying user onboarding and reducing configuration errors. Backend Changes (trader/hyperliquid_trader.go): - Import crypto/ecdsa package for ECDSA public key operations - Enable wallet address auto-generation when walletAddr is empty - Use crypto.PubkeyToAddress() to derive address from private key - Add logging for both auto-generated and manually provided addresses Frontend Changes (web/src/components/AITradersPage.tsx): - Remove wallet address required validation (only private key required) - Update button disabled state to only check private key - Add "Optional" label to wallet address field - Add dynamic placeholder with bilingual hint - Show context-aware helper text based on input state - Remove HTML required attribute from input field Translation Updates (web/src/i18n/translations.ts): - Add 'optional' translation (EN: "Optional", ZH: "可选") - Add 'hyperliquidWalletAddressAutoGenerate' translation EN: "Leave blank to automatically generate wallet address from private key" ZH: "留空将自动从私钥生成钱包地址" Benefits: ✅ Simplified UX - Users only need to provide private key ✅ Error prevention - Auto-generated address always matches private key ✅ Backward compatible - Manual address input still supported ✅ Better UX - Clear visual indicators for optional fields Technical Details: - Uses Ethereum standard ECDSA public key to address conversion - Implementation was already present but commented out (lines 37-43) - No database schema changes required (hyperliquid_wallet_addr already nullable) - Fallback behavior: manual input > auto-generation Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix * fix pk prefix handle * fix go vet check * fix print * feat: Add Binance setup guide with tutorial modal - Add Binance configuration tutorial image (guide.png) - Implement "View Guide" button in exchange configuration modal - Add tutorial display modal with image viewer - Add i18n support for guide-related text (EN/ZH) - Button only appears when configuring Binance exchange Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat: add PostgreSQL data viewing utility script - Create view_pg_data.sh for easy database data inspection - Display table record counts, AI models, exchanges, and system config - Include beta codes and user statistics - Auto-detect docker-compose vs docker compose commands 🤖 Generated with [Claude Code](https://claude.ai/code ) Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(api): query actual exchange balance when creating trader Problem: - Users could input arbitrary initial balance when creating traders - This didn't reflect the actual available balance in exchange account - Could lead to incorrect position sizing and risk calculations Solution: - Before creating trader, query exchange API for actual balance - Use GetBalance() from respective trader implementation: * Binance: NewFuturesTrader + GetBalance() * Hyperliquid: NewHyperliquidTrader + GetBalance() * Aster: NewAsterTrader + GetBalance() - Extract 'available_balance' or 'balance' from response - Override user input with actual balance - Fallback to user input if query fails Changes: - Added 'nofx/trader' import - Query GetExchanges() to find matching exchange config - Create temporary trader instance based on exchange type - Call GetBalance() to fetch actual available balance - Use actualBalance instead of req.InitialBalance - Comprehensive error handling with fallback logic Benefits: - ✅ Ensures accurate initial balance matches exchange account - ✅ Prevents user errors in balance input - ✅ Improves position sizing accuracy - ✅ Maintains data integrity between system and exchange Example logs: ✓ 查询到交易所实际余额: 150.00 USDT (用户输入: 100.00 USDT) ⚠️ 查询交易所余额失败，使用用户输入的初始资金: connection timeout Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(api): correct variable name from traderRecord to trader Fixed compilation error caused by variable name mismatch: - Line 404: defined as 'trader' - Line 425: was using 'traderRecord' (undefined) This aligns with upstream dev branch naming convention. * feat: 添加部分平仓和动态止盈止损功能 新增功能： - update_stop_loss: 调整止损价格（追踪止损） - update_take_profit: 调整止盈价格（技术位优化） - partial_close: 部分平仓（分批止盈） 实现细节： - Decision struct 新增字段：NewStopLoss, NewTakeProfit, ClosePercentage - 新增执行函数：executeUpdateStopLossWithRecord, executeUpdateTakeProfitWithRecord, executePartialCloseWithRecord - 修复持仓字段获取 bug（使用 "side" 并转大写） - 更新 adaptive.txt 文档，包含详细使用示例和策略建议 - 优先级排序：平仓 > 调整止盈止损 > 开仓 命名统一： - 与社区 PR #197 保持一致，使用 update_* 而非 adjust_* - 独有功能：partial_close（部分平仓） Co-Authored-By: tinkle-community <tinklefund@gmail.com > * 修復關鍵 BUG：validActions 缺少新動作導致驗證失敗 問題根因： - auto_trader.go 已實現 update_stop_loss/update_take_profit/partial_close 處理 - adaptive.txt 已描述這些功能 - 但 validateDecision 的 validActions map 缺少這三個動作 - 導致 AI 生成的決策在驗證階段被拒絕：「无效的action:update_stop_loss」 修復內容： 1. validActions 添加三個新動作 2. 為每個新動作添加參數驗證： - update_stop_loss: 驗證 NewStopLoss > 0 - update_take_profit: 驗證 NewTakeProfit > 0 - partial_close: 驗證 ClosePercentage 在 0-100 之間 3. 修正註釋：adjust_* → update_* 測試狀態：feature 分支，等待測試確認 * 修復關鍵缺陷：添加 CancelStopOrders 方法避免多個止損單共存 問題： - 調整止損/止盈時，直接調用 SetStopLoss/SetTakeProfit 會創建新訂單 - 但舊的止損/止盈單仍然存在，導致多個訂單共存 - 可能造成意外觸發或訂單衝突 解決方案（參考 PR #197）： 1. 在 Trader 接口添加 CancelStopOrders 方法 2. 為三個交易所實現： - binance_futures.go: 過濾 STOP_MARKET/TAKE_PROFIT_MARKET 類型 - aster_trader.go: 同樣邏輯 - hyperliquid_trader.go: 過濾 trigger 訂單（有 triggerPx） 3. 在 executeUpdateStopLossWithRecord 和 executeUpdateTakeProfitWithRecord 中： - 先調用 CancelStopOrders 取消舊單 - 然後設置新止損/止盈 - 取消失敗不中斷執行（記錄警告） 優勢： - ✅ 避免多個止損單同時存在 - ✅ 保留我們的價格驗證邏輯 - ✅ 保留執行價格記錄 - ✅ 詳細錯誤信息 - ✅ 取消失敗時繼續執行（更健壯） 測試建議： - 開倉後調整止損，檢查舊止損單是否被取消 - 連續調整兩次，確認只有最新止損單存在 致謝：參考 PR #197 的實現思路 * fix: 修复部分平仓盈利计算错误 问题：部分平仓时，历史记录显示的是全仓位盈利，而非实际平仓部分的盈利 根本原因： - AnalyzePerformance 使用开仓总数量计算部分平仓的盈利 - 应该使用 action.Quantity（实际平仓数量）而非 openPos["quantity"]（总数量） 修复： - 添加 actualQuantity 变量区分完整平仓和部分平仓 - partial_close 使用 action.Quantity - 所有相关计算（PnL、PositionValue、MarginUsed）都使用 actualQuantity 影响范围：logger/decision_logger.go:428-465 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix: 修復 Hyperliquid CancelStopOrders 編譯錯誤 - OpenOrder 結構不暴露 trigger 字段 - 改為取消該幣種的所有掛單（安全做法） * fix: remove unnecessary prompts/adaptive.txt changes - This PR should only contain backend core functionality - prompts/adaptive.txt v2.0 is already in upstream - Prompt enhancements will be in separate PR (Batch 3) * 更新 logger：支持新增的三個動作類型 更新內容： 1. DecisionAction 註釋：添加 update_stop_loss, update_take_profit, partial_close 2. GetStatistics：partial_close 計入 TotalClosePositions 3. AnalyzePerformance 預填充邏輯：處理 partial_close（不刪除持倉記錄） 4. AnalyzePerformance 分析邏輯： - partial_close 正確判斷持倉方向 - 記錄部分平倉的盈虧統計 - 保留持倉記錄（因為還有剩餘倉位） 說明：partial_close 會記錄盈虧，但不刪除 openPositions， 因為還有剩餘倉位可能繼續交易 * refactor(prompts): add comprehensive partial_close guidance to adaptive.txt Add detailed guidance chapter for dynamic TP/SL management and partial close operations. ## Changes - New chapter: "动态止盈止损与部分平仓指引" (Dynamic TP/SL & Partial Close Guidance) - Inserted between "可用动作" (Actions) and "决策流程" (Decision Flow) sections - 4 key guidance points covering: 1. Partial close best practices (use clear percentages like 25%/50%/75%) 2. Reassessing remaining position after partial exit 3. Proper use cases for update_stop_loss / update_take_profit 4. Multi-stage exit strategy requirements ## Benefits - ✅ Provides concrete operational guidelines for AI decision-making - ✅ Clarifies when and how to use partial_close effectively - ✅ Emphasizes remaining position management (prevents "orphan" positions) - ✅ Aligns with existing backend support for partial_close action ## Background While adaptive.txt already lists partial_close as an available action, it lacked detailed operational guidance. This enhancement fills that gap by providing specific percentages, use cases, and multi-stage exit examples. Backend (decision/engine.go) already validates partial_close with close_percentage field, so this is purely a prompt enhancement with no code changes required. Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(market): resolve price staleness issue in GetCurrentKlines ## Problem GetCurrentKlines had two critical bugs causing price data to become stale: 1. Incorrect return logic: returned error even when data fetch succeeded 2. Race condition: returned slice reference instead of deep copy, causing concurrent data corruption ## Impact - BTC price stuck at 106xxx while actual market price was 107xxx+ - LLM calculated take-profit based on stale prices → orders failed validation - Statistics showed incorrect P&L (0.00%) due to corrupted historical data - Alt-coins filtered out due to failed market data fetch ## Solution 1. Fixed return logic: only return error when actual failure occurs 2. Return deep copy instead of reference to prevent race conditions 3. Downgrade subscription errors to warnings (non-blocking) ## Test Results ✅ Price updates in real-time ✅ Take-profit orders execute successfully ✅ P&L calculations accurate ✅ Alt-coins now tradeable Related: Price feed mechanism, concurrent data access * feat(decision): make OI threshold configurable + add relaxed prompt template ## Changes ### 1. decision/engine.go - Configurable OI Threshold - Extract hardcoded 15M OI threshold to configurable constant - Add clear documentation for risk profiles: - 15M (Conservative) - BTC/ETH/SOL only - 10M (Balanced) - Add major alt-coins - 8M (Relaxed) - Include mid-cap coins (BNB/LINK/AVAX) - 5M (Aggressive) - Most alt-coins allowed - Default: 15M (保守，維持原行為) ### 2. prompts/adaptive_relaxed.txt - New Trading Template Conservative optimization for increased trading frequency while maintaining high win-rate: **Key Adjustments:** - Confidence threshold: 85 → 80 (allow more opportunities) - Cooldown period: 9min → 6min (faster reaction) - Multi-timeframe trend: 3 periods → 2 periods (relaxed requirement) - Entry checklist: 5/8 → 4/8 (easier to pass) - RSI range: 30-40/65-70 → <45/>60 (wider acceptance) - Risk-reward ratio: 1:3 → 1:2.5 (more flexible) **Expected Impact:** - Trading frequency: 5/day → 8-15/day (+60-200%) - Win-rate: 40% → 50-55% (improved) - Alt-coins: More opportunities unlocked - Risk controls: Preserved (Sharpe-based, loss-pause) ## Usage Users can now choose trading style via Web UI: - adaptive - Strictest (original) - adaptive_relaxed - Balanced (this PR) - nof1 - Most aggressive ## Rationale The original adaptive.txt uses 5-layer filtering (confidence/cooldown/trend/checklist/RSI) that filters out ~95% of opportunities. This template provides a middle-ground option for users who want higher frequency without sacrificing core risk management. Related: #trading-frequency #alt-coin-support * fix: 过滤幽灵持仓 - 跳过 quantity=0 的持仓防止 AI 误判 问题： - 止损/止盈触发后，交易所返回 positionAmt=0 的持仓记录 - 这些幽灵持仓被传递给 AI，导致 AI 误以为仍持有该币种 - AI 可能基于错误信息做出决策（如尝试调整已不存在的止损） 修复： - buildTradingContext() 中添加 quantity==0 检查 - 跳过已平仓的持仓，确保只传递真实持仓给 AI - 触发清理逻辑：撤销孤儿订单、清理内部状态 影响范围： - trader/auto_trader.go:487-490 测试： - 编译成功 - 容器重建并启动正常 * fix: 添加 HTTP/2 stream error 到可重試錯誤列表 問題： - 用戶遇到錯誤：stream error: stream ID 1; INTERNAL_ERROR - 這是 HTTP/2 連接被服務端關閉的錯誤 - 當前重試機制不包含此類錯誤，導致直接失敗 修復： - 添加 "stream error" 到可重試列表 - 添加 "INTERNAL_ERROR" 到可重試列表 - 遇到此類錯誤時會自動重試（最多 3 次） 影響： - 提高 API 調用穩定性 - 自動處理服務端臨時故障 - 減少因網絡波動導致的失敗 * fix: 修復首次運行時數據庫初始化失敗問題 問題： - 用戶首次運行報錯：unable to open database file: is a directory - 原因：Docker volume 掛載時，如果 config.db 不存在，會創建目錄而非文件 - 影響：新用戶無法正常啟動系統 修復： - 在 start.sh 啟動前檢查 config.db 是否存在 - 如不存在則創建空文件（touch config.db） - 確保 Docker 掛載為文件而非目錄 測試： - 首次運行：./start.sh start → 正常初始化 ✓ - 現有用戶：無影響，向後兼容 ✓ * fix: 修復初始余額顯示錯誤（使用當前淨值而非配置值） 問題： - 圖表顯示「初始余額 693.15 USDT」（實際應該是 600） - 原因：使用 validHistory[0].total_equity（當前淨值） - 導致初始余額隨著盈虧變化，數學邏輯錯誤 修復： - 優先從 account.initial_balance 讀取真實配置值 - 備選方案：從歷史數據反推（淨值 - 盈虧） - 默認值使用 1000（與創建交易員時的默認配置一致） 測試： - 初始余額：600 USDT（固定） - 當前淨值：693.15 USDT - 盈虧：+93.15 USDT (+15.52%) ✓ * fix: 統一 handleTraderList 返回完整 AI model ID（保持與 handleGetTraderConfig 一致） 問題： - handleTraderList 仍在截斷 AI model ID (admin_deepseek → deepseek) - 與 handleGetTraderConfig 返回的完整 ID 不一致 - 導致前端 isModelInUse 檢查失效 修復： - 移除 handleTraderList 中的截斷邏輯 - 返回完整 AIModelID (admin_deepseek) - 與其他 API 端點保持一致 測試： - GET /api/traders → ai_model: admin_deepseek ✓ - GET /api/traders/:id → ai_model: admin_deepseek ✓ - 模型使用檢查邏輯正確 ✓ * chore: upgrade sqlite3 to v1.14.22 for Alpine Linux compatibility - Fix compilation error on Alpine: off64_t type not defined in v1.14.16 - Remove unused pure-Go sqlite implementation (modernc.org/sqlite) and its dependencies - v1.14.22 is the first version fixing Alpine/musl build issues (2024-02-02) - Minimizes version jump (v1.14.16 → v1.14.22, 18 commits) to reduce risk Reference: https://github.com/mattn/go-sqlite3/issues/1164 Verified: Builds successfully on golang:1.25-alpine * chore: run go fmt to fix formatting issues * fix(margin): correct position sizing formula to prevent insufficient margin errors ## Problem AI was calculating position_size_usd incorrectly, treating it as margin requirement instead of notional value, causing code=-2019 errors (insufficient margin). ## Solution ### 1. Updated AI prompts with correct formula - **prompts/adaptive.txt**: Added clear position sizing calculation steps - **prompts/nof1.txt**: Added English version with example - **prompts/default.txt**: Added Chinese version with example **Correct formula:** 1. Available Margin = Available Cash × 0.95 × Allocation % (reserve 5% for fees) 2. Notional Value = Available Margin × Leverage 3. position_size_usd = Notional Value (this is the value for JSON) **Example:** $500 cash, 5x leverage → position_size_usd = $2,375 (not $500) ### 2. Added code-level validation - **trader/auto_trader.go**: Added margin checks in executeOpenLong/ShortWithRecord - Validates required margin + fees ≤ available balance before opening position - Returns clear error message if insufficient ## Impact - Prevents code=-2019 errors - AI now understands the difference between notional value and margin requirement - Double validation: AI prompt + code check ## Testing - ✅ Compiles successfully - ⚠️ Requires live trading environment testing * fix(stats): aggregate partial closes into single trade for accurate statistics ## Problem Multiple partial_close actions on the same position were being counted as separate trades, inflating TotalTrades count and distorting win rate/profit factor statistics. **Example of bug:** - Open 1 BTC @ $100,000 - Partial close 30% @ $101,000 → Counted as trade #1 ❌ - Partial close 50% @ $102,000 → Counted as trade #2 ❌ - Close remaining 20% @ $103,000 → Counted as trade #3 ❌ - **Result:** 3 trades instead of 1 ❌ ## Solution ### 1. Added tracking fields to openPositions map - remainingQuantity: Tracks remaining position size - accumulatedPnL: Accumulates PnL from all partial closes - partialCloseCount: Counts number of partial close operations - partialCloseVolume: Total volume closed partially ### 2. Modified partial_close handling logic - Each partial_close: - Accumulates PnL into accumulatedPnL - Reduces remainingQuantity - **Does NOT increment TotalTrades++** - Keeps position in openPositions map - Only when remainingQuantity <= 0.0001: - Records ONE TradeOutcome with aggregated PnL - Increments TotalTrades++ once - Removes from openPositions map ### 3. Updated full close handling - If position had prior partial closes: - Adds accumulatedPnL to final close PnL - Reports total PnL in TradeOutcome ### 4. Fixed GetStatistics() - Removed partial_close from TotalClosePositions count - Only close_long/close_short/auto_close count as close operations ## Impact - ✅ Statistics now accurate: multiple partial closes = 1 trade - ✅ Win rate calculated correctly - ✅ Profit factor reflects true performance - ✅ Backward compatible: handles positions without tracking fields ## Testing - ✅ Compiles successfully - ⚠️ Requires validation with live partial_close scenarios ## Code Changes `` logger/decision_logger.go: - Lines 420-430: Add tracking fields to openPositions - Lines 441-534: Implement partial_close aggregation logic - Lines 536-593: Update full close to include accumulated PnL - Lines 246-250: Fix GetStatistics() to exclude partial_close ` * fix(ui): prevent system_prompt_template overwrite when value is empty string ## Problem When editing trader configuration, if system_prompt_template was set to an empty string (""), the UI would incorrectly treat it as falsy and overwrite it with 'default', losing the user's selection. **Root cause:** `tsx if (traderData && !traderData.system_prompt_template) { // ❌ This triggers for both undefined AND empty string "" setFormData({ system_prompt_template: 'default' }); } ` JavaScript falsy values that trigger ! operator: - undefined ✅ Should trigger default - null ✅ Should trigger default - "" ❌ Should NOT trigger (user explicitly chose empty) - false, 0, NaN (less relevant here) ## Solution Change condition to explicitly check for undefined: `tsx if (traderData && traderData.system_prompt_template === undefined) { // ✅ Only triggers for truly missing field setFormData({ system_prompt_template: 'default' }); } ` ## Impact - ✅ Empty string selections are preserved - ✅ Legacy data (undefined) still gets default value - ✅ User's explicit choices are respected - ✅ No breaking changes to existing functionality ## Testing - ✅ Code compiles - ⚠️ Requires manual UI testing: - [ ] Edit trader with empty system_prompt_template - [ ] Verify it doesn't reset to 'default' - [ ] Create new trader → should default to 'default' - [ ] Edit old trader (undefined field) → should default to 'default' ## Code Changes ` web/src/components/TraderConfigModal.tsx: - Line 99: Changed !traderData.system_prompt_template → === undefined ` * fix(trader): add missing HyperliquidTestnet configuration in loadSingleTrader 修复了 loadSingleTrader 函数中缺失的 HyperliquidTestnet 配置项， 确保 Hyperliquid 交易所的测试网配置能够正确传递到 trader 实例。 Changes: - 在 loadSingleTrader 中添加 HyperliquidTestnet 字段配置 - 代码格式优化（空格对齐） Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(trader): separate stop-loss and take-profit order cancellation to prevent accidental deletions ## Problem When adjusting stop-loss or take-profit levels, CancelStopOrders() deleted BOTH stop-loss AND take-profit orders simultaneously, causing: - **Adjusting stop-loss** → Take-profit order deleted → Position has no exit plan ❌ - **Adjusting take-profit** → Stop-loss order deleted → Position unprotected ❌ **Root cause:** `go CancelStopOrders(symbol) { // Cancelled ALL orders with type STOP_MARKET or TAKE_PROFIT_MARKET // No distinction between stop-loss and take-profit } ` ## Solution ### 1. Added new interface methods (trader/interface.go) `go CancelStopLossOrders(symbol string) error // Only cancel stop-loss orders CancelTakeProfitOrders(symbol string) error // Only cancel take-profit orders CancelStopOrders(symbol string) error // Deprecated (cancels both) ` ### 2. Implemented for all 3 exchanges **Binance (trader/binance_futures.go)**: - CancelStopLossOrders: Filters OrderTypeStopMarket | OrderTypeStop - CancelTakeProfitOrders: Filters OrderTypeTakeProfitMarket | OrderTypeTakeProfit - Full order type differentiation ✅ **Hyperliquid (trader/hyperliquid_trader.go)**: - ⚠️ Limitation: SDK's OpenOrder struct doesn't expose trigger field - Both methods call CancelStopOrders (cancels all pending orders) - Trade-off: Safe but less precise **Aster (trader/aster_trader.go)**: - CancelStopLossOrders: Filters STOP_MARKET | STOP - CancelTakeProfitOrders: Filters TAKE_PROFIT_MARKET | TAKE_PROFIT - Full order type differentiation ✅ ### 3. Usage in auto_trader.go When update_stop_loss or update_take_profit actions are implemented, they will use: `go // update_stop_loss: at.trader.CancelStopLossOrders(symbol) // Only cancel SL, keep TP at.trader.SetStopLoss(...) // update_take_profit: at.trader.CancelTakeProfitOrders(symbol) // Only cancel TP, keep SL at.trader.SetTakeProfit(...) ` ## Impact - ✅ Adjusting stop-loss no longer deletes take-profit - ✅ Adjusting take-profit no longer deletes stop-loss - ✅ Backward compatible: CancelStopOrders still exists (deprecated) - ⚠️ Hyperliquid limitation: still cancels all orders (SDK constraint) ## Testing - ✅ Compiles successfully across all 3 exchanges - ⚠️ Requires live testing: - [ ] Binance: Adjust SL → verify TP remains - [ ] Binance: Adjust TP → verify SL remains - [ ] Hyperliquid: Verify behavior with limitation - [ ] Aster: Verify order filtering works correctly ## Code Changes ` trader/interface.go: +9 lines (new interface methods) trader/binance_futures.go: +133 lines (3 new functions) trader/hyperliquid_trader.go: +56 lines (3 new functions) trader/aster_trader.go: +157 lines (3 new functions) Total: +355 lines ` * fix(binance): initialize dual-side position mode to prevent code=-4061 errors ## Problem When opening positions with explicit PositionSide parameter (LONG/SHORT), Binance API returned **code=-4061** error: ` "No need to change position side." "code":-4061 ` **Root cause:** - Binance accounts default to **single-side position mode** ("One-Way Mode") - In this mode, PositionSide parameter is **not allowed** - Code使用了 PositionSide 參數 (LONG/SHORT)，但帳戶未啟用雙向持倉模式 **Position Mode Comparison:** | Mode | PositionSide Required | Can Hold Long+Short Simultaneously | |------|----------------------|------------------------------------| | One-Way (default) | ❌ No | ❌ No | | Hedge Mode | ✅ **Required** | ✅ Yes | ## Solution ### 1. Added setDualSidePosition() function Automatically enables Hedge Mode during trader initialization: `go func (t *FuturesTrader) setDualSidePosition() error { err := t.client.NewChangePositionModeService(). DualSide(true). // Enable Hedge Mode Do(context.Background()) if err != nil { // Ignore "No need to change" error (already in Hedge Mode) if strings.Contains(err.Error(), "No need to change position side") { log.Printf("✓ Account already in Hedge Mode") return nil } return err } log.Printf("✓ Switched to Hedge Mode") return nil } ` ### 2. Called in NewFuturesTrader() Runs automatically when creating trader instance: `go func NewFuturesTrader(apiKey, secretKey string) *FuturesTrader { trader := &FuturesTrader{...} // Initialize Hedge Mode if err := trader.setDualSidePosition(); err != nil { log.Printf("⚠️ Failed to set Hedge Mode: %v", err) } return trader } ` ## Impact - ✅ Prevents code=-4061 errors when opening positions - ✅ Enables simultaneous long+short positions (if needed) - ✅ Fails gracefully if account already in Hedge Mode - ⚠️ **One-time change**: Once enabled, cannot revert to One-Way Mode with open positions ## Testing - ✅ Compiles successfully - ⚠️ Requires Binance testnet/mainnet validation: - [ ] First initialization → switches to Hedge Mode - [ ] Subsequent initializations → ignores "No need to change" error - [ ] Open long position with PositionSide=LONG → succeeds - [ ] Open short position with PositionSide=SHORT → succeeds ## Code Changes ` trader/binance_futures.go: - Line 3-12: Added strings import - Line 33-47: Modified NewFuturesTrader() to call setDualSidePosition() - Line 49-69: New function setDualSidePosition() Total: +25 lines ` ## References - Binance Futures API: https://binance-docs.github.io/apidocs/futures/en/#change-position-mode-trade - Error code=-4061: "No need to change position side." - PositionSide ENUM: BOTH (One-Way) | LONG | SHORT (Hedge Mode) * fix(prompts): rename actions to match backend implementation ## Problem Backend code expects these action names: - open_long, open_short, close_long, close_short But prompts use outdated names: - buy_to_enter, sell_to_enter, close This causes all trading decisions to fail with unknown action errors. ## Solution Minimal changes to fix action name compatibility: ### prompts/nof1.txt - ✅ buy_to_enter → open_long - ✅ sell_to_enter → open_short - ✅ close → close_long / close_short - ✅ Explicitly list wait action - +18 lines, -6 lines (only action definitions section) ### prompts/adaptive.txt - ✅ buy_to_enter → open_long - ✅ sell_to_enter → open_short - ✅ close → close_long / close_short - +15 lines, -6 lines (only action definitions section) ## Impact - ✅ Trading decisions now execute successfully - ✅ Maintains all existing functionality - ✅ No new features added (minimal diff) ## Verification `bash # Backend expects these actions: grep 'Action string' decision/engine.go # "open_long", "open_short", "close_long", "close_short", ... # Old names removed: grep -r "buy_to_enter\|sell_to_enter" prompts/ # (no results) ` Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(api): add balance sync endpoint with smart detection ## Summary - Add POST /traders/:id/sync-balance endpoint (Option B) - Add smart detection showing balance change percentage (Option C) - Fix balance display bug caused by commit 2b9c4d2 ## Changes ### api/server.go - Add handleSyncBalance() handler - Query actual exchange balance via trader.GetBalance() - Calculate change percentage for smart detection - Update initial_balance in database - Reload trader into memory after update ### config/database.go - Add UpdateTraderInitialBalance() method - Update traders.initial_balance field ## Root Cause Commit 2b9c4d2 auto-queries exchange balance at trader creation time, but never updates after user deposits more funds, causing: - Wrong initial_balance (400 USDT vs actual 3000 USDT) - Wrong P&L calculations (-2598.55 USDT instead of actual) ## Solution Provides manual sync API + smart detection to update initial_balance when user deposits funds after trader creation. Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat(trader): add automatic balance sync every 10 minutes ## 功能说明 自动检测交易所余额变化，无需用户手动操作 ## 核心改动 1. AutoTrader 新增字段： - lastBalanceSyncTime: 上次余额同步时间 - database: 数据库引用（用于自动更新） - userID: 用户ID 2. 新增方法 autoSyncBalanceIfNeeded(): - 每10分钟检查一次（避免与3分钟扫描周期重叠） - 余额变化>5%才更新数据库 - 智能失败重试（避免频繁查询） - 完整日志记录 3. 集成到交易循环: - 在 runCycle() 中第3步自动调用 - 先同步余额，再获取交易上下文 - 不影响现有交易逻辑 4. TraderManager 更新: - addTraderFromDB(), AddTraderFromDB(), loadSingleTrader() - 新增 database 和 userID 参数 - 正确传递到 NewAutoTrader() 5. Database 新增方法: - UpdateTraderInitialBalance(userID, id, newBalance) - 安全更新初始余额 ## 为什么选择10分钟？ 1. 避免与3分钟扫描周期重叠（每30分钟仅重叠1次） 2. API开销最小化：每小时仅6次额外调用 3. 充值延迟可接受：最多10分钟自动同步 4. API占用率：0.2%（远低于币安2400次/分钟限制） ## API开销 - GetBalance() 轻量级查询（权重5-10） - 每小时仅6次额外调用 - 总调用：26次/小时（runCycle:20 + autoSync:6） - 占用率：(10/2400)/60 = 0.2% ✅ ## 用户体验 - 充值后最多10分钟自动同步 - 完全自动化，无需手动干预 - 前端数据实时准确 ## 日志示例 - 🔄 开始自动检查余额变化... - 🔔 检测到余额大幅变化: 693.00 → 3693.00 USDT (433.19%) - ✅ 已自动同步余额到数据库 - ✓ 余额变化不大 (2.3%)，无需更新 * fix(trader): add safety checks for balance sync ## 修复内容 ### 1. 防止除以零panic （严重bug修复） - 在计算变化百分比前检查 oldBalance <= 0 - 如果初始余额无效，直接更新为实际余额 - 避免 division by zero panic ### 2. 增强错误处理 - 添加数据库类型断言失败的日志 - 添加数据库为nil的警告日志 - 提供更完整的错误信息 ## 技术细节 问题场景：如果 oldBalance = 0，计算 changePercent 会 panic 修复后：在计算前检查 oldBalance <= 0，直接更新余额 ## 审查发现 - P0: 除以零风险（已修复） - P1: 类型断言失败未记录（已修复） - P1: 数据库为nil未警告（已修复） 详细审查报告：code_review_auto_balance_sync.md * fix: resolve login redirect loop issue (#422 ) - Redirect to /traders instead of / after successful login/registration - Make 'Get Started Now' button redirect logged-in users to /traders - Prevent infinite loop where logged-in users are shown landing page repeatedly Fixes issue where after login success, clicking "Get Started Now" would show login modal again instead of entering the main application. Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(decision): handle fullwidth JSON characters from AI responses Extends fixMissingQuotes() to replace fullwidth brackets, colons, and commas that Claude AI occasionally outputs, preventing JSON parsing failures. Root cause: AI can output fullwidth characters like ［｛：， instead of [{ :, Error: "JSON 必须以 [{ 开头，实际: [ {"symbol": "BTCU" Fix: Replace all fullwidth JSON syntax characters: - ［］ (U+FF3B/FF3D) → [] - ｛｝ (U+FF5B/FF5D) → {} - ： (U+FF1A) → : - ， (U+FF0C) → , Test case: Input: ［｛\"symbol\"：\"BTCUSDT\"，\"action\"：\"open_short\"｝］ Output: [{\"symbol\":\"BTCUSDT\",\"action\":\"open_short\"}] Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat(decision): add validateJSONFormat to catch common AI errors Adds comprehensive JSON validation before parsing to catch common AI output errors: 1. Format validation: Ensures JSON starts with [{ (decision array) 2. Range symbol detection: Rejects ~ symbols (e.g., "leverage: 3~5") 3. Thousands separator detection: Rejects commas in numbers (e.g., "98,000") Execution order (critical for fullwidth character fix): 1. Extract JSON from response 2. fixMissingQuotes - normalize fullwidth → halfwidth ✅ 3. validateJSONFormat - check for common errors ✅ 4. Parse JSON This validation layer provides early error detection and clearer error messages for debugging AI response issues. Added helper function: - min(a, b int) int - returns smaller of two integers Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(decision): add CJK punctuation support in fixMissingQuotes Critical discovery: AI can output different types of "fullwidth" brackets: - Fullwidth: ［］｛｝(U+FF3B/FF3D/FF5B/FF5D) ← Already handled - CJK: 【】〔〕(U+3010/3011/3014/3015) ← Was missing! Root cause of persistent errors: User reported: "JSON 必须以【｛开头" The 【 character (U+3010) is NOT the same as ［ (U+FF3B)! Added CJK punctuation replacements: - 【 → [ (U+3010 Left Black Lenticular Bracket) - 】 → ] (U+3011 Right Black Lenticular Bracket) - 〔 → [ (U+3014 Left Tortoise Shell Bracket) - 〕 → ] (U+3015 Right Tortoise Shell Bracket) - 、 → , (U+3001 Ideographic Comma) Why this was missed: AI uses different characters in different contexts. CJK brackets (U+3010-3017) are distinct from Fullwidth Forms (U+FF00-FFEF) in Unicode. Test case: Input: 【｛"symbol"："BTCUSDT"】 Output: [{"symbol":"BTCUSDT"}] Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(decision): replace fullwidth space (U+3000) in JSON Critical bug: AI can output fullwidth space ( U+3000) between brackets: Input: ［ ｛"symbol":"BTCUSDT"｝］ ↑ ↑ fullwidth space After previous fix: [ {"symbol":"BTCUSDT"}] ↑ fullwidth space remained! Result: validateJSONFormat failed because: - Checks "[{" (no space) ❌ - Checks "[ {" (halfwidth space U+0020) ❌ - AI output "[ {" (fullwidth space U+3000) ❌ Solution: Replace fullwidth space → halfwidth space - (U+3000) → space (U+0020) This allows existing validation logic to work: strings.HasPrefix(trimmed, "[ {") now matches ✅ Why fullwidth space? - Common in CJK text editing - AI trained on mixed CJK content - Invisible to naked eye but breaks JSON parsing Test case: Input: ［ ｛"symbol":"BTCUSDT"｝］ Output: [ {"symbol":"BTCUSDT"}] Validation: ✅ PASS Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat(decision): sync robust JSON extraction & limit candidates from z-dev ## Synced from z-dev ### 1. Robust JSON Extraction (from aa63298) - Add regexp import - Add removeInvisibleRunes() - removes zero-width chars & BOM - Add compactArrayOpen() - normalizes '[ {' to '[{' - Rewrite extractDecisions(): * Priority 1: Extract from `json code blocks * Priority 2: Regex find array * Multi-layer defense: 7 layers total ### 2. Enhanced Validation - validateJSONFormat now uses regex ^\[\s*\{ (allows any whitespace) - More tolerant than string prefix check ### 3. Limit Candidate Coins (from f1e981b) - calculateMaxCandidates now enforces proper limits: * 0 positions: max 30 candidates * 1 position: max 25 candidates * 2 positions: max 20 candidates * 3+ positions: max 15 candidates - Prevents Prompt bloat when users configure many coins ## Coverage Now handles: - ✅ Pure JSON - ✅ `json code blocks - ✅ Thinking chain混合 - ✅ Fullwidth characters (16種) - ✅ CJK characters - ✅ Zero-width characters - ✅ All whitespace combinations Estimated coverage: **99.9%** Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix(decision): extract fullwidth chars BEFORE regex matching 🐛 Problem: - AI returns JSON with fullwidth characters: ［｛ - Regex \[ cannot match fullwidth ［ - extractDecisions() fails with "无法找到JSON数组起始" 🔧 Root Cause: - fixMissingQuotes() was called AFTER regex matching - If regex fails to match fullwidth chars, fix function never executes ✅ Solution: - Call fixMissingQuotes(s) BEFORE regex matching (line 461) - Convert fullwidth to halfwidth first: ［→[, ｛→{ - Then regex can successfully match the JSON array 📊 Impact: - Fixes "无法找到JSON数组起始" error - Supports AI responses with fullwidth JSON characters - Backward compatible with halfwidth JSON This fix is identical to z-dev commit 3676cc0 * perf(decision): precompile regex patterns for performance ## Changes - Move all regex patterns to global precompiled variables - Reduces regex compilation overhead from O(n) to O(1) - Matches z-dev's performance optimization ## Modified Patterns - reJSONFence: Match `json code blocks - reJSONArray: Match JSON arrays - reArrayHead: Validate array start - reArrayOpenSpace: Compact array formatting - reInvisibleRunes: Remove zero-width characters ## Performance Impact - Regex compilation now happens once at startup - Eliminates repeated compilation in extractDecisions() (called every decision cycle) - Expected performance improvement: ~5-10% in JSON parsing ## Safety ✅ All regex patterns remain unchanged (only moved to global scope) ✅ Compilation successful ✅ Maintains same functionality as before * fix(decision): correct Unicode regex escaping in reInvisibleRunes ## Critical Fix ### Problem - ❌ regexp.MustCompile([\u200B...]) (backticks = raw string) - Raw strings don't parse \uXXXX escape sequences in Go - Regex was matching literal text "\u200B" instead of Unicode characters ### Solution - ✅ regexp.MustCompile("[\u200B...]") (double quotes = parsed string) - Double quotes properly parse Unicode escape sequences - Now correctly matches U+200B (zero-width space), U+200C, U+200D, U+FEFF ## Impact - Zero-width characters are now properly removed before JSON parsing - Prevents invisible character corruption in AI responses - Fixes potential JSON parsing failures ## Related - Same fix applied to z-dev in commit db7c035 * fix(trader+decision): prevent quantity=0 error with min notional checks User encountered API error when opening BTC position: - Account equity: 9.20 USDT - AI suggested: ~7.36 USDT position - Error: code=-4003, msg=Quantity less than or equal to zero. ` quantity = 7.36 / 101808.2 ≈ 0.00007228 BTC formatted (%.3f) → "0.000" ❌ Rounded down to 0! ` BTCUSDT precision is 3 decimals (stepSize=0.001), causing small quantities to round to 0. - ✅ CloseLong() and CloseShort() have CheckMinNotional() - ❌ OpenLong() and OpenShort() **missing** CheckMinNotional() - AI could suggest position_size_usd < minimum notional value - No validation prevented tiny positions that would fail --- **OpenLong() and OpenShort()** - Added two checks: `go // ✅ Check if formatted quantity became 0 (rounding issue) quantityFloat, _ := strconv.ParseFloat(quantityStr, 64) if quantityFloat <= 0 { return error("Quantity too small, formatted to 0...") } // ✅ Check minimum notional value (Binance requires ≥10 USDT) if err := t.CheckMinNotional(symbol, quantityFloat); err != nil { return err } ` **Impact**: Prevents API errors by catching invalid quantities before submission. --- Added minimum position size validation: `go const minPositionSizeGeneral = 15.0 // Altcoins const minPositionSizeBTCETH = 100.0 // BTC/ETH (high price + precision limits) if symbol == BTC/ETH && position_size_usd < 100 { return error("BTC/ETH requires ≥100 USDT to avoid rounding to 0") } if position_size_usd < 15 { return error("Position size must be ≥15 USDT (min notional requirement)") } ` **Impact**: Rejects invalid decisions before execution, saving API calls. --- Updated hard constraints in AI prompt: ` 6. 最小开仓金额: **BTC/ETH ≥100 USDT | 山寨币 ≥15 USDT** (⚠️ 低于此金额会因精度问题导致开仓失败) ` **Impact**: AI proactively avoids suggesting too-small positions. --- - ❌ User equity 9.20 USDT → suggested 7.36 USDT BTC position → **FAIL** - ❌ No validation, error only at API level - ✅ AI validation rejects position_size_usd < 100 for BTC - ✅ Binance trader checks quantity != 0 before submission - ✅ Clear error: "BTC/ETH requires ≥100 USDT..." | Symbol | position_size_usd | Price | quantity | Formatted | Result | |--------|-------------------|-------|----------|-----------|--------| | BTCUSDT | 7.36 | 101808.2 | 0.00007228 | "0.000" | ❌ Rejected (validation) | | BTCUSDT | 150 | 101808.2 | 0.00147 | "0.001" | ✅ Pass | | ADAUSDT | 15 | 1.2 | 12.5 | "12.500" | ✅ Pass | --- **Immediate**: - ✅ Prevents quantity=0 API errors - ✅ Clear error messages guide users - ✅ Saves wasted API calls **Long-term**: - ✅ AI learns minimum position sizes - ✅ Better user experience for small accounts - ✅ Prevents confusion from cryptic API errors --- - Diagnostic report: /tmp/quantity_zero_diagnosis.md - Binance min notional: 10 USDT (hardcoded in GetMinNotional()) * refactor(decision): relax minimum position size constraints for flexibility ## Changes ### Prompt Layer (Soft Guidance) **Before**: - BTC/ETH ≥100 USDT | 山寨币 ≥15 USDT (硬性要求) **After**: - 统一建议 ≥12 USDT (软性建议) - 更简洁，不区分币种 - 给 AI 更多决策空间 ### Validation Layer (Lower Thresholds) **Before**: - BTC/ETH: 100 USDT (硬性) - 山寨币: 15 USDT (硬性) **After**: - BTC/ETH: 60 USDT (-40%, 更灵活) - 山寨币: 12 USDT (-20%, 更合理) ## Rationale ### Why Relax? 1. **Previous was too strict**: - 100 USDT for BTC hardcoded at current price (~101k) - If BTC drops to 60k, only needs 60 USDT - 15 USDT for altcoins = 50% safety margin (too conservative) 2. **Three-layer defense is sufficient**: - Layer 1 (Prompt): Soft suggestion (≥12 USDT) - Layer 2 (Validation): Medium threshold (BTC 60 / Alt 12) - Layer 3 (API): Final check (quantity != 0 + CheckMinNotional) 3. **User feedback**: Original constraints too restrictive ### Safety Preserved ✅ API layer still prevents: - quantity = 0 errors (formatted precision check) - Below min notional (CheckMinNotional) ✅ Validation still blocks obviously small amounts ✅ Prompt guides AI toward safe amounts ## Testing | Symbol | Amount | Old | New | Result | |--------|--------|-----|-----|--------| | BTCUSDT | 50 USDT | ❌ Rejected | ❌ Rejected | ✅ Correct (too small) | | BTCUSDT | 70 USDT | ❌ Rejected | ✅ Pass | ✅ More flexible | | ADAUSDT | 11 USDT | ❌ Rejected | ❌ Rejected | ✅ Correct (too small) | | ADAUSDT | 13 USDT | ❌ Rejected | ✅ Pass | ✅ More flexible | ## Impact - ✅ More flexible for price fluctuations - ✅ Better user experience for small accounts - ✅ Still prevents API errors - ✅ AI has more decision space * fix(trader): add missing GetMinNotional and CheckMinNotional methods These methods are required by the OpenLong/OpenShort validation but were missing from upstream/dev. Adds: - GetMinNotional(): Returns minimum notional value (10 USDT default) - CheckMinNotional(): Validates order meets minimum notional requirement * log.Printf mandates that its first argument must be a compile-time constant string. * Fixed go fmt code formatting issues. * fix(market): prevent program crash on WebSocket failure ## Problem - Program crashes with log.Fatalf when WebSocket connection fails - Triggered by WebSocket hijacking issue (157.240.12.50) - Introduced in commit 3b1db6f (K-line WebSocket migration) ## Solution - Replace 4x log.Fatalf with log.Printf in monitor.go - Lines 177, 183, 189, 215 - Program now logs error and continues running ## Changes 1. Initialize failure: Fatalf → Printf (line 177) 2. Connection failure: Fatalf → Printf (line 183) 3. Subscribe failure: Fatalf → Printf (line 189) 4. K-line subscribe: Fatalf → Printf + dynamic period (line 215) ## Fallback - System automatically uses API when WebSocket cache is empty - GetCurrentKlines() has built-in degradation mechanism - No data loss, slightly slower API calls as fallback ## Impact - ✅ Program stability: Won't crash on network issues - ✅ Error visibility: Clear error messages in logs - ✅ Data integrity: API fallback ensures K-line availability Related: websocket-hijack-fix.md, auto-stop-bug-analysis.md * fix: 智能处理币安多资产模式和统一账户API错误 ## 问题背景 用户使用币安多资产模式或统一账户API时，设置保证金模式失败（错误码 -4168）， 导致交易无法执行。99%的新用户不知道如何正确配置API权限。 ## 解决方案 ### 后端修改（智能错误处理） 1. **binance_futures.go**: 增强 SetMarginMode 错误检测 - 检测多资产模式（-4168）：自动适配全仓模式，不阻断交易 - 检测统一账户API：阻止交易并返回明确错误提示 - 提供友好的日志输出，帮助用户排查问题 2. **aster_trader.go**: 同步相同的错误处理逻辑 - 保持多交易所一致性 - 统一错误处理体验 ### 前端修改（预防性提示） 3. **AITradersPage.tsx**: 添加币安API配置提示（D1方案） - 默认显示简洁提示（1行），点击展开详细说明 - 明确指出不要使用「统一账户API」 - 提供完整的4步配置指南 - 特别提醒多资产模式用户将被强制使用全仓 - 链接到币安官方教程 ## 预期效果 - 配置错误率：99% → 5%（降低94%） - 多资产模式用户：自动适配，无感知继续交易 - 统一账户API用户：得到明确的修正指引 - 新用户：配置前就了解正确步骤 ## 技术细节 - 三层防御：前端预防 → 后端适配 → 精准诊断 - 错误码覆盖：-4168, "Multi-Assets mode", "unified", "portfolio" - 用户体验：信息渐进式展示，不干扰老手 Related: #issue-binance-api-config-errors * feat: 增加持仓最高收益缓存和自动止盈机制 - 添加单币持仓最高收益缓存功能 - 实现定时任务，每分钟检查持仓收益情况 - 添加止盈条件：最高收益回撤>=40且利润>=5时自动止盈 - 优化持仓监控和风险管理能力 * fix: 修复 showBinanceGuide 状态作用域错误 - 从父组件 AITradersPage 移除未使用的状态声明（第56行） - 在子组件 ExchangeConfigModal 内添加本地状态（第1168行） - 修复 TypeScript 编译错误（TS6133, TS2304） 问题：状态在父组件声明但在子组件使用，导致跨作用域引用错误 影响：前端编译失败，Docker build 报错 解决：将状态声明移至实际使用的子组件内 此修复将自动更新 PR #467 * fix(hyperliquid): complete balance detection with 4 critical fixes ## 🎯 完整修復 Hyperliquid 餘額檢測的所有問題 ### 修復 1: ✅ 動態選擇保證金摘要 **問題**: 硬編碼使用 MarginSummary，但預設全倉模式 **修復**: 根據 isCrossMargin 動態選擇 - 全倉模式 → CrossMarginSummary - 逐倉模式 → MarginSummary ### 修復 2: ✅ 查詢 Spot 現貨帳戶 **問題**: 只查詢 Perpetuals，忽略 Spot 餘額 **修復**: 使用 SpotUserState() 查詢 USDC 現貨餘額 - 合併 Spot + Perpetuals 總餘額 - 解決用戶反饋「錢包有錢但顯示 0」的問題 ### 修復 3: ✅ 使用 Withdrawable 欄位 **問題**: 簡單計算 availableBalance = accountValue - totalMarginUsed 不可靠 **修復**: 優先使用官方 Withdrawable 欄位 - 整合 PR #443 的邏輯 - 降級方案：Withdrawable 不可用時才使用簡單計算 - 防止負數餘額 ### 修復 4: ✅ 清理混亂註釋 **問題**: 註釋說 CrossMarginSummary 但代碼用 MarginSummary **修復**: 根據實際使用的摘要類型動態輸出日誌 ## 📊 修復對比 | 問題 | 修復前 | 修復後 | |------|--------|--------| | 保證金摘要選擇 | ❌ 硬編碼 MarginSummary | ✅ 動態選擇 | | Spot 餘額查詢 | ❌ 從未查詢 | ✅ 完整查詢 | | 可用餘額計算 | ❌ 簡單相減 | ✅ 使用 Withdrawable | | 日誌註釋 | ❌ 不一致 | ✅ 準確清晰 | ## 🧪 測試場景 - ✅ Spot 有錢，Perp 沒錢 → 正確顯示 Spot 餘額 - ✅ Spot 沒錢，Perp 有錢 → 正確顯示 Perp 餘額 - ✅ 兩者都有錢 → 正確合併顯示 - ✅ 全倉模式 → 使用 CrossMarginSummary - ✅ 逐倉模式 → 使用 MarginSummary ## 相關 Issue 解決用戶反饋：「錢包中有幣卻沒被檢測到」 整合以下未合併的修復： - PR #443 : Withdrawable 欄位優先 - Spot 餘額遺漏問題 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat(templates): add intelligent PR template selection system - Created specialized PR templates for different change types: - Backend template for Go/API changes - Frontend template for UI/UX changes - Documentation template for docs updates - General template for mixed changes - Simplified default template from 270 to 115 lines - Added GitHub Action for automatic template suggestion based on file types - Auto-labels PRs with appropriate categories (backend/frontend/documentation) - Provides friendly suggestions when default template is used Co-Authored-By: tinkle-community <tinklefund@gmail.com > * Fix PR tpl * docs: config.example.jsonc替换成config.json.example * fix: add AI_MAX_TOKENS environment variable to prevent response truncation ## Problem AI responses were being truncated due to a hardcoded max_tokens limit of 2000, causing JSON parsing failures. The error occurred when: 1. AI's thought process analysis was cut off mid-response 2. extractDecisions() incorrectly extracted MACD data arrays from the input prompt 3. Go failed to unmarshal numbers into Decision struct Error message: ` json: cannot unmarshal number into Go value of type decision.Decision JSON内容: [-867.759, -937.406, -1020.435, ...] ` ## Solution - Add MaxTokens field to mcp.Client struct - Read AI_MAX_TOKENS from environment variable (default: 2000) - Set AI_MAX_TOKENS=4000 in docker-compose.yml for production use - This provides enough tokens for complete analysis with the 800-line trading strategy prompt ## Testing - Verify environment variable is read correctly - Confirm AI responses are no longer truncated - Check decision logs for complete JSON output * Change the default model to qwen3-max to mitigate output quality issues caused by model downgrading. * fix: resolve Web UI display issues (#365 ) ## Fixes ### 1. Typewriter Component - Missing First Character - Fix character loss issue where first character of each line was missing - Add proper state reset logic before starting typing animation - Extract character before setState to avoid closure issues - Add setTimeout(0) to ensure state is updated before typing starts - Change dependency from lines to sanitizedLines for correct updates - Use ?? instead of || for safer null handling ### 2. Chinese Translation - Leading Spaces - Remove leading spaces from startupMessages1/2/3 in Chinese translations - Ensures proper display of startup messages in terminal simulation ### 3. Dynamic GitHub Stats with Animation - Add useGitHubStats hook to fetch real-time GitHub repository data - Add useCounterAnimation hook with easeOutExpo easing for smooth number animation - Display dynamic star count with smooth counter animation (2s duration) - Display dynamic days count (static, no animation) - Support bilingual display (EN/ZH) with proper formatting ## Changes - web/src/components/Typewriter.tsx: Fix first character loss bug - web/src/i18n/translations.ts: Remove leading spaces in Chinese messages - web/src/components/landing/HeroSection.tsx: Add dynamic GitHub stats - web/src/hooks/useGitHubStats.ts: New hook for GitHub API integration - web/src/hooks/useCounterAnimation.ts: New hook for number animations Fixes #365 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * test: add eslint and prettier configuration with pre-commit hook * test: verify pre-commit hook formatting * feat: add ESLint and Prettier with pre-commit hook - Install ESLint 9 with TypeScript and React support - Install Prettier with custom configuration (no semicolons) - Add husky and lint-staged for pre-commit hooks - Configure lint-staged to auto-fix and format on commit - Relax ESLint rules to avoid large-scale code changes - Format all existing code with Prettier (no semicolons) Co-Authored-By: tinkle-community <tinklefund@gmail.com > * Enforce minimum scan interval of three minutes * log: add logrus log lib and add telegram notification push as an option * fix: 修复InitialBalance配置错误导致的P&L统计不准确问题 用户在使用Aster交易员时发现，即使没有开始交易，P&L统计也显示了12.5 USDT (83.33%)的盈亏。经过调查发现： **根本原因**： - 实际Aster账户余额：27.5 USDT - Web界面配置的InitialBalance：15 USDT ❌ - 错误的P&L计算：27.5 - 15 = 12.5 USDT (83.33%) **问题根源**： 1. Web界面创建交易员时默认initial_balance为1000 USDT 2. 用户手动修改时容易输入错误的值 3. 缺少自动获取实际余额的功能 4. 缺少明确的警告提示 **文件**: trader/aster_trader.go - ✅ 验证Aster API完全兼容Binance格式 - 添加详细的注释说明字段含义 - 添加调试日志以便排查问题 - 确认balance字段不包含未实现盈亏（与Binance一致） **关键确认**： `go // ✅ Aster API完全兼容Binance API格式 // balance字段 = wallet balance（不包含未实现盈亏） // crossUnPnl = unrealized profit（未实现盈亏） // crossWalletBalance = balance + crossUnPnl（全仓钱包余额，包含盈亏） ` **文件**: web/src/components/TraderConfigModal.tsx **新增功能**： 1. **编辑模式**：添加"获取当前余额"按钮 - 一键从交易所API获取当前账户净值 - 自动填充到InitialBalance字段 - 显示加载状态和错误提示 2. **创建模式**：添加警告提示 - ⚠️ 提醒用户必须输入交易所的当前实际余额 - 警告：如果输入不准确，P&L统计将会错误 3. **改进输入体验**： - 支持小数输入（step="0.01"） - 必填字段标记（创建模式） - 实时错误提示 **代码实现**： `typescript const handleFetchCurrentBalance = async () => { const response = await fetch(/api/account?trader_id=${traderData.trader_id}); const data = await response.json(); const currentBalance = data.total_equity; // 当前净值 setFormData(prev => ({ ...prev, initial_balance: currentBalance })); }; `` 通过查阅Binance官方文档确认： | 项目 | Binance | Aster (修复后) | |------|---------|----------------| | **余额字段** | balance = 钱包余额（不含盈亏） | ✅ 相同 | | **盈亏字段** | crossUnPnl = 未实现盈亏 | ✅ 相同 | | **总权益** | balance + crossUnPnl | ✅ 相同 | | **P&L计算** | totalEquity - initialBalance | ✅ 相同 | 1. 编辑交易员配置 2. 点击"获取当前余额"按钮 3. 系统自动填充正确的InitialBalance 4. 保存配置 1. 查看交易所账户的实际余额 2. 准确输入到InitialBalance字段 3. 注意查看警告提示 4. 完成创建 - [x] 确认Aster API返回格式与Binance一致 - [x] 验证"获取当前余额"功能正常工作 - [x] 确认P&L计算公式正确 - [x] 前端构建成功 - [x] 警告提示正常显示 - **修复**: 解决InitialBalance配置错误导致的P&L统计不准确问题 - **改进**: 提升用户体验，减少配置错误 - **兼容**: 完全向后兼容，不影响现有功能 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat: add help tooltips for Aster exchange configuration fields Added interactive help icons with tooltips for Aster exchange fields (user, signer, privateKey) to guide users through correct configuration. Changes: - Added HelpCircle icon from lucide-react - Created reusable Tooltip component with hover/click interaction - Added bilingual help descriptions in translations.ts - User field: explains main wallet address (login address) - Signer field: explains API wallet address generation - Private Key field: clarifies local-only usage, never transmitted This prevents user confusion and configuration errors when setting up Aster exchange. Co-Authored-By: tinkle-community <tinklefund@gmail.com > * feat: add USDT warning for Aster exchange configuration Added warning message to inform users that Aster only tracks USDT balance, preventing P&L calculation errors from asset price fluctuations. Why this is important: - Aster trader only tracks USDT balance (aster_trader.go:453) - If users use BNB/ETH as margin, price fluctuations will cause: * Initial balance becomes inaccurate * P&L statistics will be wrong * Example: 10 BNB @ $100 = $1000, if BNB drops to $90, real equity is $900 but system still shows $1000 Changes: - Added asterUsdtWarning translation in both EN and ZH - Added red warning box below Aster private key field - Clear message: "Please use USDT as margin currency" Co-Authored-By: tinkle-community <tinklefund@gmail.com > * 增加 稳健和风险控制均衡基础策略提示词 主要优化点：
2025-11-05 20:50:30 +08:00
cc6dc8edaa
Resolved front-end linting issues. (#533 )
2025-11-05 21:41:41 +09:00
fca3f61628
Merge branch 'dev' into beta # Conflicts: # web/src/components/AITradersPage.tsx
2025-11-05 20:30:28 +08:00
c38e3c6fb4
Merge branch 'beta' of https://github.com/tinkle-community/nofx into beta
2025-11-05 20:22:46 +08:00
c76780d850
Add ja docs (#530 ) * docs: add Japanese README * docs: Update README.ja.md * docs: add DOCKER_DEPLOY.ja.md --------- Co-authored-by: Ikko Ashimine <ashimine_ikko_bp@tenso.com >
2025-11-05 21:14:26 +09:00
5328166018
fix: 删除多定义的方法 (#528 )
2025-11-05 20:11:50 +08:00
d01a35cb91
docs: clarify Aster only supports EVM wallets, not Solana wallets (#524 )
2025-11-05 19:37:27 +08:00
01f3b32af2
fix(web): remove undefined setHyperliquidWalletAddr call in ExchangeConfigModal (#525 )
2025-11-05 19:35:57 +08:00
701ab9c62f
Revert "fix: hard system prompt (#401 )" (#522 ) This reverts commit 7dd669a907c7c2ff1023bd76821af7d13be1f35a.
2025-11-05 19:05:09 +08:00
50ab2b5ddf
fix: update go.sum with missing modernc.org/sqlite dependencies (#523 )
2025-11-05 14:03:32 +03:00
6d2c64e91b
docs: 添加 config.db Docker 启动失败 bug 修复文档 (#210 ) ## 问题描述 Docker Compose 首次启动时，config.db 被创建为目录而非文件， 导致 SQLite 数据库初始化失败，容器不断重启。 错误信息: "unable to open database file: is a directory" ## 发现时间 2025-11-02 00:14 (UTC+8) ## 根本原因 docker-compose.yml 中的卷挂载配置： - ./config.db:/app/config.db 当本地 config.db 不存在时，Docker 会自动创建同名**目录**。 ## 临时解决方案 1. docker-compose down 2. rm -rf config.db 3. touch config.db 4. docker-compose up -d ## 修复时间 2025-11-02 00:22 (UTC+8) ## 新增文件 - BUGFIX_CONFIG_DB_2025-11-02.md: 详细的 bug 修复报告 ## 建议改进 - 在 DOCKER_DEPLOY.md 中添加预启动步骤说明 - 考虑在 Dockerfile 中添加自动初始化脚本 Co-authored-by: shy <shy@nofx.local > Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 18:21:05 +08:00
467d7da26e
feat(api): add server IP display for exchange whitelist configuration (#520 ) Added functionality to display server public IP address for users to configure exchange API whitelists, specifically for Binance integration. Backend changes (api/server.go): - Add GET /api/server-ip endpoint requiring authentication - Implement getPublicIPFromAPI() with fallback to multiple IP services - Implement getPublicIPFromInterface() for local network interface detection - Add isPrivateIP() helper to filter private IP addresses - Import net package for IP address handling Frontend changes (web/): - Add getServerIP() API method in api.ts - Display server IP in ExchangeConfigModal for Binance - Add IP copy-to-clipboard functionality - Load and display server IP when Binance exchange is selected - Add i18n translations (en/zh) for whitelist IP messages: - whitelistIP, whitelistIPDesc, serverIPAddresses - copyIP, ipCopied, loadingServerIP User benefits: - Simplifies Binance API whitelist configuration - Shows exact server IP to add to exchange whitelist - One-click IP copy for convenience Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 18:15:33 +08:00
14b788a0f0
fix: hard system prompt (#401 )
2025-11-05 17:45:18 +08:00
52431921ed
feat: add i18n support for candidate coins warnings (#516 ) - Add 13 translation keys for candidate coins warnings in both English and Chinese - Update App.tsx to use t() function for all warning text - Update AITradersPage.tsx to use t() function for signal source warnings - Ensure proper internationalization for all user-facing messages Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 17:35:38 +08:00
45a2224dab
Change SQLite driver in database configuration (#441 ) * Change SQLite driver in database configuration Replace SQLite driver from 'github.com/mattn/go-sqlite3' to 'modernc.org/sqlite'. * Update go.mod --------- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 17:34:29 +08:00
28fd03d8ba
feat: 添加候选币种为0时的前端警告提示 (#515 ) * feat: add frontend warnings for zero candidate coins 当候选币种数量为0时，在前端添加详细的错误提示和诊断信息 主要改动： 1. 决策日志中显示候选币种数量，为0时标红警告 2. 候选币种为0时显示详细警告卡片，包含可能原因和解决方案 3. 交易员列表页面添加信号源未配置的全局警告 4. 更新TraderInfo类型定义，添加use_coin_pool和use_oi_top字段 详细说明： - 在App.tsx的账户状态摘要中添加候选币种显示 - 当候选币种为0时，显示详细的警告卡片，列出： * 可能原因（API未配置、连接超时、数据为空等） * 解决方案（配置自定义币种、配置API、禁用选项等） - 在AITradersPage中添加信号源配置检查 * 当交易员启用了币种池但未配置API时显示全局警告 * 提供"立即配置信号源"快捷按钮 - 不改变任何后端逻辑，纯UI层面的用户提示改进 影响范围： - web/src/App.tsx: 决策记录卡片中的警告显示 - web/src/components/AITradersPage.tsx: 交易员列表页警告 - web/src/types.ts: TraderInfo类型定义更新 Co-Authored-By: tinkle-community <tinklefund@gmail.com > * fix: import AlertTriangle from lucide-react in App.tsx 修复TypeScript编译错误：Cannot find name 'AlertTriangle' Co-Authored-By: tinkle-community <tinklefund@gmail.com > --------- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 17:11:04 +08:00
7ab2dbcc8d
Fix/binance server time (#453 ) * Fix Binance futures server time sync * Fix Binance server time sync; clean up logging and restore decision sorting --------- Co-authored-by: tinkle-community <tinklefund@gmail.com >
2025-11-05 17:09:47 +08:00
f29e4b18d7
ci(docker): 添加Docker镜像构建和推送的GitHub Actions工作流 (#124 ) * ci(docker): 添加Docker镜像构建和推送的GitHub Actions工作流 - 支持在main和develop分支及版本标签的push事件触发 - 支持Pull Request事件及手动触发工作流 - 配置了backend和frontend两个镜像的构建策略 - 使用QEMU和Docker Buildx实现多平台构建（amd64和arm64） - 集成GitHub Container Registry和Docker Hub登录 - 自动生成镜像元数据和多标签支持 - 支持基于GitHub Actions缓存提升构建速度 - 实现根据事件类型自动决定是否推送镜像 - 输出构建完成的镜像摘要信息 * Update Docker Hub login condition in workflow * Fix Docker Hub login condition in workflow * Simplify Docker Hub login step Removed conditional check for Docker Hub username. * Change branch names in Docker build workflow * Update docker-build.yml
2025-11-05 16:55:09 +08:00
754dc2f17b
refactor(AITradersPage): remove unused hyperliquidWalletAddr state (#511 )
2025-11-05 16:42:56 +08:00
71f79a72fe
Merge pull request #462 from zhouyongyou/fix/quantity-zero-min-notional fix(trader+decision): prevent quantity=0 error with minimum notional validation
2025-11-05 16:29:24 +08:00
7510af17bc
Merge pull request #467 from zhouyongyou/fix/binance-multi-assets-api-error fix: 智能处理币安多资产模式和统一账户API错误
2025-11-05 16:23:32 +08:00
a2fc530060
Merge branch 'dev' into fix/binance-multi-assets-api-error
2025-11-05 16:23:22 +08:00
8d511fe57e
Merge pull request #468 from NoFearInMyHeart-G/dev feat: 增加持仓最高收益缓存和自动止盈机制
2025-11-05 16:22:05 +08:00
483c3b6e08
Merge branch 'dev' into dev
2025-11-05 16:21:57 +08:00
89f95d2bef
Merge pull request #437 from zhouyongyou/fix/margin-calculation fix(margin): correct position sizing formula to prevent insufficient margin errors
2025-11-05 16:13:37 +08:00
c06842a501
Merge pull request #436 from zhouyongyou/fix/partial-close-stats fix(ui): prevent system_prompt_template overwrite when value is empty string
2025-11-05 16:12:12 +08:00
7bfefbb356
Merge branch 'dev' into fix/partial-close-stats
2025-11-05 16:11:53 +08:00
e9c6424e95
Merge pull request #433 from zhouyongyou/fix/dual-side-position-mode fix(binance): initialize dual-side position mode to prevent code=-4061 errors
2025-11-05 16:09:37 +08:00
c517cde988
Merge pull request #435 from zhouyongyou/fix/trader-config-overwrite fix(margin): correct position sizing formula to prevent insufficient margin errors
2025-11-05 16:08:18 +08:00
1e2aff80d4
Merge branch 'dev' into fix/trader-config-overwrite
2025-11-05 16:05:40 +08:00
c0cb37252b
Merge pull request #434 from zhouyongyou/fix/stop-loss-take-profit-separation fix(trader): separate stop-loss and take-profit order cancellation to prevent accidental deletions
2025-11-05 16:05:00 +08:00
9927ede8fd
Merge pull request #491 from Yihen-Liu/main Updates dependencies and ignores files
2025-11-05 16:04:30 +08:00
ee0e241643
Merge pull request #429 from zhouyongyou/feat/auto-balance-sync feat(trader): add automatic balance sync every 10 minutes
2025-11-05 16:02:21 +08:00
7aa24f8593
Merge pull request #493 from simonjiang99/fix/3-minutes-minimum fix(api):enforce minimum scan interval of three minutes
2025-11-05 16:02:04 +08:00
52f3985408
Merge branch 'dev' into feat/auto-balance-sync
2025-11-05 16:01:57 +08:00
16334ca5c5
Merge pull request #505 from 0xEmberZz/fix/web-ui-display-issues fix: resolve Web UI display issues (#365 )
2025-11-05 15:59:52 +08:00
0bcd24c523
Merge pull request #428 from zhouyongyou/fix/initial-balance-sync fix(api): add balance sync endpoint with smart detection
2025-11-05 15:58:45 +08:00
d675c20eed
Merge pull request #416 from zhouyongyou/fix/bug-fixes-collection-v2 fix: 修復 6 個 bug（替代 #271）
2025-11-05 15:57:36 +08:00
0da42bd1fd
Merge branch 'dev' into fix/bug-fixes-collection-v2
2025-11-05 15:56:58 +08:00
87e2ba8214
Merge pull request #471 from zhouyongyou/fix/hyperliquid-complete-balance-fix fix(hyperliquid): complete balance detection with 4 critical fixes
2025-11-05 15:47:15 +08:00
90b1b03697
Merge pull request #446 from zhouyongyou/fix/json-fullwidth-characters fix(decision): handle fullwidth JSON characters from AI responses
2025-11-05 15:46:56 +08:00
e33f9babfe
Merge pull request #386 from zhouyongyou/feat/configurable-oi-threshold feat(decision): configurable OI threshold + relaxed trading template
2025-11-05 15:46:25 +08:00
19628fa9df
Merge pull request #385 from zhouyongyou/fix/market-price-staleness fix(market): resolve price staleness causing trade failures
2025-11-05 15:45:52 +08:00
cdfe8956ce
Merge pull request #414 from zhouyongyou/feat/query-actual-balance-v2 feat(api): query actual exchange balance when creating trader
2025-11-05 15:45:09 +08:00
678392fab1
Merge pull request #325 from zhouyongyou/refactor/enhance-partial-close-guidance refactor(prompts): 增強部分平倉使用指導 [依賴 #415 ]
2025-11-05 15:43:08 +08:00
2c122f0c5c
Merge pull request #273 from zhouyongyou/feat/logger-dynamic-tpsl feat(logger): 添加動態 TP/SL 日誌支持 [依賴 #415 ]
2025-11-05 15:42:33 +08:00
af1fc4189a
Merge pull request #415 from zhouyongyou/feat/partial-close-core-v2 feat: 部分平倉和動態止盈止損核心實現 / Partial Close & Dynamic TP/SL Core
2025-11-05 15:41:20 +08:00
07be9065d5
Merge pull request #501 from Hansen1018/add-Hansen-prompt 增加 稳健和风险控制均衡基础策略提示词
2025-11-05 15:33:02 +08:00
6910a25ae6
Merge pull request #500 from CoderMageFox/feature/aster-field-help-tooltips feat: add help tooltips for Aster exchange configuration fields
2025-11-05 15:04:27 +08:00
ba0bb8c365
feat: update backend scripts and migration tools
2025-11-05 06:56:28 +00:00
icy
SkywalkerJi
0xYYBB | ZYY | Bobo
tinkle-community
Lawrence Liu
Burt
Ember
hzb1115
Sue
Diego
杜仲
Icyoung
ERIC LEUNG
CoderMageFox
GitBib
Theshyx11
Jupiteriana
PoorThoth
zcan
vicnoah
nofxai