-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
RPC getblocktemplate not return POW Cummulate or other information #209
Comments
This is an example not violent. Attack can be optimized to take all the block with 15% of hashrate |
Of course my pool not using the attack |
You're incorrect - getblocktemplate returns more than that, and it definitely returns the difficulty. Per https://github.com/monero-project/bitmonero/blob/master/src/rpc/core_rpc_server_commands_defs.h#L383 -
|
How make difference between block bad branch block good branch after reorganize blockchain with same height |
Though the longest chain rule. The longest chain may take many blocks to find, but that's the way it works. There's literally no change we can make to getblocktemplate to circumvent or change this basic nature of a consensus system. I would suggest you read up on the longest chain rule. |
Present, getblocktemplate return only blob and height of blocktemplate .
No code can make difference between block 325454 and block 325454 result new branch after fork .
Present ,All pool continue mining for previous blocktemplate and not blocktemplate generate per new branch .
Exemple of attack.
1.) Pool mining regular .
When one miner find diff more 500% of diff research Ex: block 325454
Submit block 325454 and not broacast block
Other pool continue mining of block 325454 and heavy pool mining block 325455
2a ) Other pool find block 325454 ( Jackpot )
Wait 5 secondes and broacast block with diff more 500% . Blockchain fork and new branch is create .
All other pool continue mining of badblock 325455
You are all time for find block 325455 ( only solo mining for concurence )
Attack is easy is block diff is per exemple 500% not broadcast and mining next block .
If same block is find per network broadcast block with diff 500% and continue mining on solo .
All pool as block find reject per bitmonerod.
The text was updated successfully, but these errors were encountered: