Bitcoin Network is under sybil attack

[exstasie]

Unfortunatelly Classic nodes have to be at cloud services because of ongoing DDoS attacks

That's not really an excuse. There also is not evidence of the scope of this effect. Let us know how it works out after a fork when hardly any Classic users run their own nodes and they depend on a few entities controlling all their nodes on a cloud service. :popcorn:

[btcltccoins]

No need to worry about bitcoins. Even if it iis under attack, it wont be
defeated so easily. Bitcoin miners will come to a solution as always. So as a bitcoin user there is nothing
to worry about at the present.

[ATguy]

Unfortunatelly Classic nodes have to be at cloud services because of ongoing DDoS attacks

That's not really an excuse. There also is not evidence of the scope of this effect. Let us know how it works out after a fork when hardly any Classic users run their own nodes and they depend on a few entities controlling all their nodes on a cloud service. :popcorn:

Well, the cloud VPS have very good DDoS protection, home connections are not very well protected against such DDoS attacks. The DDoS attacks shoved unless you have much more nodes than few thousands, you need the nodes under very good DDoS protection, otherwise almost all Bitcoin nodes can be taken down anytime if serious attacker wants. So having 5000 home nodes is not solution to Bitcoin node decentralization, these home nodes are very likely to be down quickly when DDoS attack hits.

You either need much more home nodes, or rely on few thousand well protected cloud vps nodes. If Bitcoin scales many times in the number of users using Bitcoin, maybe more users will run home nodes, but until then you must protect the few thousand nodes very well.

[Lauda]

It is obvious your love to Bitcoin Classic

My personal view of Bitcoin Classic is irrelevant in this case. The chart does not lie.

Well, the cloud VPS have very good DDoS protection, home connections are not very well protected against such DDoS attacks. The DDoS attacks shoved unless you have much more nodes than few thousands, you need the nodes under very good DDoS protection, otherwise almost all Bitcoin nodes can be taken down anytime if serious attacker wants. So having 5000 home nodes is not solution to Bitcoin node decentralization, these home nodes are very likely to be down quickly when DDoS attack hits.

That's still not a good excuse. If those 'people' cared about decentralization at all, they would not be starting up hundreds of nodes at the same datacenters. They'd spread them out to multiple places. Those 800 nodes at Amazon are as important as a single node at Amazon. They can be shut down easily without the need for any kind of DDoS.

[arruah]

I like Bitcoin Classis.

[RealPhotoshoper]

I think bitcoin network is official under sybil attack atm. We have atm 1137 (13.84%) nodes from a single provider Choopa, LLC

https://bitnodes.21.co/nodes/?q=Choopa,%20LLC

and next we have 917 (11.16%) nodes from Amazon.com, Inc.
This is a very dangerous situation and i dont know how anyone cant react to this.

what is sybill attack?is that really bad attack?and what will effect for bitcoins network?
if this is dangerous situation,how can we kept our bitcoins safe?please tell me,i dont reall understand.

[chek2fire]

bitcoin is very safe and you dont have to afraid about that. Sybil attack the most problem that can do is to recover info for the transactions or to block transactions the node tha take part to this attack. Nothing more.

[exstasie]

bitcoin is very safe and you dont have to afraid about that. Sybil attack the most problem that can do is to recover info for the transactions or to block transactions the node tha take part to this attack. Nothing more.

That's assuming Sybil attackers have no hash power. If they do, they can use Sybils to facilitate double spend attacks. But yeah, the biggest problem with Sybils is the prospect of transaction censorship.

[Lauda]

what is sybill attack?is that really bad attack?and what will effect for bitcoins network?

Well, basically it is an attack in a system such as Bitcoin where a single entity tries to control as many nodes as possible.

The attacker can refuse to relay blocks and transactions from everyone, disconnecting you from the network.
The attacker can relay only blocks that he creates, putting you on a separate network. You're then open to double-spending attacks.
If you rely on transactions with 0 confirmations, the attacker can just filter out certain transactions to execute a double-spending attack.
Low-latency encryption/anonymization of Bitcoin's transmissions (With Tor, JAP, etc.) can be defeated relatively easy with a timing attack if you're connected to several of the attacker's nodes and the attacker is watching your transmissions at your ISP.

It is not that problematic and you can read more about it here and here.

if this is dangerous situation,how can we kept our bitcoins safe?please tell me,i dont reall understand.

As an average user, you don't really need to worry about this right now. Just enjoy using Bitcoin.

