AI-assisted summary, reviewed by NullTX editors.

According to recent reports, base's Denim upgrade replaced Flashblocks with five canonical blocks per second. What that means for sequencers, RPC providers and smart contract developers is where the real story sits.

For about sixteen months, Base's fastest blocks were only promises. Since November 5, they are the ledger itself.

Denim went live on Base mainnet on November 5, after activating on Sepolia on October 21.

According to the upgrade page, the chain now produces five complete canonical blocks every second instead of one every two seconds. Flashblocks, the preconfirmation layer that ran alongside the two-second blocks since July 2025, is retired.

Most coverage stopped at the speed figure. The sharper question is what separates a canonical block from a preconfirmation, because that gap decides what breaks and what improves for anyone building on the chain.

Those updates were the sequencer's early word on what the next block would contain. They were previews of pending state, and nothing in them had its own hash, state root or receipts until the two-second block was sealed. Developers therefore had to keep an early execution result mentally separate from a settled transaction.

It has been revealed that denim turns the 200ms unit into the real thing. Under Base's 200ms Native Blocks specification, every block carries its own number, hash, state root, receipts and forkchoice updates, and moves through the unsafe, safe and finalized stages like any other block.

Sources indicate that the sequencer's job gets heavier and stricter. Instead of streaming fragments of a larger block, it has to build and execute a full block for every 200ms slot. The header keeps its timestamp in whole seconds, so Denim adds a metadata transaction, the BaseTime deposit, placed second in every block. It supplies the sub-second portion: 0, 200, 400, 600 or 800 milliseconds.

Timing rules are tight. Slots can't be skipped, and each block's full timestamp must land exactly 200ms after its parent's. That timestamp comes from a schedule tied to the Denim activation and the block number, not from the sequencer's clock, so wall-clock time only determines when a build begins. Once execution finishes, the client rejects any block that breaks the 200ms progression.

Industry observers note that this removes a layer of ambiguity. A preconfirmation was only as strong as the sequencer's word, while a canonical block can be validated, replayed and challenged by any node running the same derivation rules.

Industry observers note that app developers face the biggest practical shift. Flashblocks streams ended at activation, so anything built on newFlashblocks, pendingLogs or the pending block tag has to move to canonical subscriptions like newHeads and logs. The migration guide lists the API changes required.

The seconds-based timestamp field stays as it was for compatibility. Block, header, transaction, log and receipt responses now include optional millisecond fields, timestampMs and blockTimestampMs, derived from authenticated BaseTime data. They are left out when that data has been pruned or is unavailable. One tooling detail deserves attention: the spec warns that the plain Alloy AnyRpcHeader type drops unknown fields, so anyone who needs millisecond timestamps must use a different type.

It has been revealed that node providers will see heavier traffic too. Dwellir's analysis notes that any service doing work on every block now does it ten times as often. Five fetches a second replace one every two seconds. Denim improves latency without adding capacity, so infrastructure bills are likely to climb.

Recent findings suggest that finality hasn't gone away either. Faster production doesn't erase the confirmation policy an application picks, and each 200ms block still passes through the same unsafe, safe and finalized stages. Bridges and exchanges that wait for a specific stage before crediting funds may need to rethink how many blocks they wait for, since a block count no longer equals the same stretch of time.

This is the area that deserves the most urgent attention. Base's spec warns that block.number now advances ten times faster in real time, while block.timestamp still ticks in whole seconds. A contract that treats a block count as a duration will see that duration collapse to a tenth of what its authors intended.

According to recent reports, the affected patterns are common ones. Timelocks and cooldowns measured in blocks expire in a tenth of the time. Vesting and emission schedules run ten times faster. Per-block rate limits reset five times a second instead of once every two seconds, which lifts the effective per-second limit tenfold. Governance voting windows set in blocks shrink the same way. Uniswap V3-style TWAP oracles stay accurate, but a fixed observation cardinality now covers less wall-clock history, so long lookbacks can revert sooner.

Contracts built on block.timestamp are unaffected. Where a block count can be adjusted through governance, teams proposal to divide it by ten. Where it is hardcoded into an immutable contract, the spec says it can't be retuned after activation, which leaves migration as the only fix. Denim also tightens transfer rules for Base's B20 token standard, and transfers to a token's own address now revert.

Recent findings suggest that the coming weeks will show how much of this stays theoretical. Three things are worth tracking: whether any immutable contract with block-count logic misbehaves, how providers cope with the jump in per-block requests, and whether apps built around Flashblocks have fully moved over.

Denim looks like a cleaner design than the layer it replaced. A preview mechanism gives way to a block anyone can verify, and developers pay for it with a real migration. Speed grabbed the headlines, but the lasting change is that Base's sub-second confirmations now stand on the same footing as the chain's ordinary blocks.

Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on X @nulltxnews.

According to recent reports, updated look back: this article revisits a 2018 story with what has happened since.In February 2018, MIT Technology Review put zero-knowledge proofs on its list of 10 Breakthrough Technologies under the title "Perfect Online Privacy", and singled out zk-SNARKs as the practical version. zk-STARKs, published a few weeks earlier, did not replace SNARKs, but the….

Enjin holders vote through November 13 on moving Matrixchain to OpenGov on November 16. Here is how the nine tracks, the 1,000 ENJ deposit and conviction voting work, and what the Relaychain vote shows.Enjin's fresh proposal deposit sounds steep at 1,000 ENJ. It's actually the cheap part.The Vote Closes Today and Matrixchain Governance Hangs on ItEnjin holders….

SlowMist indicates five forged receipts with valid signatures let an attacker drain about $304,500 from Ankr's Ethereum bridge using one old Optimism deposit. Here is how the check failed.Every one of the five receipts was signed by the bridge's own trusted signer. Every one pointed to a deposit that had already been paid out.Five Withdrawals Against One Settled….

It has been revealed that the SEC's crypto broker-dealer proposal, RIN 3235-AN48, is under White House review with no public text. Here is what the four named rules require today and what review means.Four rules written decades before Bitcoin existed are now sitting at the White House for a crypto rewrite, and nobody outside the SEC has seen a word of the draft. What is known is the….

One email a week with our latest explainers and the news behind them.

More explainers and analysis from NullTX.

→ Read original article