Skip to content

kagami_profiles.md

Latest commit

 

History

History
15 lines (12 loc) · 1.96 KB

kagami_profiles.md

File metadata and controls

15 lines (12 loc) · 1.96 KB
Raw

Kagami Iroha3 Profiles

Kagami ships presets for Iroha 3 networks so operators can stamp deterministic genesis manifests without juggling per-network knobs.

  • Profiles: iroha3-dev (chain iroha3-dev.local, collectors k=1 r=1, VRF seed derived from the chain id when NPoS is selected), iroha3-taira (chain iroha3-taira, collectors k=3 r=3, requires --vrf-seed-hex when NPoS is selected), iroha3-nexus (chain iroha3-nexus, collectors k=5 r=3, requires --vrf-seed-hex when NPoS is selected).
  • Consensus: Sora profile networks (Nexus + dataspaces) require NPoS and disallow staged cutovers; permissioned Iroha3 deployments must run without a Sora profile.
  • Generation: cargo run -p iroha_kagami -- genesis generate --profile <profile> --ivm-dir . --genesis-public-key <pk> --consensus-mode <npos|permissioned> [--vrf-seed-hex <hex>]. Use --consensus-mode npos for Nexus; --vrf-seed-hex is only valid for NPoS (required for taira/nexus). Kagami pins DA/RBC on the Iroha3 line and emits a summary (chain, collectors, DA/RBC, VRF seed, fingerprint).
  • Verification: cargo run -p iroha_kagami -- verify --profile <profile> --genesis <path> [--vrf-seed-hex <hex>] replays profile expectations (chain id, DA/RBC, collectors, PoP coverage, consensus fingerprint). Supply --vrf-seed-hex only when verifying an NPoS manifest for taira/nexus.
  • Sample bundles: pre-generated bundles live under defaults/kagami/iroha3-{dev,taira,nexus}/ (genesis.json, config.toml, docker-compose.yml, verify.txt, README). Regenerate with cargo xtask kagami-profiles [--profile <name>|all] [--out <dir>] [--kagami <bin>].
  • Mochi: mochi/mochi-genesis accept --genesis-profile <profile> and --vrf-seed-hex <hex> (NPoS only), forward them to Kagami, and print the same Kagami summary to stdout/stderr when a profile is used.

The bundles embed BLS PoPs alongside topology entries so kagami verify succeeds out of the box; adjust the trusted peers/ports in the configs as needed for local smoke runs.