CCanary v0.4
scanfilmlive deskhowgithubscan a token
live read-only monitoring for Pons V2

CANARYv0.4

Paste a Pons V2 token. Canary reads the live chain without a wallet, shows the current state, and can keep a persistent memory of what changed between sweeps.

public chain scanRobinhood Chain / 4663 / no signer
One read-only snapshot. Nothing is signed, stored, bought, or sold.
open live desksee how it worksview source
Created by @gippp69 on X
READ ONLYno signer or transaction path
PERSISTENT MEMORYsnapshots survive browser restarts
DETERMINISTICevery alert maps to a plain source rule
PUBLIC SCANone live snapshot without starting a watcher
CHAIN 4663 / ROBINHOOD CHAINPONS V2 / LIVE STATENO SIGNER / NO PRIVATE KEYPERSISTENT MEMORY / BEFORE -> AFTERPOOL LIQUIDITY / PRICE / SWAPS / FEES CHAIN 4663 / ROBINHOOD CHAINPONS V2 / LIVE STATENO SIGNER / NO PRIVATE KEYPERSISTENT 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 signer, no wallet prompt, no transaction path.
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 signer. No transaction path.
tokenphasedevmarket statestatusseen
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.

No wallet client, no imported account, no private key flow and no automatic exit hiding behind the dashboard. WATCH TOKEN only starts another read-only process.

NO SIGNERpublic client reads only
NO KEYsigning material is refused
NO BUY BUTTONsignals 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 a signer, a private key, or a guessed number, it does not belong in this watchtower.

useful because some paths simply do not exist.
sign transactionrefused — Canary has no signer and no execution path.
import private keyrefused — there is nowhere in the product to store signing material.
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.4usecanary.watch / Robinhood Chain / Pons V2 / read-only watchtower / created by @gippp69