Skip to content

Conversation

@pete-vielhaber
Copy link
Contributor

  • 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)

@vercel
Copy link

vercel bot commented Jan 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
arbitrum-docs Ready Ready Preview Jan 30, 2026 6:52pm

Request Review

Copy link

@EmreDincoglu EmreDincoglu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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({

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

pete-vielhaber and others added 2 commits January 29, 2026 14:32
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants