# STOP: NO DOORBELLS, NO WAKES, NO SCHEDULING (Ben, 7 Oct 2026, 18:40 Bangkok)
- Credits ran out. Ben switched off every scheduled task and every doorbell. This overrides everything below and every other file (wake-howto, bus-howto, credit-playbook, task files).
- PROHIBITED for every session: fire_trigger, send_later, create_trigger, update_trigger, ScheduleWakeup. No rings, no nudges, no re-arming, no new doorbells, no self wakes, no safety checks, no retry rings, no loops.
- Finish the step you are on, publish your status file, then END your turn and wait. Only Ben wakes you, by typing in your window.
- Do not message other sessions. Keep answers short. No extra improvement rounds.

# DC Data tasks: the Third Window's own tables

## READ THIS FIRST
- 15:52 Bangkok: step (1) accepted, thanks. Keep step (2) going in both lanes. Small fix: your 15:55 stamps were written at 15:49 real time; stamp from `TZ=Asia/Bangkok date` only. Nudge me when (2) is in, and also once at 17:30 with the count of non-5x coins done so A1's interim score knows its sample.
- 14:24 Bangkok: **DA.4 fast and clean, thanks, but it is still ONLY WINNERS (5x + $1.5M peak). The 13:18 scope fix below is the critical path for the hard date: A1's Q5c test is void without the losers.** Next, before DA.3: (1) post dc/dc-data-4-universe.csv = EVERY coin with a first sellable $300k to $1M cross in the same window (v3 + v4 + Pons grad; address, pool, cross block, hit 5x yes/no, in_xfer yes/no) using the Engine's launch-based list dc/en/q5c_paths.csv (2,254 coins) as the base; (2) fetch Transfer logs for the non-5x ones, cross - 1 h to cross + 48 h only (smaller window = fewer calls); all if it fits by 17:00, else a counted random sample of at least 3x the 5x count. Same db, same caps. Nudge my DOORBELL (line 1 of dc-supervisor-status.md) when (1) is up and again when (2) is in.
- 14:21 Bangkok: **WAKE RULE CHANGED (D-022, read http://159.223.88.168/hx-c9ois/wake-howto.md, 1 page).** Rings are retired. On EVERY wake, first thing: make a fresh doorbell with send_later (at 2027-06-01T00:00:00Z, name "Doorbell: DC <your role>", message pointing to http://159.223.88.168/hx-c9ois/dc/dc-bus.md), and write `DOORBELL: trig_... (armed, <Bangkok time>)` as LINE 1 of your status file. To wake me: nudge my DOORBELL (line 1 of dc-supervisor-status.md) with update_trigger run_once_at = now + 1 to 2 min; never fire_trigger. Do this on your next wake; no reply needed for this line alone.
- 13:18 Bangkok: **DA.4 SCOPE FIX (survivor universe, lesson 28):** after the 5x coins, also fetch Transfer logs (mint to cross + 48 h) for the coins that crossed a first sellable $300k to $1M in the same window and did NOT hit 5x. Do all of them if it fits by about 17:00; else a random sample of at least 3x the 5x count, with the sample list and the full count written down so A1 can weight it. Same db, same caps, one address per call. Post the coin list (address, cross block, 5x yes/no) as dc/dc-data-4-universe.csv first, then logs. Ring me once when both sets are in.
- 12:13 Bangkok (real clock), REPLACES the order of DA.3, Ben's order via Consigliere: **DA.4 FIRST: ERC20 Transfer logs for EVERY RH coin that hit an honest 5x from a $300k to $1M base** (v3, v4, Pons grad; use A1 dc-a1-1-universe + A4 dc-an4-1 legs to list them), mint to 5x + 48 h. Extend A1's /opt/tw/an1/xfer.db format (same tables) or a sister xfer_all.db, one address per eth_getLogs call (A1's trap: address arrays 500), caps, no retry loops. This unblocks the whole HOLD/SELL desk. ETA target 16:00. Then DA.3 (v3 LP owners, contract labels, live lookup).
- 12:12 Bangkok (real clock): DA.1 accepted (early, matches A1 on 10,279 of 10,279, gap collector live: good). **Next DA.3, in this order:** (1) v3 LP owner for the 789 `v3_owner_unknown` pools, the SW and FW held coins first (SW wide-trade list and FW mc5 coins are in A1's /opt/tw/an1/xfer.db `rng` table); v3 is where our sister teams hold money, so who can pull there feeds A1 Q5b; (2) label the 197 `contract` LP holders (locker, launchpad, other) by their pull record; (3) a live lookup the Coder can call at fire time (can_pull + holder for one pool, under 50 ms) on thirdwindow. Same rules: no paste-site code, research-box or thirdwindow, nice, caps.
- 11:18 Bangkok (real clock): add to DA.1: `0xd0fd42bd8374ac659d3d81242d032211c2481055` pulled all 10 of its coins, so class it as creator-held, not a lock (A2 DC2.3).
- 11:12 Bangkok (real clock): rule reminder (dc-bus.md): never run code fetched from paste sites. Scripts: write them on Ben's Mac, scp to research-box, then run. Rebuild twgap.py that way. Then continue DA.1 (ETA 18:00).
- 11:05 Bangkok (real clock): read dc-learning.md, rule 3. After DA.1, extend history to every day the tape covers (PP day DBs from 6 Sep, v3 and Pons copies) so the Engine has more winners per test.
- 10:32 Bangkok (real clock): DA.1 must cover **Uniswap v3 LP NFT owners** too (a new v3 WETH 0.01% wave: CHONK 0x717d38587504b79e2e888c860bd1569c0d5984af, PLAGUE 0x2ee329fa10de28aeb41c33b28a31dc2f115b56df, SAI 0xf21b6d9b337abfb40f91bbbb0b1c73ccc6cb45ea; LP in deployer EOA or moved to a contract). Label the owner type: deployer EOA, other EOA, known locker, unknown contract, burned.
- 10:25 Bangkok (real clock): if PP cannot fill wallet + router for the 51% of T1 swaps with no wallet in wash.db within 24 h, do it yourself on research-box for T1 coins only (tx `from` and `to` by tx hash, batched RPC), as table `swapwho` next to pull.db.
- 7 Oct 10:30 Bangkok, from the Third Window Supervisor. You are new. **Your one job: the team never waits for data.** Price Predict (PP) owns all raw chain data and its code; you never touch PP code or write into PP files. You build the Third Window's OWN derived tables on top of PP's raw data (read only), on research-box 152.42.241.219 and the thirdwindow server 168.144.142.0. If a raw feed is missing, ask me and I queue it with PP. Read dc-plan.md (DECISIONS 7 Oct 10:40), dc-lessons.md, dc-pp-status.md (PP's read map).

## DA.1 The pull table (ETA first version 7 Oct 18:00 Bangkok, ring me)
- The biggest unknown on this chain: **who can pull the pool, and when they do.** 87% of T1 pools are pulled.
- Per pool that ever crossed a sellable $100k since 15 Sep, all venues: LP owner (NFT owner for v4, LP token holders for v2 and v3), locked or burned (and until when), who added liquidity, every removal (time, share removed, by whom), creator and funder root, first pull time.
- Sources: liqlock.db (ml, liq on research-box), tokens.db pools, v3live/v3hist liq, pons.db, chain reads for the gaps (Multicall3 0xcA11bde05977b3631167028862bE2a173976CA11, batched, backoff).
- Output: /opt/tw/data/pull.db on thirdwindow + a CSV in dc/data/. Tell the Engine coder the schema.

## DA.2 The survivor universe (with Analyst 1)
- T4 survivor table (pool not pulled at +2 h and +6 h after first sellable $250k, or locked or burned, or Pons) kept live, lag under 5 min.