jmcanterafonseca-iota
commented
2 years ago this should be made configurable
On Tue, Feb 8, 2022 at 4:19 PM sikhness @.***> wrote:
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.
- Clone repository and follow steps to run private tangle
- 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.
— Reply to this email directly, view it on GitHub https://github.com/iotaledger/one-click-tangle/issues/72, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQEZJLRJAZPQZW3DD7L4QM3U2EYADANCNFSM5N2YRSHQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- IOTA Foundation Pappelallee 78/79 10437 Berlin, Germany
Board of Directors: Dominik Schiener, Navin Ramachandran ID/Foundation No.: 3416/1234/2 (Foundation Register of Berlin)
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?
Steps To reproduce the bug
Explain how the maintainer can reproduce the bug.
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.