Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

review & fix jormungandr configuration to enable block production in BFT mode #382

Merged
merged 1 commit into from
Jun 6, 2019

Conversation

KtorZ
Copy link
Member

@KtorZ KtorZ commented Jun 6, 2019

Issue Number

#219

Overview

  • I have reviewed & fixed jormungandr configuration to enable block production in BFT mode

Comments

Not sure how the leader ids were generated in the genesis file but, it didn't match the public key of the signing key given as configuration. Now fixed and Jormungandr correctly produces block in BFT mode now.

Note that because the node is alone, it schedules a lot of blocks which result in quite a lot of messages (and eventually error messages from the logger which can't keep up). I've alerted the rust team and they're looking into it.

@KtorZ KtorZ requested a review from Anviking June 6, 2019 16:46
@KtorZ KtorZ self-assigned this Jun 6, 2019
@@ -22,19 +22,19 @@ blockchain_configuration:
block0_consensus: bft

# Number of slots in each epoch
slots_per_epoch: 2160
slots_per_epoch: 500
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to avoid too many blocks in the schedule which makes the logger panics otherwise 🤷‍♂️ ... And, it'll be fun to not use 2160 slots per epoch, I am sure of it.


# The number of blocks (*10) per epoch
epoch_stability_depth: 10

# A list of Ed25519 Extended PublicKey that represents the
# BFT leaders encoded as bech32. The order in the list matters.
consensus_leader_ids:
- ed25519e_pk1xznffwqdhw3drw9yk4t99vpajcc4epq5kp205um5gkkz625xt3mqn4z3mx
- ed25519_pk1kgtwuwy0cf2edn6rl09gzhzx8sma09tqhxzcqrpaduaq7k5h0ceqe4qqpv
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, this was the main reason blocks weren't produce. The leader defined in the genesis file was not the one pointed by the node configuration...

@@ -21,7 +21,7 @@ spec = describe "cardano-wallet-launcher" $ do
let jormungandrLauncher = Command
"jormungandr"
[ "--genesis-block", dir ++ "/block-0.bin"
, "--config", dir ++ "/node.config"
, "--config", dir ++ "/config.yaml"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using .yaml since this is actually a yaml file...

Copy link
Collaborator

@Anviking Anviking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😮 Thanks @KtorZ!

lgtm - It produces blocks when I run it.

@Anviking Anviking force-pushed the KtorZ/jormungandr-produces-blocks branch from b4aa361 to 290a18e Compare June 6, 2019 17:37
@Anviking Anviking merged commit 1bc3413 into master Jun 6, 2019
@Anviking Anviking deleted the KtorZ/jormungandr-produces-blocks branch June 6, 2019 17:56
@KtorZ KtorZ mentioned this pull request Jun 10, 2019
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants