Skip to content
Hikmalayer Core edited this page Feb 17, 2026 · 2 revisions

# Welcome to the hikmalayer-core wiki!

Overview

Hikmalayer is a hybrid Layer-1 blockchain prototype combining:

  • Proof-of-Stake (validator selection)
  • Proof-of-Work (block finalization)
  • Governance and slashing mechanisms
  • Token execution layer
  • REST API interface
  • Dockerized multi-node deployment

The project is developed by Muhammad Ayan Rao, founder and director of Bestower Labs, and maintained by Bestower Labs Limited.

Current Status

Hikmalayer has completed Phase-4 validation:

  • Multi-container Docker deployment operational
  • REST execution layer benchmarked
  • Monitoring stack active (Prometheus + Grafana)
  • Sustained transaction throughput validated
  • Operational tooling hardened Phase-5 introduces peer-to-peer validator networking and public testnet deployment.

Architecture Summary

Core Components

  • Blockchain engine (block validation, PoW)
  • PoS validator selection
  • Token subsystem
  • Governance configuration
  • Persistence layer
  • REST API server
  • Monitoring integration

Deployment Modes

  • Single-node (local development)
  • Multi-container (Docker Compose)
  • Planned: multi-host P2P testnet

Repository Structure

src/ blockchain/ consensus/ token/ contract/ api/ auth/ persistence/ bench/ docs/ ops/ dashboard/

Running Hikmalayer

Local Development

cargo run

Docker Deployment

docker compose up -d --build

RPC default:

http://localhost:3010

Benchmarking

Benchmark harness located in:

bench/

Phase-4 benchmark artifacts:

bench/results/run_10min/

Documentation

Whitepaper: docs/Whitepaper.md

Consensus Flow: docs/consensus_flow.md

Security Hardening: docs/security_hardening.md

Threat Model: docs/threat_model.md

Roadmap

  • Phase 1 – Core PoW primitives
  • Phase 2 – PoS validator logic
  • Phase 3 – Persistence and governance
  • Phase 4 – Operational hardening and benchmarking
  • Phase 5 – Public P2P testnet

Contributing

See:

LICENSE

CLA.md

Pull requests should follow the existing module structure and maintain consensus integrity.