Table of Content

Blockmaze Protocol Technical Specification

1. Introduction

This document defines the technical specifications of the Blockmaze protocol. It describes the scope of node operation, system requirements, tooling dependencies, validator responsibilities, protocol performance characteristics, native token usage, and the sovereign chain model.

The specification is intended for developers, node operators, and validators who plan to run or interact with the Blockmaze network. It focuses on operational and infrastructure-level details required to deploy and maintain nodes.

This document does not describe application logic or user-facing features. It outlines only the technical components and assumptions needed to support validator and full node operation within the Blockmaze protocol.

2. Node Setup Scope

The Blockmaze protocol supports two primary node types. Each node type serves a distinct purpose within the network and has different operational requirements.

Validator Node Scope

Validator nodes take part in block production and consensus. They are responsible for validating transactions, producing blocks and maintaining network state.

A validator node must:

  • Remain online with high uptime
  • Follow protocol rules during block production
  • Maintain secure key management
  • Participate in staking and governance processes

Validator nodes require stricter operational discipline compared to other node types due to their role in securing the network.

Full Node Scope

Full nodes maintain a complete copy of the blockchain and provide read access to network data. They do not participate in block production or consensus.

A full node can be used for:

  • Querying blockchain data
  • Supporting applications and services
  • Monitoring network activity

Full nodes help improve network visibility and data availability without carrying validation responsibilities.

3. System Requirements

Running a Blockmaze node requires meeting specific system and infrastructure requirements. These requirements are necessary to support stable operation, block processing and continuous network participation.

Operating System Requirements

Nodes must run on a Linux-based operating system.

  • Operating System: Ubuntu 22.04 or a compatible Linux distribution

Using a supported Linux environment ensures compatibility with required tooling and node software.

Hardware Requirements

Nodes must meet the following minimum hardware specifications:

  • Memory: At least 16 GB of RAM to handle network demands
  • Storage: A minimum of 500 GB of available disk space to store Blockmaze chain data and logs
  • CPU: Minimum 8-core processor

These specifications apply to validator nodes and are recommended for full nodes running long-term services.

Network and Server Setup Requirements

  • Internet Connection: A stable, high-speed internet connection is required to maintain consistent node performance and uptime.
  • Server Setup: Nodes can be deployed either on a cloud-based server or on a locally hosted system. The server must support continuous operation and reliable network connectivity.

Failure to meet these requirements may result in degraded performance or reduced participation in network operations.

4. Tools and Dependencies

The following tools must be installed on the server before setting up a Blockmaze node. These tools are required for building, running and maintaining the node software.

  • Bash: Command-line shell used for running scripts and executing commands.
  • Go: A Go version compatible with the Cosmos SDK requirements must be installed.
  • Jq: A command-line tool used for processing and parsing JSON data.
  • wget: Used for downloading files from external sources.
  • unzip: Required for extracting compressed archive files.
  • build-essential: A package that includes compilers and build tools needed for compiling software from source.

Server Resource Requirement

To operate reliably as a validator, a dedicated server with sufficient computational resources is required. Shared or constrained environments may affect node stability and uptime. Validators may deploy their server on a cloud platform or on local infrastructure.

For reference on cloud-based server setup, the following guide can be used for creating and configuring and EC2 instance:

Reference link:

5. Validator Operations

Validator operations define the core responsibilities that must be followed by all validators participating in the Blockmaze network. These responsibilities are required to maintain network stability, security and correct protocol behavior.

Maintain Uptime

Validators must keep their nodes online and operational at all times.

  • 24/7 Operations: Validator nodes must run continuously to avoid penalties and ensure consistent participation in block production.
  • Redundancy: Validators should implement backup systems to reduce downtime caused by hardware failures or network issues.

Secure the Network

Validators are responsible for protecting their nodes and credentials.

  • Node Security: Validators must follow standard security practices to protect nodes from unauthorized access and attacks.
  • Private Keys: Private keys must be stored securely and backed up in encrypted form.

Adhere to Governance Policies

Validators must operate in line with network rules and governance standards.

  • Compliance: Validators must follow protocol rules and governance decisions defined by the Blockmaze network.
  • Ethical Practices: Validators must participate honestly and fairly to maintain the integrity of the Blockmaze network ecosystem.

6. Throughput and Performance

Network throughput and performance depend on multiple technical factors. These include gas limits, node hardware capacity, network bandwidth and the logic of enabled modules.

  • Block Time: The target block time is approximately 6 seconds.
  • Transactions Per Second: The network can support potentially thousands of transactions per second, depending on application design and configuration.

These values may vary based on network conditions and workload.

7. Native Token (BMZ) and Economics

BMZ is the native token of the Blockmaze ecosystem. It plays a core role in network security, transaction processing and governance participation.

  • Staking and Security: BMZ is used by validators and delegators for staking. Staked BMZ helps secure the network and supports validator participation.
  • Fees: BMZ is used to pay transaction fees on the network. Some zones may use their own native token for fees based on their configuration.
  • Governance: BMZ enables participation in on-chain governance. Token holders can take part in voting and decision-making processes.

8. Customizability and Governance

Blockmaze supports a sovereign chain model that allows flexibility at the zone level.

Sovereign Chains

Each zone operates independently and can define:

  • Its own governance rules
  • Its own tokenomics
  • Its own validator set

This allows zones to operate with autonomy while remaining connected to the broader ecosystem.

Governance

Governance is handled through on-chain mechanisms. Stakeholders can submit proposals and vote on protocol upgrades or parameter changes according to the rules defined by each zone.