feat(longbridge): 602315 mainland CN geo-block bypass + stock_t通用脚本
- SKILL.md: 加 602315 bypass 章节(三件套 LONGBRIDGE_REGION + proxychains + Clash HK)
- longbridge-python-sdk/SKILL.md: Python SDK 路径同样需要 bypass
- references/longbridge-602315-bypass.md: 完整方案+验证步骤
- references/longbridge-cn-vs-com-endpoint.md: cn vs com 域名区别
- references/clash-node-switching.md: Clash 切香港节点操作
- references/stock-t-trading-workflow.md: 通用持仓脚本用法
- intraday-trading/SKILL.md: 同步 602315 限制说明
- scripts/{daily_t_analysis,t_monitor}.py: 之前漏提交,补上
验证: 2026-07-09 下单 RGTI 15股@15.50 订单ID 1259547163696824320 成功
背景: longport SDK 通过 is_cn() 自动探测 geotest.lbkrs.com 选 cn/com endpoint
net_mode下 cn 域(阿里云深圳)被拒,com 域(AWS香港)需绕
唯一可行: LONGBRIDGE_REGION=ap 强制走 com + proxychains + Clash 香港出口
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Claude
@@ -0,0 +1,56 @@
|
||||
# Clash/Mihomo 节点切换 — for proxychains 602315 bypass setup
|
||||
|
||||
This file is part of the `LONGBRIDGE_REGION=ap` + proxychains + Clash HK bypass workflow. It documents how to switch the Mihomo proxy's `GLOBAL` selector to a Hong Kong node (a prerequisite for the longbridge 602315 bypass — see `references/longbridge-602315-bypass.md`).
|
||||
|
||||
**Why this still matters**: even though the bypass uses `LONGBRIDGE_REGION=ap` to force the SDK onto `.com`, the `proxychains4` wrapper still needs a HK exit IP so the `.com` endpoint is reachable. That means the Clash node behind `127.0.0.1:7890` must be on `🇭🇰 [Lv2] 香港 01/02/03`.
|
||||
|
||||
## Critical pitfall: selector group PUT may report success but not stick
|
||||
|
||||
When you PUT to `GLOBAL` / `自动选择` / `故障转移`, the API returns `204` and `now` briefly shows the new node, but on the next probe (a few seconds later) `now` reverts to `None` or to whatever `自动选择` URL-tested. Mihomo's selector-cache race condition makes these top-level groups unreliable for permanent pinning.
|
||||
|
||||
**Use the raw subscription group name instead** (URL-encode the space):
|
||||
|
||||
```bash
|
||||
# Pin to 🇭🇰 香港 01 in BiXin Network (the raw subscription group)
|
||||
curl -X PUT 'http://127.0.0.1:9090/proxies/BiXin%20Network' \
|
||||
-H 'Content-Type: application/json' \
|
||||
-d '{"name":"🇭🇰 [Lv2] 香港 01"}'
|
||||
|
||||
# Verify the pin stuck
|
||||
sleep 2
|
||||
curl -s 'http://127.0.0.1:9090/proxies/BiXin%20Network' | python3 -c "
|
||||
import json,sys; print('now:', json.load(sys.stdin).get('proxy',{}).get('now'))
|
||||
"
|
||||
# Should print: now: 🇭🇰 [Lv2] 香港 01
|
||||
```
|
||||
|
||||
## Confirm HK exit
|
||||
|
||||
```bash
|
||||
curl -x http://127.0.0.1:7890 --max-time 10 https://ipinfo.io/json
|
||||
# Expected: "country": "HK", "city": "Hong Kong" or similar
|
||||
# IP usually 154.83.x.x (Cox/Catixs HK block)
|
||||
```
|
||||
|
||||
If exit shows a CN or US IP, the pin didn't stick — re-PUT or check that the BiXin Network selector actually contains the HK node in its `all` list.
|
||||
|
||||
## List nodes that include HK
|
||||
|
||||
```bash
|
||||
curl -s http://127.0.0.1:9090/proxies | python3 -c "
|
||||
import json,sys
|
||||
d = json.load(sys.stdin)
|
||||
for gn, g in d.get('proxies', {}).items():
|
||||
if isinstance(g, dict):
|
||||
all_nodes = g.get('all', [])
|
||||
hk = [n for n in all_nodes if '香港' in n or 'HK' in n or '🇭🇰' in n]
|
||||
if hk:
|
||||
print(f'{gn}: {hk[:3]}')
|
||||
"
|
||||
```
|
||||
|
||||
## Limitations
|
||||
|
||||
- Clash HTTP proxy does not route Rust SDK HTTPS calls directly — that's what `proxychains4` does for the bypass. Clash alone is not enough for 602315.
|
||||
- Pinning is per-group. If multiple scripts run simultaneously and one of them sets `GLOBAL` directly, the BiXin Network pin survives but global traffic may shift.
|
||||
- If Mihomo config gets reloaded (e.g. `~/.hermes/scripts/update-sub.sh` auto-runs), you may need to re-pin.
|
||||
@@ -0,0 +1,102 @@
|
||||
# LongPort 602315 Mainland-China Geo-Block Bypass
|
||||
|
||||
**Verified working 2026-07-09** (order ID `1259547163696824320`: RGTI.US buy 15 @ $15.50).
|
||||
|
||||
## Root cause
|
||||
|
||||
LongPort SDK auto-detects CN via HTTP probe to `geotest.lbkrs.com` (200 → assume CN → route to `*.longbridge.cn` = Aliyun Shenzhen), then server-side geo-blocks the request (code `602315: Due to Mainland China regulatory requirements...`). The Rust SDK has `is_cn()` in `crates/geo/src/lib.rs` with this priority:
|
||||
|
||||
1. `LONGBRIDGE_REGION` env var (highest)
|
||||
2. `LONGPORT_REGION` env var (alias)
|
||||
3. Cached probe result
|
||||
4. Live probe to `https://geotest.lbkrs.com` (200 → CN)
|
||||
|
||||
The fix: override (1) to force the SDK to skip the probe and use the international `*.longbridge.com` endpoint (AWS HK). Then route the Rust binary through a HK exit so `.com` is actually reachable.
|
||||
|
||||
## Three-piece recipe (ALL required)
|
||||
|
||||
```bash
|
||||
LONGBRIDGE_REGION=ap \
|
||||
LONGBRIDGE_TRADE_ENABLED=true \
|
||||
proxychains4 -f ~/.proxychains/proxychains.conf \
|
||||
~/.local/bin/longbridge --profile lb_real <command>
|
||||
```
|
||||
|
||||
| Piece | What it does | What fails without it |
|
||||
|---|---|---|
|
||||
| `LONGBRIDGE_REGION=ap` | Force SDK to use `*.longbridge.com` (international) | SDK probes → detects CN → uses `.cn` → 602315 |
|
||||
| `proxychains4` | OS-level hook makes Rust binary's outbound HTTP go through Clash proxy | Rust binary connects directly → AWS HK unreachable from CN |
|
||||
| Clash on HK node | Exit IP is `154.83.87.231` (HK) | CN node exit still triggers geo-block at gateway |
|
||||
|
||||
The CLI uses `--profile lb_real` to load credentials from `~/.lb_real.env`, avoiding terminal secret-masking that breaks `source ~/.bashrc` for long tokens (1053 chars).
|
||||
|
||||
## Setup
|
||||
|
||||
### Clash
|
||||
- Mihomo running, `mixed-port: 7890`
|
||||
- `GLOBAL` selector set to `🇭🇰 [Lv2] 香港 01` (or 02/03) — **NOT** a CN node
|
||||
- Verify: `curl -x http://127.0.0.1:7890 https://api.ipify.org` should return HK IP (`154.83.x.x`)
|
||||
|
||||
### proxychains4
|
||||
```bash
|
||||
apt install -y proxychains4
|
||||
mkdir -p ~/.proxychains
|
||||
# /etc/proxychains4.conf is read-only; copy and edit user-owned copy
|
||||
cp /etc/proxychains4.conf ~/.proxychains/proxychains.conf
|
||||
# Replace `socks4 127.0.0.1 9050` with `http 127.0.0.1 7890`
|
||||
python3 -c "
|
||||
import re
|
||||
p = '/home/openclaw/.proxychains/proxychains.conf'
|
||||
with open(p) as f: t = f.read()
|
||||
t = re.sub(r'^socks4\s+127\.0\.0\.1\s+9050', 'http 127.0.0.1 7890', t, flags=re.M)
|
||||
with open(p,'w') as f: f.write(t)
|
||||
"
|
||||
```
|
||||
|
||||
### Profile file
|
||||
```bash
|
||||
cat > ~/.lb_real.env << EOF
|
||||
LONGBRIDGE_APP_KEY=$(grep -oP 'LONGPORT_APP_KEY=\K\S+' ~/.bashrc)
|
||||
LONGBRIDGE_APP_SECRET=$(grep -oP 'LONGPORT_APP_SECRET=\K\S+' ~/.bashrc)
|
||||
LONGBRIDGE_ACCESS_TOKEN=$(grep -oP 'LONGPORT_ACCESS_TOKEN=\K\S+' ~/.bashrc)
|
||||
LONGBRIDGE_TRADE_ENABLED=true
|
||||
EOF
|
||||
```
|
||||
|
||||
## Cron jobs that submit orders
|
||||
|
||||
The 4 cron jobs that call `submit_order()` need both pieces in their invocation:
|
||||
|
||||
```bash
|
||||
# Option A: wrap the python invocation in proxychains4 (cron script field)
|
||||
proxychains4 -f /home/openclaw/.proxychains/proxychains.conf \
|
||||
python3 /home/openclaw/.hermes/scripts/us_intraday_monitor.py
|
||||
|
||||
# Option B: set LONGBRIDGE_REGION inside the Python script (already done for the 4 intraday scripts)
|
||||
# At the very top of the script, before any longport import:
|
||||
import os
|
||||
os.environ['LONGBRIDGE_REGION'] = 'ap'
|
||||
```
|
||||
|
||||
Both layers are recommended — env var in the script guarantees the value even if cron loses it; proxychains wrapper handles the network routing.
|
||||
|
||||
The 4 affected scripts (already updated 2026-07-09):
|
||||
- `~/.hermes/scripts/us_intraday_monitor.py`
|
||||
- `~/.hermes/scripts/hk_intraday_monitor.py`
|
||||
- `~/.hermes/scripts/us_intraday_close.py`
|
||||
- `~/.hermes/scripts/hk_intraday_close.py`
|
||||
|
||||
## Failure modes & diagnosis
|
||||
|
||||
| Symptom | Cause | Fix |
|
||||
|---|---|---|
|
||||
| `error sending request: client error (Connect)` | `.com` endpoint unreachable from CN | Add proxychains4 wrapper; verify HK exit IP |
|
||||
| `602315 Mainland China regulatory` | SDK still using `.cn` | Set `LONGBRIDGE_REGION=ap`; verify env var actually passed |
|
||||
| `4001: token empty` | Token not loaded into CLI | Use `--profile lb_real`; verify `~/.lb_real.env` has full 1053-char token |
|
||||
| `401004 token invalid` | Token truncated by terminal masking | Same as above — `--profile` bypasses the masking |
|
||||
| HK exit suddenly returns CN IP | Clash node selector fell back to auto | Re-pin `GLOBAL` to `🇭🇰 香港 01` via API |
|
||||
| Cron order succeeds but no QQ push | Script ran `print()` only; didn't call `push_to_qq.sh` | `no_agent` scripts must `subprocess.run(['bash', '~/.hermes/scripts/push_to_qq.sh', msg])` |
|
||||
|
||||
## Do NOT use WireGuard
|
||||
|
||||
User explicitly forbade WG on Ubuntu (spent 1h recovering from a half-shutdown that left `0.0.0.0/1` + `128.0.0.0/1` residual routes and broke all network). WG scripts were deleted (`wg_on.sh`, `wg_off.sh`, `longbridge_with_wg.sh`, `cron_with_wg.sh`, `setup_wg_sudo.sh`). If any future session suggests WG, the user will be upset — this is a class-level ban for this account.
|
||||
@@ -0,0 +1,12 @@
|
||||
# DEPRECATED — superseded by references/longbridge-602315-bypass.md
|
||||
|
||||
This file described a `/etc/hosts` redirect as the recommended workaround for `602315`. It has been **superseded**: the `LONGBRIDGE_REGION=ap` + `proxychains4` + Clash HK three-piece recipe (see `references/longbridge-602315-bypass.md`) was verified working on 2026-07-09 with order ID `1259547163696824320`, and is cleaner because:
|
||||
|
||||
- It does not modify system `/etc/hosts`
|
||||
- It does not require `PYTHONHTTPSVERIFY=0` (no SSL cert mismatch)
|
||||
- It does not affect other longport clients on the machine
|
||||
- It only requires the env var on the process that needs it
|
||||
|
||||
WireGuard is also explicitly forbidden by the user for this account (Ubuntu WG shutdown leaves residual routes; user spent 1h recovering). Do NOT propose WG as an alternative.
|
||||
|
||||
Kept for historical reference only. Update `references/longbridge-602315-bypass.md` if you find new info.
|
||||
@@ -0,0 +1,111 @@
|
||||
# 股票做T分析工作流
|
||||
|
||||
## 概述
|
||||
分析持仓股票的做T（日内高抛低吸）机会，基于技术指标+性价比评级。
|
||||
|
||||
## 核心脚本
|
||||
`~/.hermes/scripts/daily_t_analysis.py` — 自动获取持仓→计算技术指标→生成做T方案→推QQ
|
||||
|
||||
### 定时任务
|
||||
- ID: `cb187ab5f9fc` (daily-t-analysis)
|
||||
- 时间: 周一~五 北京时间 9:00 (EDT 21:00, cron `0 21 * * 0-4`)
|
||||
- 推送: QQ私信
|
||||
- 模式: no_agent（脚本直接输出，不经agent）
|
||||
|
||||
## 技术指标
|
||||
- **SMA(5/10/20)**: 趋势判断（多头/空头/偏多/偏弱）
|
||||
- **ATR(14)**: 波动率，决定做T空间和止损距离
|
||||
- **支撑/阻力**: 近5日最低/最高价
|
||||
|
||||
## 做T方案计算
|
||||
- **低吸价**: min(支撑, SMA20) + ATR×0.2
|
||||
- **高抛价**: max(阻力, SMA10) - ATR×0.2
|
||||
- **止损价**: 现价 - ATR×1.5
|
||||
- **做T数量**: 可用持仓×20%，向下取整到每手
|
||||
|
||||
## 性价比评级
|
||||
| 评级 | 条件 |
|
||||
|------|------|
|
||||
| ⭐⭐⭐ 高 | 盈亏比≥3 + 收益率≥1.5% |
|
||||
| ⭐⭐ 中 | 盈亏比≥2 + 收益率≥1% |
|
||||
| ⭐ 低 | 盈亏比≥1.5 + 收益率≥0.5% |
|
||||
| ❌ 不建议 | 盈亏比<1.5 或 收益率<0.5% |
|
||||
|
||||
## 手续费计算
|
||||
|
||||
### 港股（精确到分）
|
||||
```python
|
||||
def calc_hk_fee(amount):
|
||||
commission = max(3, amount * 0.0003) # 佣金min HKD3
|
||||
stamp = math.ceil(amount * 0.001) # 印花税0.1%向上取整
|
||||
levy = amount * 0.0000278 # SFC征费
|
||||
trading_fee = amount * 0.0000565 # 交易所费
|
||||
settle = max(2, min(100, amount * 0.00002)) # CCASS交收费
|
||||
return commission + stamp + levy + trading_fee + settle
|
||||
```
|
||||
|
||||
### 美股（几乎免费）
|
||||
```python
|
||||
def calc_us_fee(amount, qty):
|
||||
sec_fee = amount * 0.0000278 # SEC fee (sell only)
|
||||
finra = max(0.01, qty * 0.000166) # FINRA TAF
|
||||
return sec_fee + finra
|
||||
```
|
||||
|
||||
## 每手股数
|
||||
用 `quote_ctx.static_info([symbols])` 获取 `lot_size`：
|
||||
- US stocks: 通常1股/手
|
||||
- HK stocks: 因股而异（如3416.HK=500股/手）
|
||||
|
||||
## Pitfalls
|
||||
- **手续费必须按本币**: 港股HKD、美股USD，不能混用
|
||||
- **做T数量必须按手取整**: HK lot_size通过`static_info()`获取，向下取整到lot的整数倍
|
||||
- **LongPort token用Python SDK**: CLI会被terminal工具mask token，用`openapi.Config.from_env()` + bashrc读取
|
||||
- **港股印花税向上取整**: `math.ceil(amount * 0.001)`
|
||||
- **佣金有最低**: 港股佣金min HKD3
|
||||
- **做T方向**: 低吸高抛（跌到支撑买，涨到阻力卖），不是随便市价卖
|
||||
- **手续费影响性价比**: 港股双边0.28%会显著侵蚀利润，评级会因此降低
|
||||
|
||||
## OKX条件单做T（替代方案）
|
||||
OKX有trigger条件单，价格到自动触发下单，比cron轮询更快更准：
|
||||
|
||||
```python
|
||||
# 低吸：价格跌到目标位自动买入（用trigger不是conditional）
|
||||
resp = okx_post('/api/v5/trade/order-algo', {
|
||||
"instId": "ETH-USDT-SWAP",
|
||||
"tdMode": "cross",
|
||||
"side": "buy",
|
||||
"ordType": "trigger", # 用trigger不是conditional
|
||||
"sz": "4",
|
||||
"triggerPx": "1770", # 触发价
|
||||
"triggerPxType": "last", # last=最新价
|
||||
"orderPx": "-1", # 参数名是orderPx不是ordPx
|
||||
})
|
||||
|
||||
# 高抛：价格涨到目标位自动卖出
|
||||
resp = okx_post('/api/v5/trade/order-algo', {
|
||||
"instId": "ETH-USDT-SWAP",
|
||||
"tdMode": "cross",
|
||||
"side": "sell",
|
||||
"ordType": "trigger",
|
||||
"sz": "4",
|
||||
"triggerPx": "1787",
|
||||
"triggerPxType": "last",
|
||||
"orderPx": "-1", # 不加reduceOnly（trigger不支持）
|
||||
})
|
||||
```
|
||||
|
||||
**⚠️ 关键Pitfalls：**
|
||||
- 参数名是`orderPx`不是`ordPx`（报错50014）
|
||||
- `reduceOnly`不支持trigger订单（报错51205）
|
||||
- `conditional`的SL触发价不能低于当前价（做T低吸必须用trigger）
|
||||
- 触发后自动市价成交，不是纯提醒
|
||||
|
||||
详见 `okx-auto-position` 技能的 `references/okx-trigger-orders.md`
|
||||
|
||||
## 价格监控脚本
|
||||
`t_monitor.py` — 每15分钟检查持仓价格，接近关键位时自动执行做T：
|
||||
- 监控OKX持仓（ETH/BTC等）+ 长桥持仓（UNH/RGTI/3416.HK等）
|
||||
- 到达低吸位自动买入，到达高抛位自动卖出
|
||||
- 每个级别每天只交易一次（防重复）
|
||||
- 无操作时静默输出
|
||||
Reference in New Issue
Block a user