Bitcoin Forum
March 19, 2024, 04:21:17 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Overloading Bitcoin on purpose, possible flaw?  (Read 1399 times)
Elwar (OP)
Legendary
*
Offline Offline

Activity: 3598
Merit: 2384


Viva Ut Vivas


View Profile WWW
March 10, 2012, 01:44:39 PM
 #1

I am by far no expert on the inner workings of Bitcoin but I have wondered about ways in which an outside entity (The Federal Reserve) may try to take down Bitcoin.

I do know that all transactions are stored in the chain. And also that you can get as many addresses as you want. I see these as potential weaknesses against an attack.

For the first one, I may be off but when you download the Bitcoin app you are also downloading all transactions that have taken place right? (I may be way off there). But if someone wanted to attack, they would just create millions of dummy transactions back and forth between two addresses so that the size of the download would get so huge that nobody would be able to load up the client because of the hard drive space needed. Again, I may be way off on how that works but it seems that hard drive space could potentially be an issue if someone went about it right.

As for the BTC addresses, yes I know that there are billions (trillions?) of addresses, but could someone not set up thousands of bots to just keep creating addresses at a speed where they own all BTC addresses after a few years? What is preventing this from happening?

Those are my major concerns. I know that there are major forces out there that do not want Bitcoin or anything like it to succeed, and we are probably off the radar for now as a "currency for trading drugs" but if/when Bitcoin becomes a competitor, we will be attacked.

First seastead company actually selling sea homes: Ocean Builders https://ocean.builders  Of course we accept bitcoin.
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Gabi
Legendary
*
Offline Offline

Activity: 1148
Merit: 1008


If you want to walk on water, get out of the boat


View Profile
March 10, 2012, 01:48:43 PM
 #2

Quote
But if someone wanted to attack, they would just create millions of dummy transactions back and forth between two addresses so that the size of the download would get so huge that nobody would be able to load up the client because of the hard drive space needed. Again, I may be way off on how that works but it seems that hard drive space could potentially be an issue if someone went about it right.
You forget transaction fees. If they want to do they will be forced to spend thousands of BTC on fees. Let's hope they do that, we will become rich

Quote
As for the BTC addresses, yes I know that there are billions (trillions?) of addresses, but could someone not set up thousands of bots to just keep creating addresses at a speed where they own all BTC addresses after a few years? What is preventing this from happening?
The fact that you seems to ignore how MANY possible addresses there are.

Thousands of bots? Useless.

Maybe if every planet on every galaxy in the whole universe is covered of bots, then maybe in more than the whole age of the universe they can find how many, 1% of all total addresses?
Mhh.... add some universes.

bitcoinsarefun
Member
**
Offline Offline

Activity: 98
Merit: 10



View Profile
March 10, 2012, 01:50:03 PM
 #3

I am by far no expert on the inner workings of Bitcoin but I have wondered about ways in which an outside entity (The Federal Reserve) may try to take down Bitcoin.

I do know that all transactions are stored in the chain. And also that you can get as many addresses as you want. I see these as potential weaknesses against an attack.

For the first one, I may be off but when you download the Bitcoin app you are also downloading all transactions that have taken place right? (I may be way off there). But if someone wanted to attack, they would just create millions of dummy transactions back and forth between two addresses so that the size of the download would get so huge that nobody would be able to load up the client because of the hard drive space needed. Again, I may be way off on how that works but it seems that hard drive space could potentially be an issue if someone went about it right.

As for the BTC addresses, yes I know that there are billions (trillions?) of addresses, but could someone not set up thousands of bots to just keep creating addresses at a speed where they own all BTC addresses after a few years? What is preventing this from happening?

Those are my major concerns. I know that there are major forces out there that do not want Bitcoin or anything like it to succeed, and we are probably off the radar for now as a "currency for trading drugs" but if/when Bitcoin becomes a competitor, we will be attacked.

How do dummy ( ie invalid ) transactions get into the chain? If they are invalid shouldn't they be discarded and never reach the chain?
Remember remember the 5th of November
Legendary
*
Offline Offline

Activity: 1862
Merit: 1011

Reverse engineer from time to time


