Proxy implementation changed
Upgraded(address) · Base
Watchtower detects a configured Base upgrade, investigates it at exact historical blocks, and produces evidence you can independently verify.
Upgraded(address) · Base
Start an investigation
Watchtower’s public MVP accepts only server-approved contracts and fixed historical checks.
INVESTIGATE
When a configured proxy emits an upgrade, Watchtower reconstructs the trigger, checks historical state, and binds the result into a deterministic receipt.
Open the evidence workspaceThe emitted implementation agrees with historical proxy state at the upgrade block.
MONITOR
Closed target registry
Selection changes the evidence workspace. It never changes the approved address, event, calls, or historical blocks.
Only these registered profiles can be selected. Contract addresses and calls remain fixed server-side.
Operational workspace
Three configured profiles. Three live-scan targets. Every result stays tied to evidence.
Loading the verified fixture archive.
Visible failure
Observe
Loading the selected profile and checking its recorded upgrade event before building the evidence trace.
Read-only · configured Base profile
HOW IT WORKS
How Watchtower thinks
Each stage records what was requested, what was observed, and what could not be verified.
Verify the approved proxy event and its historical trigger evidence.
Select the immutable investigation plan registered for this profile.
Read historical state at N−1 and N using the fixed, versioned plan.
Let the bounded agent choose approved follow-up check IDs while deterministic code controls every RPC parameter.
Issue a deterministic corroborated, contradicted, or incomplete disposition.
Recompute the canonical receipt ID and open the underlying Base evidence.
RECEIPTS
Committed evidence
Replay one verified upgrade fixture per configured profile. No synthetic activity.
| Protocol | Event | Block and date | Disposition | Checks | Receipt | Action |
|---|
VERIFY
Review packet
Choose a Watchtower review packet or portable integrity proof to verify it locally in this browser.
No upload, fetch, RPC call, or scan is performed.
Verification status
Select an exported JSON packet to begin.
A valid result verifies the canonical receipt payload and its SHA-256 identifier. Packet metadata, narrative, links, and other fields outside that payload are not verified by the receipt hash.
EVIDENCE
VERIFIED FIXTURE · BASEUpgraded(address)
RECORDEDEXACT BLOCK TAGSHistorical checks
FIXED CHECKSCANONICAL PAYLOADReceipt issued
REPLAYABLEFAQ
Quick answers
Quick answers about how Watchtower monitors, investigates and verifies onchain activity.
Still curious? Read the full documentationStart with real evidence
Select one of three approved Base profiles and replay its verified investigation.