Skip to content

Mainnet: onboarding request for sentry peering (CL libp2p / EL devp2p) for an independent full node currently in --follow mode #424

Description

@Inah-choi

Request

We operate an Arc mainnet (chain id 5042) full node (arc-node-consensus v0.8.0 + arc-node-execution, AWS ap-northeast-1) in --follow mode, syncing from public RPC endpoints (rpc.mainnet.arc.io, Alchemy, QuickNode). We would like to be onboarded for sentry peering so the consensus layer can sync over libp2p (--p2p.persistent-peers <SENTRY_MULTIADDRS>) and the execution layer over devp2p, as described in docs/running-an-arc-node.md for RPC-provider nodes.

Why

In follow mode the CL pulls each block from the follow endpoints only after they have served it (the log shows SYNC REQUIRED: Falling behind … Requesting sync from peer … Sent value request every block). Measured on our node this puts the node 60–75 ms behind the providers' own newHeads notifications, so a self-hosted node cannot serve pinned-block eth_call/eth_getBlockReceipts earlier than a third-party RPC. Direct sentry peering is the only way we see to run a self-sufficient, low-latency node.

Questions

  1. What is the onboarding route for a non-validator operator to obtain sentry multiaddrs (CL libp2p, port 27000) and EL trusted peers for mainnet? The docs say the addresses are "provided during onboarding" but do not say where to apply (same question as Mainnet: onboarding route for a non-validator operator — need blocks + certificates from height 18,474,680 and ongoing sync (sentry peer or follow endpoint) #356 and What about P2P peering / trusted peers to run an RPC node properly? #423, both still open).
  2. Are there requirements (bandwidth, IP allowlisting, uptime, --p2p.persistent-peers-only, public RPC exposure) we should prepare for?
  3. If sentry peering is validator-only for now, is there a planned timeline for opening it to independent operators, or an alternative lower-latency block feed?

We can provide our node's public IP and libp2p peer id, and are happy to run with --p2p.persistent-peers-only and IP allowlisting on 27000. Thank you.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions