-
Notifications
You must be signed in to change notification settings - Fork 170
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
Weak blocks WIP #1 #2055
base: master
Are you sure you want to change the base?
Weak blocks WIP #1 #2055
Conversation
could also be somewhere else and not known to both A and B). | ||
|
||
Then, for example, miner A is generating a sub-block committing to new transactions after last block. It sends sub-block | ||
header as well as weak transaction ids (6 bytes hashes) of transactions included into this sub-block but not previous |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be worth detailing weak transaction ids a little bit, why 6 bytes of hashes specifically?
when the sub-block time is 1 second, high probability to produce many orphan blocks, is it suitable to still use the longest chain rule? or consider using GHOST algo, greedy heaviest observed sub-tree, to choose the chain, but the security of this chain is also secured by ergo main-chain, so just a suggestion. |
…geSpec externalized
Fixed OpenAPI description for /wallet/getPrivateKey argument
No description provided.