Bitcoin Forum
April 25, 2024, 07:49:19 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How developers can protect their services against 51% attack?  (Read 945 times)
rPman (OP)
Legendary
*
Offline Offline

Activity: 1120
Merit: 1069


View Profile WWW
October 02, 2011, 12:45:27 PM
 #1

Today bitparking i0coin and ixcoin exchange market closed due attack.

What others can to do to protect from it?
For example - take longer time to confirm transactions, depending on the amount this transaction or all transactions to service at time? Let this time will be 3 times longer than it takes to get this amount of coins across the network.
120k i0c ~ 40 hours.

What you think about it?

Здecь нe мoжeт нaxoдитьcя вaшa peклaмa Smiley
Protect a future of bitcoin, use p2pool
Donation in BTC: 19fv5yYtfWZ9jQNjx2ncmu1TTrvg5CczZe
1714031359
Hero Member
*
Offline Offline

Posts: 1714031359

View Profile Personal Message (Offline)

Ignore
1714031359
Reply with quote  #2

1714031359
Report to moderator
1714031359
Hero Member
*
Offline Offline

Posts: 1714031359

View Profile Personal Message (Offline)

Ignore
1714031359
Reply with quote  #2

1714031359
Report to moderator
It is a common myth that Bitcoin is ruled by a majority of miners. This is not true. Bitcoin miners "vote" on the ordering of transactions, but that's all they do. They can't vote to change the network rules.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714031359
Hero Member
*
Offline Offline

Posts: 1714031359

View Profile Personal Message (Offline)

Ignore
1714031359
Reply with quote  #2

1714031359
Report to moderator
MaGNeT
Legendary
*
Offline Offline

Activity: 1526
Merit: 1002


Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na


View Profile WWW
October 02, 2011, 01:03:01 PM
 #2

The coin should be fixed, not the exchange.

DoubleC lost 198 BTC, I think it's enough... I still have 18,000 i0coins but I consider them "lost"... No place to sell and no future for i0coins unless someone fixes the code...
d.james
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250

Firstbits: 12pqwk


View Profile
October 02, 2011, 11:49:30 PM
 #3

you can give those i0coins out as a bounty so people will fix that code.
but then again you won't have any coins left once the code is fixed.
also people might not take your bounty because it doesn't worth anything, until the codes are fixed...

You can not roll a BitCoin, but you can rollback some. Cheesy
Roll me back: 1NxMkvbYn8o7kKCWPsnWR4FDvH7L9TJqGG
doublec
Legendary
*
Offline Offline

Activity: 1078
Merit: 1005


View Profile
October 03, 2011, 01:24:18 AM
 #4

The coin should be fixed, not the exchange.
I agree. Without a trusted miner/pool giving a huge amount of hash power all new chains are exploitable in this regard. Would having the coin reject attempts to do a block reorganization  further back than a certain number of confirmations be enough? Exchanges can then have their deposit limits set sometime beyond that limit. What are the downsides to that?
bulanula
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
October 03, 2011, 08:43:34 AM
 #5

PS Yes this means that if the US Government or any other rouge entity wanted to wipe out Bitcoin, all they would have to do is drop a couple of million in hardware and kiss Bitcoin goodbye. It's that simple really.

Or to put it another way drive the price down far enough for the miners to quit then easily attack the weakened network without spending any dime on ATi cards
tytanhamon04
Jr. Member
*
Offline Offline

Activity: 210
Merit: 1

A nexgen decentralized ride hailing


View Profile
January 11, 2019, 09:02:55 PM
 #6

Very old and interesting topic that I think is worth discussing, it's been 8 years but the problem is not solved and a couple of days ago was made 51% attack on the network Ethereum Classic ! If I'm not mistaken.

DRIFE ●●
█ NEXGEN DECENTRALIZED RIDE HAILING PLATFORM █
●●● 
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!