The signals that matter put a date on a vendor decision: a network upgrade or testnet shutdown that forces client and tooling changes, a deployment to a new chain, a jump in deposits that raises load and risk, and a governance post or engineering hire that names the function you sell. Posts and listings without a date rarely do.
Which signals put a date on the decision?
Six signal types do, and each points to a different buyer at the protocol.
| Signal | What it forces | Where to watch | Who to contact |
|---|---|---|---|
| Scheduled network upgrade | Client, builder and validator tooling updates before activation | Core developer blogs, client release notes | Staking operators, node teams, block builders |
| Testnet shutdown | Test infrastructure moves to a new network | Foundation blogs | Infrastructure leads at protocols and operators |
| Deployment to a new chain | A new RPC, oracle, indexing and bridge choice for that chain | Governance forums, testnet docs | CTO or head of engineering |
| Deposit or volume jump | More load on data providers, more value behind each price update | DefiLlama TVL, on-chain volume dashboards | Head of engineering, risk lead |
| Governance post that names a function | A vendor change that needs a vote | DAO forums and Snapshot spaces | Proposal author, delegates, risk service providers |
| Infrastructure engineering hire | A build-or-buy decision on nodes, data or MEV | Careers pages, job boards | CTO, hiring manager |
Each row names its own owner. A message about an upgrade goes to operations, and a message about a deposit jump goes to engineering or risk.
How do network upgrades create infrastructure demand?
An upgrade gives every operator on the network the same deadline. Ethereum's next upgrade, Glamsterdam, was scheduled to activate on the Sepolia testnet on 6 October 2026, and Hoodi and mainnet dates had not yet been decided (Ethereum Foundation, 28 September 2026).
Glamsterdam includes enshrined proposer-builder separation (EIP-7732), under which the protocol handles the payment from builder to proposer. The Foundation says this reduces reliance on trusted middleware between the two. It told staking operators to review their client's instructions for new ePBS duties and for any changes to builder or validator tooling. For a company that sells MEV, relay, builder or validator software, every Ethereum staking operator now has a dated reason to review its stack.
Testnet shutdowns work the same way at smaller scale. On 1 September 2025, the Foundation said most Holešky validators would shut down two weeks after the Fusaka upgrade finalised there. Staking operators and infrastructure providers were told to move to Hoodi, and application developers to Sepolia (Ethereum Foundation, September 2025). Every team still on Holešky had to rebuild its test setup on a known date.
Write when the date is announced. Teams test changes on the testnet fork first, so the vendor choice happens before that fork and well before mainnet.
Why does a deployment to a new chain matter?
Each deployment repeats the vendor decision. A lending protocol live on four chains chose RPC, oracle and indexing providers four times, and it chooses again on the fifth.
Governance forums show these decisions early. A deployment proposal often names the oracle, bridge and data providers the team plans to use. If the proposal names an incumbent in your category, the slot is taken for that deployment. If it names none, or asks for comments on providers, the slot is open and the proposal author is your contact.
What does a jump in deposits tell an infrastructure seller?
More deposits mean more requests to data providers, more liquidations to process and more value behind each oracle update. Our catalyst monitor logged 566 TVL moves and 40 new DeFi listings among 6,069 buying signals between 26 July and 7 October 2026 (our data, October 2026; the monitor watches a fixed list of target companies across X, job boards, crypto news and DefiLlama).
Read a rise as a reason for a capacity or risk review, and write to engineering or risk with a figure from your product at that size. A sustained fall can matter too if you sell on price, because a protocol earning less in fees reviews its vendor bills. A new listing on its own says only that the protocol exists. Pair it with a deployment date or a governance post before you write.
What does an infrastructure engineering hire mean?
A job post for a node, site reliability or MEV engineer says the team plans to run the function itself. That opens a build-or-buy window that closes once the hire starts.
In general B2B outbound, engineering roles say little about a sales budget, and we drop them for that purpose, as covered in which buying signals predict a B2B purchase. For an infrastructure seller the same post is a direct signal. Write to the hiring manager with a cost comparison: the loaded cost of the hire and the time to production, set against your price and your setup time.
How do you rank the signals you collect?
Score each signal before anyone writes. Use these steps:
- Match the signal to exactly one company, and confirm the domain in the signal matches the company you found. Skip the signal if it does not.
- Add 2 points if the signal names a date in the next 90 days.
- Add 2 points if it names the function you sell.
- Add 1 point if you can name the person who owns the decision.
- Subtract 1 point if a proposal or the chain's docs name an incumbent in your category for this deployment.
- Write to signals that score 4 or more within a week. Log the rest and check them again when a second signal arrives.
The first step does the most work. We caught two namesake errors in our own signal matching, where a signal for one company matched a different firm with the same name (our data, October 2026). An email about an upgrade or a deployment that the reader never planned costs more than a skipped signal.
What is the decision rule?
Act on a signal when it names one company, a date and your function. Write to the person who owns that function, open with the dated fact from the signal, and send before the testnet fork, the deployment vote or the hire's start date.
To get signal sources and scoring rules set up for the protocols in your category, start with The Diagnostic at $2,500.