KIPP UI v1, memory updates, daily notes 2026-02-10
This commit is contained in:
@ -64,3 +64,46 @@ Major session analyzing Polymarket/crypto tweets D J forwarded from X feed.
|
||||
- D J sending Telegram crypto signal group export (Option 2: JSON export)
|
||||
- Signal provider uses VWAP-based strategy
|
||||
- Sub-agent researching 5 more wallets
|
||||
|
||||
## Evening Session — KIPP + Leverage Trading
|
||||
|
||||
### Crypto Leverage Trading
|
||||
- Built **short signal scanner** (`scripts/short_scanner.py`) — RSI/VWAP/MACD/Bollinger scoring for 29 coins
|
||||
- Built **leverage game engine** (`leverage_game.py`) — $10K, 20x max leverage, longs/shorts/liquidations
|
||||
- Built **auto-trader** (`scripts/leverage_trader.py`) — connects scanners to game, TP/SL/trailing stops
|
||||
- "Leverage Challenge" game initialized, player "case"
|
||||
- Systemd timer every 15min
|
||||
- First scan: market quiet, no strong signals (highest short score 40 on FIL)
|
||||
|
||||
### KIPP Setup
|
||||
- KIPP VM: 192.168.86.100 (Proxmox CT, 8 cores, 8GB RAM, Ubuntu 24.04)
|
||||
- Installed Node.js 22, OpenClaw 2026.2.9
|
||||
- Set up SSH key auth from Case's VM
|
||||
- Created KIPP identity: SOUL.md, AGENTS.md, MEMORY.md, USER.md
|
||||
- Initially tried GLM-4.7 Flash via llama.cpp — had issues, switched to Claude
|
||||
- Configured Telegram bot: @dzclaw_kipp_bot (token: 8535439246:AAE...)
|
||||
- Webchat accessible via https://kipp.host.letsgetnashty.com/
|
||||
- Gateway token: kipp-local-token-2026
|
||||
- Proxmox firewall was blocking LAN access — D J disabled it
|
||||
- Needed trustedProxies, allowedOrigins, dangerouslyDisableDeviceAuth for reverse proxy
|
||||
- D J ran `openclaw configure` to set up Anthropic auth
|
||||
- KIPP is LIVE on Claude + Telegram
|
||||
- Name confirmed: KIPP (not Kip)
|
||||
|
||||
### KIPP Local LLM Attempt (Late Session)
|
||||
- Goal: Switch KIPP from Claude to local GLM-4 Flash 30B (q4) on llama.cpp at 192.168.86.40:8080/v1
|
||||
- llama.cpp server confirmed running and responding
|
||||
- Multiple openclaw.json config attempts failed — schema validation errors
|
||||
- Key schema findings for `openclaw.json`:
|
||||
- `gateway.bind`: must be enum (auto/lan/loopback/custom/tailnet)
|
||||
- `agents.defaults.model`: must be `{ primary: string, fallbacks?: string[] }`
|
||||
- `models.providers`: array of `{ baseUrl, apiKey, api, models[] }` for custom endpoints
|
||||
- `auth.profiles`: only allows provider/mode/email — NOT baseURL/apiKey
|
||||
- Gateway service installed but crashing on config validation
|
||||
- **Status: BLOCKED** — need to apply correct config schema, was mid-fix when session compacted
|
||||
|
||||
### Infrastructure
|
||||
- SSH keys generated on Case's VM, copied to KIPP VM
|
||||
- `loginctl enable-linger` set for boot persistence
|
||||
- sshpass installed on Case's VM
|
||||
- llama.cpp server: 192.168.86.40:8080/v1 (GLM-4 Flash 30B q4)
|
||||
|
||||
Reference in New Issue
Block a user