Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Private tangle coordinator configuration has milestone generation set to 60s #72

Open
sikhness opened this issue Feb 8, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@sikhness
Copy link

sikhness commented Feb 8, 2022

Bug description

In the config-coo.json, the milestone generation it set to 60s. This makes the network confirm messages much slower as Chrysalis should be set to 10s.

What hardware are you using?

  • Operating system: Windows 10
  • RAM: 32GB
  • Cores: 6 cores

Steps To reproduce the bug

Explain how the maintainer can reproduce the bug.

  1. Clone repository and follow steps to run private tangle
  2. config-coo.json will have coordinator interval set incorrectly to 60s

Expected behaviour

The config-coo.json should be set to 10s to speed up confirmation times as per Chrysalis specifications.

Actual behaviour

Coordinator confirmations happen 5 times slower.

@sikhness sikhness added the bug Something isn't working label Feb 8, 2022
@jmcanterafonseca-iota
Copy link
Collaborator

jmcanterafonseca-iota commented Feb 8, 2022 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants