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

Single node configuration for development environment #42

Closed
longfin opened this issue Jan 18, 2019 · 3 comments
Closed

Single node configuration for development environment #42

longfin opened this issue Jan 18, 2019 · 3 comments
Labels
stale The issue is stale suggestion Suggestion or feature request

Comments

@longfin
Copy link
Member

longfin commented Jan 18, 2019

Currently, the only way to correctly generate a block is to call Blockchain.MineBlock() to mine block. However, in a development environment that typically consists of a single node, mining has a large variation in resource usage, making it difficult to guarantee the block creation time. it sometimes makes development and testing difficult.

So for a development or test chain, we need a method (e.g. configuration) that allows us to create a valid block without these mining processes.

@longfin longfin added the suggestion Suggestion or feature request label Jan 18, 2019
@dahlia
Copy link
Contributor

dahlia commented May 20, 2019

I think we can now achieve this by implementing a custom IBlockPolicy<T>. Or do we need a kind of façade (which implements IBlockPolicy<T>) for single node?

@stale
Copy link

stale bot commented Oct 30, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale The issue is stale label Oct 30, 2019
@stale stale bot closed this as completed Nov 6, 2019
@limebell limebell reopened this Nov 7, 2019
@stale stale bot removed the stale The issue is stale label Nov 7, 2019
@stale
Copy link

stale bot commented Jan 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale The issue is stale label Jan 6, 2020
limebell pushed a commit to limebell/libplanet that referenced this issue Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue is stale suggestion Suggestion or feature request
Projects
None yet
Development

No branches or pull requests

4 participants