Bitcoin Forum
July 19, 2019, 02:45:18 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [2014-06-15] Gavin Andresen about the 51% problem  (Read 692 times)
LiteCoinGuy
Legendary
*
Offline Offline

Activity: 1148
Merit: 1001


In Satoshi I Trust


View Profile WWW
June 15, 2014, 10:16:23 AM
 #1

Gavin Andresen about the 51% problem

https://bitcoinfoundation.org/2014/06/13/centralized-mining/

1563504318
Hero Member
*
Offline Offline

Posts: 1563504318

View Profile Personal Message (Offline)

Ignore
1563504318
Reply with quote  #2

1563504318
Report to moderator
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1563504318
Hero Member
*
Offline Offline

Posts: 1563504318

View Profile Personal Message (Offline)

Ignore
1563504318
Reply with quote  #2

1563504318
Report to moderator
zby
Legendary
*
Offline Offline

Activity: 1592
Merit: 1001


View Profile
June 15, 2014, 11:15:13 AM
 #2


The hashing power of GigaHash comes from users that work for them - how easy would it be to direct the users to hash a double-spending transaction? Has GigaHas full power over what the user machines hash?
CoinMode
Sr. Member
****
Offline Offline

Activity: 417
Merit: 250


View Profile
June 15, 2014, 02:03:48 PM
 #3



The only solution would be to penalize pools who produce too much hashrate. There should be a limit, like 5% or total network rate or more gets penalized harshly. It needs to be kept very low, but not so low that some of the bigger individual users are shut out of the network. Some individuals are currently producing a few petahashes on their own, and they should be allowed to do so. But nobody or thing should ever be allowed to come anywhere close to even 10% of network hashrate. This is destroying GHash.io's reputation quickly.
Kosta#
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 15, 2014, 08:59:07 PM
 #4

The only solution would be to penalize pools who produce too much hashrate. There should be a limit, like 5% or total network rate or more gets penalized harshly. It needs to be kept very low, but not so low that some of the bigger individual users are shut out of the network. Some individuals are currently producing a few petahashes on their own, and they should be allowed to do so. But nobody or thing should ever be allowed to come anywhere close to even 10% of network hashrate. This is destroying GHash.io's reputation quickly.

there is nothing in the bitcoin protocol that would allow to determine that two coinbase transactions came from the same pool. assuming we know what the identity of the "pool" is in the first place.
kjlimo
Legendary
*
Offline Offline

Activity: 1876
Merit: 1002


View Profile WWW
June 16, 2014, 12:50:19 AM
 #5

I realize 5 years isn't very long in this world, but even the three years of legit experience has pushed me towards believing if it could have been done... it would have been done by now...

Coinbase for selling BTCs or Vircurex for trading alt cryptocurrencies like DOGEs
CoinNinja for exploring the blockchain.
PM me with any questions on these sites!  Happy to help!
Grinder
Legendary
*
Offline Offline

Activity: 1284
Merit: 1000


View Profile
June 16, 2014, 08:28:24 AM
 #6

Anything that can happen will happen. The biggest problem I see is that you don't have to buy mining equipment with more than the current mining power to do a 51% attack. All you need to do is start a few pools that pays slightly better than the current pools, and wait until their total mining power is more than 51%. It's also sad that Gavin seems to think that the safety of the Bitcoin network ultimately depends on the ability of the established banking network to verify their customers.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!