mirrors/mempool
1
0
Fork 0
mirror of https://github.com/mempool/mempool.git synced 2025-02-22 06:21:46 +01:00
Code Issues Projects Releases Wiki Activity

Update frontend/src/app/docs/api-docs/api-docs.component.html

Browse source 
Co-authored-by: mononaut <83316221+mononaut@users.noreply.github.com>
This commit is contained in:
BitcoinMechanic 2024-05-12 23:05:55 -07:00 • committed by GitHub
parent 64d979d5f9
commit 16c154f39d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
frontend/src/app/docs/api-docs/api-docs.component.html
View file

@ -238,7 +238,7 @@
</ng-template>
<ng-template type="why-empty-blocks">
<p>When a new block is found, mining pools send miners a block template with no transactions so they can begin doing useful work as soon as possible. The pool will then send a block template full of transactions right afterward, and the miners will usually have it in under a second.</p><p>Miners sometimes get lucky and find the empty block in the interim period before having the full template however this is rarely the reason for an empty block as it's such a small amount of time.</p><p>The usual cause is that some mining hardware will continue to work on old work for up to 60 seconds despite having newer work. This is also why when comparing "Actual Blocks" with "Expected Blocks" on mempool.space you will often observe slightly lower fees in the blocks found than what's theoretically possible.</p>
<p>When a new block is found, mining pools send miners a block template with no transactions so they can begin doing useful work as soon as possible. The pool will then send a block template full of transactions right afterward, and the miners will usually have it in under a second.</p><p>Miners sometimes get lucky and find the empty block in the interim period before having the full template however this is rarely the reason for an empty block as it's such a small amount of time.</p><p>The usual cause is that some mining hardware will continue to work on old work for up to 60 seconds despite having newer work.</p>
</ng-template>
<ng-template type="why-block-timestamps-dont-always-increase">