-
Notifications
You must be signed in to change notification settings - Fork 531
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
No empty blocks + Heartbeat #419
Comments
This seems to work for launchpad: clayd start --consensus.create_empty_blocks true --consensus.create_empty_blocks_interval 180s I'll try it out on stargate, too.
We save resources and we get a nice reassuring heartbeat every three minutes. Not really sure why the second block came rapidly, but the third took its time like it should have. |
But does that require anything not included with Starport already?
This does not work the way it supposed to for me on Stargate, but not because it hasn't been propagated to |
If you're some significant struggle getting the new version of gaia running and happy I can report that this seems like an issue that is confirmed to starport. When I start a gaia testnet, I can adjust the block times successfully. The version of Gaia I'm using is here: https://github.com/cosmos/gaia/tree/cosmoshub-test-stargate-e What do we know?
There's discussion of removing consensus config/flag options at the tendermint repo, here: I am not 100% certain that this is that, but it certainly sounds like it could be.
Will check.... |
Starport based
Infra is making one block per second. Gaia makes one every five seconds per our request:
Gaia doesn't let us change this setting after genesis:
Key learningIf we fire up infrad without starport, we can adjust the empty block interval:
|
When using stargate with the config.yaml you posted above above, config.toml looks like: # EmptyBlocks mode and possible interval between empty blocks
create_empty_blocks = true
create_empty_blocks_interval = "0s" to keep things lively I tried to set it in two ways: version: 1
accounts:
- name: user1
coins: ["1000token", "100000000stake"]
- name: user2
coins: ["500token"]
validator:
name: user1
staked: "100000000stake"
#FIRST WAY
#init.config:
# consensus:
# create_empty_blocks_interval: "10s"
#SECOND WAY
init:
config:
consensus:
create_empty_blocks_interval: "20s" |
Can be configured using existing features of |
In resource constrained setups, like embedded computers, it may be desirable to tweak the Tendermint settings so that empty blocks are not produced.
This also makes early stage blockchains grow less rapidly-- when there are no transactions, drastically fewer blocks will be produced, I'm wondering if we can make this a part of config.yml or the like.
My off-the-cuff thinking on this is that default should be true (as it is now)
For developers serious about embedded chains, ideal settings might be:
--consensus.create_empty_blocks true
consensus.create_empty_blocks_interval 180
Which would make an empty "heartbeat" block every three minutes.
The text was updated successfully, but these errors were encountered: