Bitcoin Forum
November 05, 2024, 06:28:22 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Idea: Announcing best PoW reached prior to mined block  (Read 469 times)
Hawkix (OP)
Hero Member
*****
Offline Offline

Activity: 531
Merit: 505



View Profile WWW
April 05, 2014, 05:01:27 PM
 #1

What if miners announced on the network the best PoW reached prior to finding the mined block?

This could kind of close the gap between "0 confirmation" and "1 confirmation". Anyone can check if his transaction is being worked on, because e.g. 50% of difficulty target reached indicate that some work was already spent on that.

For given TXID, the network would return a block containing that TX together with best target reached, so anyone can verify it.

The only problem with this is how to prevent overloading the network/miners with bogus requests/DoS.

Donations: 1Hawkix7GHym6SM98ii5vSHHShA3FUgpV6
http://btcportal.net/ - All about Bitcoin - coming soon!
DannyHamilton
Legendary
*
Offline Offline

Activity: 3472
Merit: 4801



View Profile
April 06, 2014, 12:27:35 AM
 #2

What if miners announced on the network the best PoW reached prior to finding the mined block?

This could kind of close the gap between "0 confirmation" and "1 confirmation". Anyone can check if his transaction is being worked on, because e.g. 50% of difficulty target reached indicate that some work was already spent on that.

For given TXID, the network would return a block containing that TX together with best target reached, so anyone can verify it.

The only problem with this is how to prevent overloading the network/miners with bogus requests/DoS.

And the fact that some miner somewhere happens to be working on your transaction, and happens to have reached an insufficient difficulty tells you absolutely nothing about whether or not your transaction will be included in the next block.  Furthermore, the attacker could broadcast your transaction with an insufficient difficulty.  This seems like a huge load on the network with zero benefit.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!