docs: tw589-seq-timing-adjustments#3024
Conversation
pete-vielhaber
commented
Jan 20, 2026
- Generated content for sequencer timing adjustments
- needs thorough review
- questioning placement; this may be better combined into a single page and placed under Arbitrum Node Runners (under Launch Arbitrum Chain)
This reverts commit a60b607.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
EmreDincoglu
left a comment
There was a problem hiding this comment.
Im decently knowledgeable about most of these topics but if anyone else could review it I think that would be good.
| ```typescript | ||
| import { prepareNodeConfig } from '@arbitrum/orbit-sdk'; | ||
|
|
||
| const nodeConfig = await prepareNodeConfig({ |
There was a problem hiding this comment.
So im looking at the chain SDK and while you should override the node config file. I do not see any parameters you can add to prepareNodeConfig function (Specifically for overriding), and looking where the execution part is, it seems to be hard coded, so needing to override the info is correct, but it cannot be done via using the prepareNodeConfig function, it can only be done after you have received the var containing the nodeConfig information
…nfig-sequencer-timing-adjustments.mdx Co-authored-by: Emre Dincoglu <85258206+EmreDincoglu@users.noreply.github.com>
…nfig-sequencer-timing-adjustments.mdx Co-authored-by: Emre Dincoglu <85258206+EmreDincoglu@users.noreply.github.com>
…nfig-sequencer-timing-adjustments.mdx
| @@ -35,16 +35,13 @@ import { prepareNodeConfig } from '@arbitrum/orbit-sdk'; | |||
| const nodeConfig = await prepareNodeConfig({ | |||
There was a problem hiding this comment.
I would move the if statements out of the function call since it looks like you send them into the function. Other than that as long as in this tutorial the goal is to set some of these values aka the max-block-speed and max-delay then this should be good