WINR Protocol
  • What is WINR?
  • iGaming, Decentralized.
  • Roadmap
  • WINR Protocol
    • WINR VRF
      • Elliptic Curve VRF
      • Verification in WINR
    • Games
    • High-Leverage Trading
    • WINR Wallet
      • Using the WINR Wallet: Quick-Start Guide
    • Liquidity
      • Evolution from WLP to Single-Sided Pools
      • Key Changes in Liquidity Management
      • Distribution Structure
      • Customizable Pools and LP Tokens
      • Security Measures
    • Staking
      • Previous Staking Mechanism
      • Transition to the New WINR Staking on WINR Chain
      • Migration from Arbitrum to WINR Chain
      • Profit Distribution and Epoch Structure
    • Rewards
      • Reward Types
      • Levels and Badges
      • Referral Rewards
    • Fees
  • WINR Chain
    • Overview
    • Core Features of WINR Chain
      • Speed, Reliability, and Cost Effectiveness
      • Account Abstraction
      • Price Feed and RNG Services
    • WINR Bridge: Seamless Cross-Chain Transactions
      • Deposit and Withdrawal Flows on WINR Chain
      • Native Token Transfers with Arbitrum Orbit
      • Cross-Chain Token Bridging with SuperBridge by Socket.io
    • RPC Endpoints and Providers
    • Running a Full Node on WINR Chain
  • BUILD ON WINR
    • Become a Frontend Operator
      • Ready to Use Templates
      • Setting Up Revenue Accounts
      • Deploying Single-Sided LPs
      • Deploy Unique Game Contracts
    • Build a Game
      • WINR Game SDK
      • Example Smart Contract
      • Interacting with VRF and Smart Wallet
      • Interacting with a Frontend
  • EXTRA
    • Governance
    • Tokenomics
    • Contracts
    • Media Kit
    • Audits
Powered by GitBook
On this page
  • Setting Up a Full Node with Docker Compose
  • Explanation of Configuration
  • Running the Node
  1. WINR Chain

Running a Full Node on WINR Chain

Running a full node on the WINR Chain allows users to participate in validating the network, furthers decentralization of the network, and be able to directly access blockchain data for themselves. Users can easily set up a full node with Docker Compose.

Setting Up a Full Node with Docker Compose

To set up a WINR Chain full node using Docker Compose, use the configuration below:

volumes:
  mainnet: {}

services:
  mainnet:
    image: offchainlabs/nitro-node:v3.1.0-7d1d84c
    ports:
      - 8547:8547
      - 8548:8548
    volumes:
      - mainnet:/home/user/.arbitrum
    command:
      - --ws.port=8548
      - --ws.addr=0.0.0.0
      - --ws.origins=*
      - --node.staker.enable=false
      - --node.data-availability.enable=true
      - --node.data-availability.rest-aggregator.enable=true
      - --parent-chain.connection.url=https://arb1.arbitrum.io/rpc
      - --execution.forwarding-target=https://rpc-winrprotocolmainnet-wmwv59m23g.t.conduit.xyz
      - --node.data-availability.rest-aggregator.urls=https://das-winrprotocolmainnet-wmwv59m23g.t.conduit.xyz
      - --node.feed.input.url=wss://relay-winr-mainnet-0.t.conduit.xyz/DQifzKpXv54Zh3vx2NMS5kfbqtPdwjKyu
      - --chain.id=777777
      - --chain.name=conduit-orbit-deployer
      - --http.api=net,web3,eth,debug
      - --http.addr=0.0.0.0
      - --chain.info-json=[{"chain-id":777777,"parent-chain-id":42161,"chain-name":"conduit-orbit-deployer","chain-config":{"chainId":777777,"homesteadBlock":0,"daoForkBlock":null,"daoForkSupport":true,"eip150Block":0,"eip150Hash":"0x0000000000000000000000000000000000000000000000000000000000000000","eip155Block":0,"eip158Block":0,"byzantiumBlock":0,"constantinopleBlock":0,"petersburgBlock":0,"istanbulBlock":0,"muirGlacierBlock":0,"berlinBlock":0,"londonBlock":0,"clique":{"period":0,"epoch":0},"arbitrum":{"EnableArbOS":true,"AllowDebugPrecompiles":false,"DataAvailabilityCommittee":true,"InitialArbOSVersion":11,"InitialChainOwner":"0xD23d1DAF772BDc525842Ebf2B379A305d89DC914","GenesisBlockNum":0}},"rollup":{"bridge":"0xF3f01622Ac969156760c32190995F9dC5b3eb7FA","inbox":"0x4FeBaEF286Ca477402dafCEeB17C64de481aFB42","sequencer-inbox":"0x8AeDdE55Cb361e73a0B0c0cF2A5bB35E97a20456","rollup":"0x2633ea91d15BeE85105C9b27E068f406F2F36a4a","validator-utils":"0x6c21303F5986180B1394d2C89f3e883890E2867b","validator-wallet-creator":"0x2b0E04Dc90e3fA58165CB41E2834B44A56E766aF","deployed-at":211603139}}]
      - --http.corsdomain=*
      - --http.vhosts=*

Explanation of Configuration

  • Ports:

    • The node exposes two ports: 8547 for HTTP and 8548 for WebSocket communication, allowing external applications to interact with your node.

  • Volumes:

    • Blockchain data is stored in a Docker volume named mainnet, ensuring data persistence across container restarts.

  • Node Commands:

    • WebSocket Configuration:

      • Configures the node to accept WebSocket connections on port 8548 with open access from all origins (--ws.origins=*).

    • Execution Forwarding:

      • The node forwards execution to a specified target to ensure that transactions and smart contract interactions are correctly processed.

    • Data Availability:

      • Enables data availability features to ensure that necessary data is accessible for transaction validation.

    • Chain ID and Name:

      • The node is configured with a chain ID of 777777 and a chain name of conduit-orbit-deployer, aligning it with the WINR Chain network.

Running the Node

  • Save the above configuration to a docker-compose.yml file.

  • Start the node using the following command:

shCopy codedocker-compose up -d

This command will launch the node in the background, initiating synchronization with the WINR Chain network. You can monitor the node’s logs and performance using standard Docker commands.

PreviousRPC Endpoints and ProvidersNextBecome a Frontend Operator

Last updated 1 month ago