Polygon FastLane
  • What is Polygon FastLane?
    • Overview
    • Design Principles
    • Components
    • Component Diagram
  • Getting Started as a Validator
    • Getting Started as a Validator
    • Connecting to a FastLane Sentry Node
      • Finding Your Enode Address & Peer ID
      • Adding FastLane as a Static Peer
    • Patching Your Sentry Nodes With The FastLane Patch
      • Installing from source
        • Patch Download
        • Patch Installation
      • Installing from packages
  • Withdrawing Validator Revenue
    • Validator Vault
      • Connect an Eligible Wallet
      • Revenue Redemption (withdrawal)
  • Searcher Guides
    • Getting Started as a Searcher
      • Solver Call Data
      • Submission Methods
      • Migration Guide for Searchers
    • Bundles (Backruns)
      • Bundle Format
      • Bid Submission
      • Bundle Requirements
      • Full Example
      • Subscribe Events
    • 4337 Bundles Integration Guide
      • Overview
      • How it works
      • RPC Reference
      • Examples
    • Searcher Contract Integration
      • Safety Considerations
      • atlasSolverCall
      • Direct Implementation
      • Proxy Implementation
      • Solver Concepts
      • Altas Bonding Concept
      • Bond atlETH
      • Estimating Solver Gas Charges
    • Addresses & Endpoints
    • Helpers
    • Common Mistakes
    • Atlas SDK's
  • Tools and Analytics
    • FastLane Bundle Explorer
      • Features Overview
      • Key Components
      • Usage Example
      • Error Codes & Troubleshooting
  • Key Concepts
    • Transaction Encoding
  • INFRASTRUCTURE
    • Health Status Endpoint
  • Reference
    • Relay JSON-RPC API
    • Relay REST API
    • Glossary of Terms
Powered by GitBook
On this page
  1. Getting Started as a Validator
  2. Connecting to a FastLane Sentry Node

Adding FastLane as a Static Peer

PreviousFinding Your Enode Address & Peer IDNextPatching Your Sentry Nodes With The FastLane Patch

Last updated 1 year ago

The validator node must label the FastLane Sentry as a "static peer." This can be accomplished by using one of the following:

  • Add the FastLane Sentry enode in the validator's /home/ubuntu/node/bor/bor_config.toml or ~/.bor/data/bor/static-nodes.json peers file.

  • Runadmin.addPeer(enode://fastLaneSentryEnode@PFL.IP.0.0:30303) command inside of Bor (bor attach ~/.bor/data/bor.ipc). This will have to be run each time Bor restarts.

  • List the FastLane Sentry node as one of its "boot nodes" during startup.

MAXPEERS Configuration

Validators are urged to check their MAXPEERS setting. It has been our experience that most peering failures are due to the validator node's MAXPEERS value not being increased by the number of FastLane Sentry nodes being added as new peers.

<- Back to "Connecting to a FastLane Sentry Node"