The length depends on who signs. A core team that signs alone moves at its engineers' pace. A deal that needs a DAO vote carries fixed minimums: 11 days of votes and delays at Aave, 23 at Uniswap and 27 to 42 at Arbitrum. Aave's first Chainlink SVR integration took 91 days from first forum post to on-chain vote.
What sets the length of the cycle?
The signer sets it. Infrastructure deals in crypto go to four kinds of signer, and only one of them publishes its timetable.
| Who signs | Gates before the signature | Public timing |
|---|---|---|
| Validator or staking operator | Testnet trial, software update, slashing review | None; set by their own upgrade schedule |
| Protocol core team or multisig | Technical review, integration audit, commercial terms | None |
| DAO | Forum discussion, off-chain vote, on-chain vote, timelock | Fixed minimums in the DAO's docs |
| Exchange, custodian or institution | Security review, vendor onboarding, legal | Set by their procurement; ask your champion |
Find out in the first call which row you are in. Ask who signs, whether the change needs a vote, and what the last comparable vendor took from first meeting to live.
How much time does DAO governance add?
Between 11 and 42 days at minimum, before any engineering. These are the documented minimums for three large DAOs, as of 15 October 2026:
| DAO | Steps and durations | Minimum |
|---|---|---|
| Aave, standard proposal | Temp Check Snapshot 3 days, ARFC Snapshot 3 days, 1-day delay after on-chain submission, 3-day vote, 1-day timelock (Aave) | 11 days |
| Aave, long executor | Same off-chain steps, then a 10-day vote and a 7-day timelock | 24 days |
| Uniswap | Forum RFC at least 7 days, temperature check 5 days, 2-day wait, 7-day vote, 2-day timelock (Uniswap) | 23 days |
| Arbitrum, non-constitutional | Forum and temperature check, formal proposal, 14 to 16-day vote, L2 waiting period (Arbitrum Foundation) | 27 days |
| Arbitrum, constitutional | The same, plus an L2-to-L1 message and a 3-day L1 waiting period | 42 days |
The minimums exclude three things: the commercial talks before the first forum post, the drafting of the proposal, and the engineering after execution. Real proposals take longer.
What does a real integration timeline look like?
Aave's first integration of Chainlink's Smart Value Recapture (SVR) oracles is fully public on its forum. SVR recaptures MEV from Aave liquidations and returns part of it to the DAO.
| Date | Step |
|---|---|
| 23 December 2024 | Temp Check posted on the Aave forum |
| 22 January 2025 | Temp Check Snapshot vote created |
| 4 March 2025 | ARFC for Phase 1 posted, covering a subset of Aave v3 Core Ethereum assets |
| 10 March 2025 | ARFC Snapshot vote created |
| 24 March 2025 | On-chain proposal 274 created, with voting set to start about 24 hours later |
| 4 April 2025 | Chainlink Labs reported SVR working on live liquidations over the prior week |
From first post to on-chain proposal took 91 days, against an 11-day minimum. The forum thread shows where the time went: community discussion, published reviews from two risk service providers, and a decision to split parameter changes out of the activation proposal. Talks between the two teams before 23 December 2024 do not appear in the record, so the full cycle ran longer than 91 days.
Why is the second deal faster?
The first proposal settles whether the function belongs in the protocol at all. Later proposals only change the scope.
Aave's later SVR steps show it. Phase 2 went through the Direct-to-AIP framework: the forum post went up on 1 May 2025 and the on-chain proposal on 7 May 2025, six days later (Aave forum). The expansion to Base and Arbitrum moved from ARFC on 6 March 2026 to on-chain proposal on 23 March 2026, 17 days (Aave forum).
Forecast the first integration with a DAO as a long deal. Forecast expansions from your own last proposal in that DAO, because the forum has already approved the idea.
How do you forecast a governance-dependent deal?
Work backwards from the date the integration must be live. Use these steps:
- Pick the live date.
- Subtract the timelock and the voting period for the executor your change needs.
- Subtract the delay between on-chain submission and the vote.
- Subtract each off-chain vote and the forum minimum.
- Add the time that comparable proposals in the same forum spent in discussion and risk review.
- The result is the latest date for the first forum post. Agree commercial terms before that date.
A worked example for Uniswap with a live date of 1 March 2027: the 2-day timelock puts the vote's end at 27 February. The 7-day vote means it opens on 20 February, after a 2-day wait from 18 February. The 5-day temperature check must start by 13 February, and the 7-day RFC by 6 February. That is the floor. Step 5 then pushes the first post earlier, and in the Aave case above it added about 80 days.
How do you shorten the cycle?
Remove the reasons a forum slows down:
- Publish parameters, failure cases and a rollback plan with the first post, so risk reviewers start from your numbers.
- Brief the largest delegates and the DAO's risk service providers before you post.
- Start with a subset of assets or one deployment, as Aave's SVR Phase 1 did, so the first vote covers a small change.
- Ask whether a fast path applies, such as Aave's Direct-to-AIP route for follow-on proposals.
For exchanges and custodians, the slow step is diligence, and a prepared pack shortens it. The contents are in how crypto infrastructure firms book meetings with institutions. Each live integration then becomes proof for the next signer, as described in how blockchain infrastructure protocols grow market share.
What is the decision rule?
Forecast a first DAO deal at the documented minimum plus the discussion time of comparable proposals in that forum. Forecast a deal with a core team or operator from your own closed deals with that type of signer. Forecast an expansion from your last proposal in the same DAO.
To get your open deals mapped by signer type, with governance dates set against your forecast, start with The Diagnostic at $2,500.