If you have read about Base for a while, you have probably seen the phrase "seven day withdrawal". You may also have seen newer headlines about "ZK proofs" and "multiproofs" that talk about withdrawals finishing in about a day. This guide explains what those terms mean, how they relate, and what they change for you as a wallet user.
A quick refresher: how Base gets its security
Base is a rollup. It runs transactions on its own network, then posts the results back to Ethereum. Ethereum acts as the final referee. The open question every rollup must answer is: how does Ethereum know the results Base posts are correct?
There are two broad answers:
- Optimistic approach: assume the posted result is correct, but leave a window of time in which anyone can challenge it. If nobody proves it wrong, it stands.
- Validity proof approach: attach a mathematical proof to each result so Ethereum can check correctness right away.
Base has historically used the first answer. That is the origin of the seven day delay when moving funds from Base back to Ethereum. Our guide on how Base stays secure covers the optimistic model in more detail.
What is a zero knowledge proof?
A zero knowledge proof is a way to convince someone that a statement is true without handing over all the information behind it. The classic example is proving you know a password without ever showing the password.
For rollups, the statement is something like: "Starting from this previous state, running this batch of transactions correctly produces this new state." A prover does the heavy computation off Ethereum and produces a small proof. Ethereum can verify that proof cheaply, without re running every transaction.
Two things are worth knowing:
- In rollup discussions, the "zero knowledge" label is mostly about the compact, checkable proof. Privacy is not the main goal. A ZK rollup is not automatically private.
- Generating these proofs takes serious computing power. That cost has been a big reason optimistic rollups became popular first.
Optimistic versus ZK, side by side
| Optimistic model | ZK validity proofs | |
|---|---|---|
| Default assumption | Result is right unless challenged | Result is right only if the proof checks out |
| Who can catch a mistake | Anyone watching, during the window | The math itself, before acceptance |
| Withdrawal wait | Long, because the challenge window must pass | Can be much shorter |
| Main cost | Waiting time | Proof generation is computationally heavy |
Neither model is "the safe one" and "the unsafe one". They make different trade offs, and real systems keep evolving.
What Base changed with multiproofs
In 2026, Base shipped an upgrade called Azul. Per Base's own engineering documentation, Azul introduced a multiproof system that combines two kinds of provers:
- A TEE prover. TEE stands for trusted execution environment, a specially isolated piece of hardware that runs code in a way that can be attested. Base's documentation describes this path as using AWS Nitro Enclaves and handling the common case.
- A ZK prover. This is permissionless, meaning anyone can run one. It can back a proposal, or override and dispute one that is wrong.
The key idea is that either proof type can finalize a proposal on its own, but when both agree, withdrawals can finalize in as little as one day. When only one proof backs a proposal, the longer window of seven days still applies. According to press coverage, the upgrade activated on Base mainnet in late May 2026.
In plain terms: two independent systems checking the same result is a stronger signal than one system, so the wait can be shorter when they match.
What this means for you
Everyday swaps and sends are not affected. Moving tokens within Base, or swapping on Base, works as before. Multiproofs concern the path that secures withdrawals from Base back to Ethereum.
Withdrawals to Ethereum may finish sooner. If you use the official route back to Ethereum, the wait can be shorter than the older seven day figure. The exact timing depends on how the proposal was proven, so check the timing shown in the bridge interface at the moment you withdraw rather than assuming. Our guide on withdrawing from Base to Ethereum walks through the steps.
Older articles may still cite seven days. Seven days remains a real number in the system for the slower path, so it was not wrong, but it is no longer the only possible timing.
You do not need to do anything. Base's own announcement described the upgrade as requiring no action from regular users.
Honest caveats
Because this is your money, it helps to be clear about what has not changed and what is still evolving:
- Base's documentation states that this design is not a long term model for the most advanced level of rollup decentralization, sometimes called Stage 2. Stronger proving systems may be adopted over time.
- The TEE path involves specialized hardware and is permissioned in the common case. The permissionless ZK prover is what provides an independent backstop.
- A faster withdrawal path does not remove the general risks of bridging, such as interface mistakes or phishing sites. See why bridging carries different risks than swapping.
- The details of proof systems change as networks upgrade. Treat official Base documentation as the source of truth for current timings and parameters.
A simple mental model
Think of a signed cheque. The optimistic model says: "We will accept it, and give everyone a week to object." A validity proof says: "We will accept it once the signature is verified." Multiproofs say: "If two separate checkers both approve, we can accept it in a day. If only one does, we keep the longer objection window."
Takeaways
- A zero knowledge proof lets Ethereum verify a batch of transactions cheaply without repeating the work.
- Optimistic rollups rely on a challenge window. ZK rollups rely on proofs. Base now combines proof types with multiproofs.
- When both proof types agree, Base withdrawals can finalize in as little as one day. Otherwise the longer window applies.
- Day to day swapping and sending on Base is unchanged.
- Always confirm withdrawal timing in the app you are using and rely on official documentation for the latest details.
This article is educational and not financial advice. Crypto involves risk, and you are responsible for verifying information before moving funds.