Sources and limits
This is a prototype on Arc (mode_ceiling: BUILD). The pool telemetry — current tick, liquidity, read directly from the chain by RPC — is real, not a fixture. Everything downstream of the handover memo — the rota, the shift claims, watcher handles, the week log, block numbers, log indices — is fixture data, marked <Simulated> wherever it appears, because arc-memo’s exact ABI is unverified on chain (see Sources below). Nothing mock is ever shown unlabelled.
What we read, and how
We read slot0, liquidity and ticks directly from the Lunya contract on Arc. Memos are emitted only after a successful contract call so the log index is real. We show exactly what the chain returns.
What the chain will and will not prove
A single concentrated liquidity pool on a new chain cannot be watched by chat alone. One withdrawal can be the entire story. So the watch runs in fixed three-hour shifts, and each one ends with a memo the chain only emits if the call under it succeeded.
The chain will not tell you the exact second — block times are approximate and not ours to sharpen. It tells you the order: block number, log index, memo sequence. Nobody can slip a note in behind yours, nobody can claim they wrote theirs first, and nobody can backfill an hour they did not stand.
Why the holes stay
After seven days the strip reads as one account. Fifty-six shifts, each entry sitting where its block number and log index put it, no line movable afterwards. Where an hour went unstood the strip shows the hole, and the hole stays — that is the part no summary would have kept. Uncovered hours are never hidden, never auto-filled, on the rota strip or in the week log.
Contracts and reads
- Arc Memo predeploy —
0x5294E9927c3306DcBaDb03fe70b92e01cCede505, events emit only when the wrapped call succeeds. - Lunya factory —
0x711492DF23F320745de6fD7f0ab9564FDBfeA016, not yet resolvable to a single dominant pool within this build’s window (a PoolCreated scan across its history hit RPC rate limits). - Live panel reads instead from Synthra V3’s POLL/USDC 1% pool on Arc —
0x5bc5ced48bec9260c8d626269f44e22808b8d2c1, the documented backup subject for Lunya (both run the same Uniswap V3 curve), verified live on 2026-09-18. slot0()/liquidity() are called directly, unlabelled <Simulated>, because the read is real even though the pool is the backup one. - Handover memos queried by memoId (the pool address), ordered by (blockNumber, logIndex, memo sequence).
What this product will not do
- No custody of user funds, ever.
- No token information on the site before launch.
- Real data only; missing data is shown as missing.
- Every list paginated, 50 rows max.
- Signatures verifiable; evidence with a real source call.