Basechain
  • About Basechain
  • Base BigBang Language
    • Introduction
    • 1. Getting started
      • 1.1 Installing BigBangNet
      • 1.2 BigBang basics
    • 2. Type
      • 2.1 Primitives
      • 2.2 Sequences
      • 2.3 Composites
    • 3. Keywords
    • 4. Storing data
      • 4.1 Constants
      • 4.2 Variables
      • 4.3 Maps
    • 5. Functions
      • 5.1 Public functions
      • 5.2 Private functions
      • 5.3 Read-only functions
  • 6. Control flow & error handling
    • 6.1 Asserts
    • 6.2 Try
    • 6.3 Unwrap flavours
    • 6.4 Response checking
  • 7. Using BigBangNet
    • 7.1 Creating a new project
    • 7.2 Writing your first contract
    • 7.3 Interacting with your contract
    • 7.4 Testing your contract
  • 8. Practice projects
    • 8.1 Time-locked wallet
    • 8.2 Smart claimant
    • 8.3 Multi-signature vault
  • 9. Traits
    • 9.1 Defining traits
    • 9.2 Implement traits
    • 9.3 Passing traits as arguments
  • 10. Building a marketplace
    • 10.1 Setup
    • 10.2 Listing & cancelling
    • 10.3 Fulfilling listings
    • 10.4 Uni tests
  • 11. Runtime cost analysis
  • Nodes & Miners
    • Run a Node with Docker
    • Run a Node with DigitalOcean
    • Run a Node with a Hosted Provider
    • Base Node Configuration
    • Mine testnet Base tokens
    • Verify Miner
    • Miner costs and fees
  • Website
  • X(Twitter)
  • Github
Powered by GitBook
On this page
  • Requirements:
  • Quickstart​
  • Accessing the services​
  • Upgrades
  1. Nodes & Miners

Run a Node with Docker

Previous11. Runtime cost analysisNextRun a Node with DigitalOcean

Last updated 1 year ago

With just a few commands, you can run your own Base Blockchain node using . Simply use the base blockchain docker.

Requirements:

Listed below are the minimum viable requirements.

Although it is possible to run a node using these specifications, it is recommended to assign more resources for optimal performance.

  • version 2.2.2 or greater is required

  • 4GB memory

  • 1 Vcpu ( minimum of 2 Vcpu is recommended )

  • 100GB disk ( minimum of 150GB SSD is recommended )

MACOS WITH AN ARM PROCESSOR IS NOT RECOMMENDED

The design of Docker for Mac on an Arm CPU results in slow I/O, which can be problematic for I/O-intensive applications like blockchains. This issue appears to be specific to MacOS, as other Arm-based systems, such as Raspberry Pi, perform as expected.

Quickstart

The <network> placeholder used below can be replaced with one of:

  • mainnet

  • testnet

  • mocknet

  1. Clone the base-blockchain-docker repository locally

git clone https://github.com/Base-Technology/base-blockchain-docker && cd base-blockchain-docker

  1. Start the Services

./manage.sh -n <network> -a start

WITH AN OPTIONAL HTTP PROXY ON PORT 80:

./manage.sh -n <network> -a start -f proxy

TIP

For networks other than mocknet, downloading the initial headers can take several minutes. Until the headers are downloaded, the /v2/info endpoints won't return any data.

Follow the logs to track the sync progress:

./manage.sh -n <network> -a logs

Base-blockchain:

  • Ports 20443-20444 are exposed on localhost

curl -sL localhost:20443/v2/info | jq -r

Base-blockchain-api:

  • Port 3999 is exposed on localhost

curl -sL localhost:3999 | jq -r

proxy:

  • Port 80 is exposed on localhost

curl -sL localhost/v2/info | jq -r
curl -sL localhost | jq -r

Upgrades

Accessing the services

docker-compose
docker-compose
​
​