mukan-network/mukan-consensus
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
mukan-consensus/.github/ISSUE_TEMPLATE/bug-report.md
Mukan Erkin Törük ef24c0b67e
Some checks are pending
docker-build-cometbft / vars (push) Waiting to run
Details
docker-build-cometbft / build-images (amd64, ubuntu-24.04) (push) Blocked by required conditions
Details
docker-build-cometbft / build-images (arm64, ubuntu-24.04-arm) (push) Blocked by required conditions
Details
docker-build-cometbft / merge-images (push) Blocked by required conditions
Details
docker-build-e2e-node / vars (push) Waiting to run
Details
docker-build-e2e-node / build-images (amd64, ubuntu-24.04) (push) Blocked by required conditions
Details
docker-build-e2e-node / build-images (arm64, ubuntu-24.04-arm) (push) Blocked by required conditions
Details
docker-build-e2e-node / merge-images (push) Blocked by required conditions
Details
initial: sovereign Mukan Network fork
2026-05-11 03:18:27 +03:00

1.6 KiB
Raw Permalink Blame History

name about labels
Bug report Create a report to help us squash bugs! bug, needs-triage

Bug Report

Setup

CometBFT version (use cometbft version or git rev-parse --verify HEAD if installed from source):

Have you tried the latest version: yes/no

ABCI app (name for built-in, URL for self-written if it's publicly available):

Environment:

  • OS (e.g. from /etc/os-release):
  • Install tools:
  • Others:

node command runtime flags:

Config

What happened?

What did you expect to happen?

How to reproduce it

Logs

dump_consensus_state output

Anything else we need to know