CCanary v0.4
scanfilmlive deskhowgithubscan a token
live watchtower / Robinhood Chain 4663

CANARYv0.4

the chart forgets.
canary doesn't.

One snapshot tells you what exists now. Canary keeps the state before it, compares the next sweep against it, and leaves the reason beside every deterministic signal.

OPEN SOURCE / PUBLIC CONTRACT DATA ONLY / NO LOGIN / NO WALLET CONNECTION / NO PAYMENTS
WATCHTOWER ONLINEusecanary.watch / public scan + persistent local memory
rpcprobing
chain block-
snapshots0
remembered0
public chain scanone token / one live read / zero execution
01 / validate launch
02 / read state
03 / normalize
04 / snapshot
Public contract address only. No account, wallet connection, or payment is required.
flight recorder sentinel grid view source
Created by @gippp69 on X
CHAIN 4663 / ROBINHOOD CHAINPONS V2 / LIVE STATEREAD ONLY / NO WALLET CONNECTIONPERSISTENT MEMORY / BEFORE -> AFTERPOOL LIQUIDITY / PRICE / SWAPS / FEES CHAIN 4663 / ROBINHOOD CHAINPONS V2 / LIVE STATEREAD ONLY / NO WALLET CONNECTIONPERSISTENT MEMORY / BEFORE -> AFTERPOOL LIQUIDITY / PRICE / SWAPS / FEES
00 / twenty seconds

one sweep becomes a memory.

product sequence / no token required
CANARY / READ-ONLY WATCHTOWER00:00 / 00:20
read the chain.
save the state.
Canary starts with one current snapshot. No wallet connection and no transaction execution.
00:00RPC / chain 4663 / block acquired
00:04snapshot / deployer / market / activity / fees
00:08memory / previous state loaded
00:12delta / pool price moved beyond threshold
00:16reason / before -> after stored beside signal
00:20next sweep / memory compounds
Canary v0.4 live desk
Pons V2 / Robinhood Chain 4663 / persistent read-only watchtower
READ ONLY
loading local state...
0
tracked positions
0
active local watchers
0
WATCH signals / 24h
0
LEAVE signals / 24h
0
remembered snapshots
-
Robinhood Chain block
the pulse

Only values Canary can actually read or remember. No manufactured score and no market promises.

rpcprobing
chain block-
snapshots0
remembered0

positions remembered by Canary

Starts a local read-only watcher. No wallet connection. No transaction execution.
tokenphasedevmarket statestatusseen
03 / flight recorder

every sweep leaves a receipt.

The useful object is not one chart. It is the sequence: what Canary saw, what changed, which rule noticed it, and what the previous state looked like.

CANARY / FLIGHT RECORDERwaiting for state
loading remembered state...
rpc-
block-
samples0
watchers0
04 / sentinel grid

the watchtower, moving on one screen.

Remembered positions become a compact live surface. A token you scan can also appear here immediately as a current snapshot.

CANARY // SENTINEL GRIDRobinhood Chain 4663 / read only
observe → remember → compare → signal → sweep again
waiting for remembered positions or a public token scan.
05 / what Canary remembers

six fields become a state history.

The same surfaces are normalized every sweep so the next change has a baseline.

deployershare, launch count and movement
liquiditycurve reserve or pool liquidity
pricepool price against previous state
activitytrades, swaps and last activity
feesquote and token fee movement
phasecurve, swept, pool and rescued
02 / what changed

the useful part is the delta.

A single chart tells you what exists now. Canary is built around the comparison: what moved, by how much, and which plain rule noticed it.

previous sweepillustrative sequence
phasePOOL
deployer share4.80%
pool price0.000124
recent swaps14
token fees0.00
→
current sweepsame fields
phasePOOL
deployer share4.80%
pool price0.000091
recent swaps37
token fees12.40
why this matters: the example is deliberately labeled illustrative. On a real watched position Canary fills this surface from stored sweeps and keeps the before → after values beside the rule that fired.
03 / workflow

one token becomes a state timeline

Canary never trades. It reads the chain, saves a snapshot, compares it with the previous state, explains any deterministic delta, and keeps the result for the next sweep.

01

paste CA

Start a local watcher directly from the board.

02

read chain

Read deployer, phase, reserve or pool state, swaps, fees and activity.

03

snapshot

Persist the current state locally for a real before-and-after baseline.

04

compare

Run transparent thresholds over the previous and current snapshots.

05

remember

Build live charts and a signal timeline that survives browser refreshes.

04 / coverage

what the desk actually tracks

Each token is a stateful position with deployer context, market activity, fee movement and Pons V2 phase information attached to it.

D

deployer share

Tracks deployer balance across sweeps and records material drops.

L

reserve and liquidity

Reads curve quote reserve before graduation and pool state after graduation.

A

swaps and activity

Tracks recent curve trades or pool swaps and the latest known activity.

F

fee movement

Shows quote-side and token-side fee state between snapshots.

P

phase changes

Follows curve, swept, pool and rescued routing state.

#

deployer history

Surfaces recent launch count and graduation context for the deployer.

05 / deterministic signals

three states, with the reason beside them

There is no hidden score. The board keeps the final surface small and every signal points back to a plain rule.

QUIET

No configured threshold crossed on the latest comparison. State is still recorded and memory keeps growing.

WATCH

A deterministic condition deserves inspection, such as stale activity, fee movement or a serial deployer threshold.

LEAVE

The highest-severity local signal, such as a sharp deployer-balance or curve-reserve drop. It is still not an automatic trade.

06 / persistent memory

the chart remembers the previous state

A fresh chart tells you what exists now. Canary is built around what changed one sweep ago, then keeps stacking those observations into live history.

sweep arriveslive on-chain state becomes a normalized snapshot
previous state loadsthe last remembered snapshot becomes the baseline
delta is evaluatedplain rules produce QUIET / WATCH / LEAVE context
timeline persistshistory and signal context remain available for the next session

local state by design

The board is a view over data the watcher already collected. Closing the browser does not erase the previous state.

.canary/snapshots.json = latest state
.canary/board-memory.json = historical samples + alerts
board refresh 2s = visualization
watch sweep 10s = fresh chain read
07 / trust boundary

useful because it cannot spend

The read-only boundary is part of the product. Canary observes and explains state while execution remains somewhere else.

no transaction path.

The public site never connects an account and exposes no transaction execution. WATCH TOKEN only starts another read-only monitoring process.

READ ONLYpublic contract data only
NO ACCOUNTno credentials are collected
NO TRADING UIsignals are context, not orders
PLAIN RULESthresholds live in source
08 / refusals

what Canary refuses to become.

The boundary is visible on purpose. If a feature needs account access, transaction execution, or a guessed number, it does not belong in this watchtower.

useful because some paths simply do not exist.
execute transactionrefused — Canary is an observation-only service.
connect accountrefused — the public site does not collect credentials or connect wallets.
invent a signalrefused — a WATCH or LEAVE state must map to a configured deterministic rule.
judge one snapshotrefused — change signals need a remembered previous state, not a story around one number.
CANARY v0.4 / Robinhood Chain watchtower scan recorder terminal github X / @gippp69
CANARY
usecanary.watch / Robinhood Chain 4663 / Pons V2READ ONLY / NO WALLET CONNECTION / NO TRANSACTION EXECUTION