View Profile
March 10, 2012, 01:50:11 PM
 #4

There are actually ~2 quindicillion possible addresses, it's a number much much higher than trillions.

And it is possible to flood the network with fee-less transactions, but who knows if they will get confirmed, ever.
Not to mention, that it requires bitcoins in the first place.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
JoelKatz
Legendary
*
Offline Offline

Activity: 1596
Merit: 1012


Democracy is vulnerable to a 51% attack.


View Profile WWW
March 10, 2012, 01:57:46 PM
 #5

For the first one, I may be off but when you download the Bitcoin app you are also downloading all transactions that have taken place right? (I may be way off there). But if someone wanted to attack, they would just create millions of dummy transactions back and forth between two addresses so that the size of the download would get so huge that nobody would be able to load up the client because of the hard drive space needed. Again, I may be way off on how that works but it seems that hard drive space could potentially be an issue if someone went about it right.
How would these transactions get in the block chain exactly?

Quote
As for the BTC addresses, yes I know that there are billions (trillions?) of addresses, but could someone not set up thousands of bots to just keep creating addresses at a speed where they own all BTC addresses after a few years? What is preventing this from happening?
Creating a bitcoin address has no effect on anyone else whatsoever. Creating an address is purely something you do locally. So if they did this, nobody would ever even know.

Now, in order to take your Bitcoins, they'd have to find a private key whose corresponding public key has the same 160-bit hash as your key. The size of the hash was specifically chosen to be way too large to make this possible. The consensus right now is that a 104-bit hash would be safe from such an attack, even against an attack funded by all the resources the human race could muster, until around 2050. A 160-bit hash is 72,000,000,000,000,000 times harder.

I am an employee of Ripple. Follow me on Twitter @JoelKatz
1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
Elwar (OP)
Legendary
*
Offline Offline

Activity: 3598
Merit: 2384


Viva Ut Vivas


View Profile WWW
March 10, 2012, 01:58:15 PM
 #6

I see...so they could flood the network with fee-less transactions back and forth between their own addresses but it would take so long because of lack of fees that it would not be possible to flood it to the point of harm.

That is good to know, I am sure that as regular transactions take up hard drive space over time the hard drives will grow at a fast enough rate where it will not have much affect.

First seastead company actually selling sea homes: Ocean Builders https://ocean.builders  Of course we accept bitcoin.
kronosvl
Full Member
***
Offline Offline

Activity: 134
Merit: 100


View Profile
March 10, 2012, 01:58:47 PM
 #7


As for the BTC addresses, yes I know that there are billions (trillions?) of addresses, but could someone not set up thousands of bots to just keep creating addresses at a speed where they own all BTC addresses after a few years? What is preventing this from happening?


They would have more success ordering the army to gather all the grains of sand from earth than having all the BTC addresses

Donations are accepted @: 19Uk8zVhdgfrRo5Z6wH9yghWxZUtdiNtX9
OTC: http://bitcoin-otc.com/viewgpg.php?nick=kronosvl
Gavin Andresen
Legendary
*
Offline Offline

Activity: 1652
Merit: 2164


Chief Scientist


View Profile WWW
March 10, 2012, 03:13:37 PM
 #8

There have already been several "transaction spam" attacks; as already pointed out, transaction fees keep them from being a big problem.

The code also limits the number of free transactions that are relayed across the network, so you can't flood the network with transactions that will never get mined.

Smarter denial-of-service attack prevention code has been a major unseen feature of the last couple Bitcoin releases.

How often do you get the chance to work on a potentially world-changing project?
cypherdoc
Legendary
*
Offline Offline

Activity: 1764
Merit: 1002



View Profile
March 10, 2012, 03:32:49 PM
 #9

There have already been several "transaction spam" attacks; as already pointed out, transaction fees keep them from being a big problem.

The code also limits the number of free transactions that are relayed across the network, so you can't flood the network with transactions that will never get mined.

Smarter denial-of-service attack prevention code has been a major unseen feature of the last couple Bitcoin releases.


i distinctly remember the .01 btc attack of last summer that went on for hours/days.  the network handled it well. 

keep up the great work Gavin. 
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!