Protocol operations check

We check how a protocol runs on chain, not how its code is written: whether the addresses you publish are the ones your contracts use, whether money is sitting in services that stopped, and whether the jobs and withdrawals you rely on still go through. Each finding comes with the reads behind it, a script you can re-run and the exact fix. $2,400 for up to five chains, in ten business days.

What the check looks at

• Address books and published metadata

  Every address in your docs, README tables, SDK and metadata packages, read against what your registries, proxies and contract wiring return on chain. What turns up: an address with no code on the chain it is listed for, for example another chain's deployment in the wrong row, and a contract replaced on chain while the published copy still lists the old one.

• LINK left in Automation upkeeps

  Chainlink deprecated Automation 1.x on 2026-06-30 and 2.1 on 2026-07-31, and its migration guide ends with cancelling the old upkeep and withdrawing its LINK. An upkeep that was never cancelled keeps its prepaid balance. On 2026-10-22 the seven Automation 2.1 registries we read still held 7,456 LINK in 922 upkeeps that were never cancelled. We list each of yours with its balance and its admin, and the two transactions that return the LINK: a cancel, then a withdrawal 50 blocks later.

• Fee routes

  Where protocol fees actually go on each chain, against where your docs say they go: fee receivers still pointing at a retired auction or contract, auctions long past their epoch and selling for close to nothing, and release thresholds far above what a chain collects.

• Keepers and scheduled jobs

  Jobs whose own check says they are due while nothing performs them, keeper lanes still set up for a network that stopped, and governance payloads queued past their delay. A job that stops raises no error, so we read when each one last actually ran.

• Withdrawal and send paths on the next fork

  Glamsterdam has run on Sepolia since 2026-10-06 and reaches Hoodi on 2026-10-26 at 17:42 UTC; mainnet has no date yet. On Sepolia a first ETH send to a never-used address needs 204,600 gas instead of 21,000, and a send with too little is included and fails rather than being rejected (our measurements). We find the fixed gas limits in your withdrawal, payout and bridge paths, the gas fields in your chain or network config and the limits your users sign, and measure each one on Sepolia.

What you get

• A report with each finding: what we read, at which block, what came back, and why it matters on that chain.
• A script for each check that you can re-run against a public RPC.
• The fix in the form you would apply it: a Safe transaction batch, payload calldata, a config value, or a pull request against your docs or code.
• The list of everything we checked that was in order, so you know what was covered.

The check is read-only. We need no key, no admin role and no access to your systems: public chain data, your published docs and your repositories are enough, and we send no transactions. What we find in a paid check is yours, and we publish nothing from it without your agreement.

What it is not

It is not a code audit or a security review. We do not look for vulnerabilities in your contracts, and a clean result is not a guarantee. Nonceworks is not affiliated with Chainlink, OpenZeppelin or the Ethereum Foundation.

Prices

Operations check	$2,400fixed, up to five chains	The five checks above on up to five chains, delivered within ten business days, with the report, the scripts and the fixes.
Operations watch	$600a month	The same checks every week, with an alert when something drifts from the last run: a balance left behind, an address that changes, a job that stops. Cancel any time.
Glamsterdam send-path check	$299per codebase	One repository or service scanned for fixed gas on value sends, estimate-failure fallbacks, "no code, skip the estimate" shortcuts, gas fields in config and signed limits; each hit measured on Sepolia, and on Hoodi after 2026-10-26; a fix with a test for each confirmed failure; one re-check once the values are final.

More chains or more codebases are quoted. Invoices are in USD through Stripe, and USDC is possible on request.

How to start

Write to hello@nonceworks.com or on Telegram with the protocol and the chains; a docs page or an address book is enough to scope it. We reply with the scope and an invoice, and the ten business days start when it is paid.