[chek2fire]

New info about Classic sybil attack





https://twitter.com/sysmannet/status/712320429239603200

https://twitter.com/sysmannet/status/712320018659155968

As i say and imo is a very danger situation when a big part of bitcoin node system controlled from only one provider like choopa. My question is how can we block this nodes to connect to our nodes? Anyone know what are their ip range?
As you remember we have done this before when chainalysis do a sybil attack before some months and we have block back then their nodes to connect to our nodes.

[Straux]

There should be a max of 1-10 nodes per single entity/IP. It will cause alot of trouble for these attackers, and give us a stronger sense of safety

[Lauda]

As i say and imo is a very danger situation when a big part of bitcoin node system controlled from only one provider like choopa. My question is how can we block this nodes to connect to our nodes? Anyone know what are their ip range?

I don't think that you should block whole IP ranges. You could work with a few individuals and summarize a list of these nodes and block them all if you really wanted to. It shouldn't take you that much time.

There should be a max of 1-10 nodes per single entity/IP. It will cause alot of trouble for these attackers, and give us a stronger sense of safety

I disagree with the 'per single entity' part. If I host 100 nodes all around the world (i.e. no way of shutting all down at once) am I not helping keep the decentralization? There's a huge difference between hosting all of them at 1 place by various entities and hosting them everywhere by a single entity.

[adamstgBit]

you are not under a sybil attack, until the nodes start misbehaving.
the nodes in question are working perfectly relying TX, working within expected parameters.
all this is an economic show of force by the bitcoin classic community. there is nothing hostile about it.

[hdbuck]

you are not under a sybil attack, until the nodes start misbehaving.
the nodes in question are working perfectly relying TX, working within expected parameters.
all this is an economic show of force by the bitcoin classic community. there is nothing hostile about it.

bwahahahah.

fork off adam.

[icecube45]

I think bitcoin network is official under sybil attack atm. We have atm 1137 (13.84%) nodes from a single provider Choopa, LLC

https://bitnodes.21.co/nodes/?q=Choopa,%20LLC

and next we have 917 (11.16%) nodes from Amazon.com, Inc.
This is a very dangerous situation and i dont know how anyone cant react to this.

nothing can be done to combat this, aws and other cloud providers offer massive grants and credits,

just about anyone could conduct this type of attack with the right amount of resources.

in the end you cant stop it merely hope the network componsates.

[Lauda]

you are not under a sybil attack, until the nodes start misbehaving.

It is a Sybil attack. Nobody is going to keep quiet and wait for them to "misbehave".

the nodes in question are working perfectly relying TX, working within expected parameters.

Perfectly draining the bandwidth of real ('legit') node owners. Might be time to summarize a list and block them

all this is an economic show of force by the bitcoin classic community. there is nothing hostile about it.

You shouldn't have gone to that other forum. It might be too late for you already.

nothing can be done to combat this, aws and other cloud providers offer massive grants and credits,

You can block them.

[Lauda]

https://bitnodes.21.co/nodes/ are attacking my altcoin network also
daily , I have been working a lot on this and they are making nodes/peers with "f yeah bitcoin classic" and all sorts of weird names

What are you talking about? This does not even make sense. Who is attacking your "network" and why? I'm not even sure how this is relevant to the OP.

[Labumi]

In my opinion, this is indeed a very dangerous situation, but I think this would not be possible until a fairly high level, because of the security system in the network of bitcoin is very safe and it may be just a network interruption or an excess of something. So the possibility of this situation will last for some time

[Lauda]

In my opinion, this is indeed a very dangerous situation, but I think this would not be possible until a fairly high level, because of the security system in the network of bitcoin is very safe and it may be just a network interruption or an excess of something. So the possibility of this situation will last for some time

This post makes does not make any sense. I highly suggest improving your language skills before posting in such threads.

[ACP]

In my opinion, this is indeed a very dangerous situation, but I think this would not be possible until a fairly high level, because of the security system in the network of bitcoin is very safe and it may be just a network interruption or an excess of something. So the possibility of this situation will last for some time

This post makes does not make any sense. I highly suggest improving your language skills before posting in such threads.

It's related to this topic. If you see this kind of attack hit the bitcoin network to the strength of hitting all it's seeders and major pools. You will just see the bitcoin wallet look like it's out of sync when in fact it's not.
The only way to stop it is to manually drop the ip's within iptables . This isn't about debating, discussion.