docs(denim): warn about block-number-based contract logic under 200ms blocks - #1949
Open
0x00101010 wants to merge 1 commit into
Open
docs(denim): warn about block-number-based contract logic under 200ms blocks#19490x00101010 wants to merge 1 commit into
0x00101010 wants to merge 1 commit into
Conversation
… blocks Add a Block-Number-Based Contract Logic section to the 200ms Native Blocks page: block.number advances 10x faster in wall-clock time while block.timestamp stays seconds-based, so block-count timelocks, vesting, rate limits, deadlines, block-based governance windows, and TWAP history depth are affected. Align the activation text with the Denim overview's October 2026 planning window. Amp-Thread-ID: https://ampcode.com/threads/T-01a08c4c-75d9-753e-92fa-d96799d82ff0 Co-authored-by: Amp <amp@ampcode.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
🟡 Heimdall Review Status
|
0x00101010
marked this pull request as ready for review
September 10, 2026 17:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Adds a Block-Number-Based Contract Logic section to the Denim 200ms Native Blocks page. Denim moves Base from 0.5 to 5 blocks/s, so
block.numberadvances 10× faster in wall-clock time whileblock.timestampstays seconds-based. Contracts that treat a block count as a duration (timelocks, cooldowns, vesting/emission schedules, per-block rate limits,expirationBlockdeadlines, block-denominated governance windows) will see those durations shrink to one tenth; TWAP oracles keep correct values but retain ~half the history. Teams have asked about this and about activation timing, so the section also lists concrete preparation steps and points to Vibenet for testing.Also aligns the page's activation text and Network Availability table with the Denim overview's October 2026 planning window (the page previously said "undecided" with no month).
Notes to reviewers
clock(), Uniswap V3 observation cadence). No protocol addresses are named in the docs.How has it been tested?
node scripts/lint-mdx.js docs/upgrades/denim/200ms-blocks.mdx— 0 errors, 0 warningsmint devand inspected the new section, table, and callout.Screenshots
Full page of
/upgrades/denim/200ms-blocks— updated top callout, Network Availability table, and the new Block-Number-Based Contract Logic section (before Execution).