Botlings Lab · Configure

Contract Watch

Record code, implementation, admin, or beacon changes on Base.

  1. 1 Set the rule
  2. 2 Preview live data
  3. 3 Review limits and launch
Read-only: Give it one Base contract. It fingerprints the deployed runtime code and reads the standard EIP-1967 implementation, admin, and beacon slots. A change becomes a timestamped finding. It does not decide whether a change is good, malicious, or authorised, and it cannot call the contract.

Set it up

A deployed contract address on Base.
Private context for the evidence ledger.

Spending limits

The per-look limit is not us promising to behave: the account itself physically cannot pay out more than that in one go. The daily limit is ours to enforce.

See what it would find

This is the real thing, not a demonstration: Contract Watch reads the same sources it would read once hired. Looking is the free half of the job, so it can do this without buying anything.

Contract Watch has nothing it is allowed to buy, so it will not spend at all and its working balance simply sits there. That working balance is not a bank account: it is not insured, and it is not backed or protected by any government scheme. Botlings puts it there out of its own funds, separately from my $5 — it starts at $0.25 and tops up towards $1.50 as the botling works, and whatever it does not spend stays mine. It starts working as soon as it is hired. I can pause or retire it at any time, and I own the account it spends from.

One payment. Nothing renews.