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

Issue capacities as cellbase outputs in the genesis block #58

Closed
doitian opened this issue Nov 7, 2018 · 1 comment
Closed

Issue capacities as cellbase outputs in the genesis block #58

doitian opened this issue Nov 7, 2018 · 1 comment
Labels
p:should-have Priority: important but not necessary for delivery in the current delivery timebox s:available Status: This issue is available for implementation. t:enhancement Type: Feature, refactoring.

Comments

@doitian
Copy link
Member

doitian commented Nov 7, 2018

Add a new configuration option in chain spec, which configures a list of outputs in genesis block:

  • Each list item must include a lock hash and a capacity.
  • The field data and contract of the outputs are empty.
  • The outputs are added to the cellbase transaction in the genesis block.
  • Ensure the outputs are indexed in the AVL tree.
  • Cellbase transaction reward verifier should be disabled in genesis block.
@doitian doitian changed the title 通过共识参数配置可以在创世块中给多个指定账户发放指定的不同数量的 capacity Issue capacities as cellbase outputs in the genesis block Dec 4, 2018
@doitian doitian transferred this issue from another repository Dec 4, 2018
@doitian doitian added s:available Status: This issue is available for implementation. m:consensus t:enhancement Type: Feature, refactoring. and removed enhancement labels Dec 27, 2018
@doitian doitian added next p:must-have Priority: critical to the current delivery timebox in order for it to be a success p:should-have Priority: important but not necessary for delivery in the current delivery timebox p:wont-have Priority: not appropriate at that time and removed next p:must-have Priority: critical to the current delivery timebox in order for it to be a success p:wont-have Priority: not appropriate at that time labels Jan 7, 2019
@doitian
Copy link
Member Author

doitian commented Jan 11, 2019

Review Log
Last Reviewed At — 2019-01-11

  • Lower its priority to should-have.
  • We need a task to track how the testnet genesis block looks like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p:should-have Priority: important but not necessary for delivery in the current delivery timebox s:available Status: This issue is available for implementation. t:enhancement Type: Feature, refactoring.
Projects
None yet
Development

No branches or pull requests

1 participant