Bitcoin Forum
May 13, 2024, 10:49:55 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: A Simple Solution to prevent 51%, DoS, and Double Spend attacks  (Read 899 times)
boliu (OP)
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250

6th BTC reached. Thank you for your support


View Profile
September 11, 2015, 01:27:12 PM
 #1

Would a simple implementation of preventing any miner or pool to submit consecutive blocks solve these attacks?
                     

"Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715597395
Hero Member
*
Offline Offline

Posts: 1715597395

View Profile Personal Message (Offline)

Ignore
1715597395
Reply with quote  #2

1715597395
Report to moderator
1715597395
Hero Member
*
Offline Offline

Posts: 1715597395

View Profile Personal Message (Offline)

Ignore
1715597395
Reply with quote  #2

1715597395
Report to moderator
1715597395
Hero Member
*
Offline Offline

Posts: 1715597395

View Profile Personal Message (Offline)

Ignore
1715597395
Reply with quote  #2

1715597395
Report to moderator
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
September 11, 2015, 02:22:52 PM
 #2

How would you determine that two submissions come from the same entity?  Assume they can: change the coinbase text (as they do), change the payout address (as they sometimes do), change their IP address (insofar that even matters), etc.

Additionally, your suggestion would not help against collusion (i.e. two miners working together).

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!