Topic: BitPay suports BIP101 (which is run by bitcoinXT) (Read 2128 times)

This is not the version available for download from official XT site.

Official XT version has a backdoor that allows NSA/CIA and other parties to start ddos attack that blocks Tor and de-anonymizes users.

IF the node is under a dos attack.

Move on.

The tweet mentioned in the OP links to a blog post

A few snippets:

From the looks of it they are supporting the hard fork that will happen once 75% of the miners (based on blocks found) accept BIP 101. I don't think it is entirely accurate to say that BitPay is not supporting XT.

I think it would be more accurate to say that BitPay is supporting Bitcoin Core to have the same rules that XT will have regarding larger blocks.

Please stop misinforming community. What are you doing is blatant manipulation in order to promote Bitcoin XT.

BitPay supports BIP101 (large blocks), but not XT!

--snip--

In our opinion, BIP 101 should be pulled into Bitcoin Core.

Currently, the block size limit is hard-coded to 1mb, which constrains overall transaction throughput. BIP101 proposes to increase that limit to 8mb after January of 2016 when a supermajority (>75%) of the blocks being mined indicate they support the increase. The limit on block size will double every two years after that until it reaches 8gb in 2036.

--snip--

In summary, we believe BIP 101 will safeguard Bitcoin’s decentralized nature while providing a reliable, immediate path toward greater network throughput, and we would like to express our support for merging BIP 101 into Bitcoin Core.

Can you comment on this ?
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010379.html

That works in a way that stops your own node from discriminating against Tor traffic, it doesn't prevent anyone using the feature from discriminating against you ....

There isn't
It's a feature against dos attack, and if you don't like it? Bam! Just add -disableipprio before running the node/client. OMG!!!

Can you comment on this ?
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010379.html

You seem to think I hate Tor. I am actually the maintainer of a full blown Tor implementation (Orchid). I've done a lot of work on integrating it into bitcoinj and I'm basically the only guy who can actually move the needle on Tor/Bitcoin usage, by enabling the use of it by default in consumer wallets that have hundreds of thousands of installs. We're not there yet (it's still too slow) but we're a lot closer than before.

This doesn't change the fact that Tor is heavily abused. It can be useful but it's a frequent source of attacks of all kinds. So finding ways to get the good without the bad involves some tricky coding.

Below, you say "anyone can jam the network with just two IP addresses". Yes, that's unfortunate isn't it. I've been sounding the alarm about Bitcoin Core's poor DoS protection for years. Nobody listened, that's why I have now written a new anti-DoS system that can handle this sort of thing. It starts by clustering and deprioritising Tor because we've seen actual jamming attacks that came through Tor, and because using it is a lot safer and more convenient for an attacker than using your own IP addresses or using a botnet. But it absolutely should be extended to have more advanced heuristics. Instead of whinging that (gasp) loading a file from a web server is "insane", maybe you should be writing code instead.

It is inevitable. All major players will support XT because it scales their operations. I'm pretty sure Mike and Gavin have been approached by them to release the code in the wild so they can use it. The free market will prevail.

Can you comment on this ?
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010379.html

No it does not, Show me the code that does what you say. So we can explain it to you.

@meono, you can comment it from your original forum account


The most of the users are not aware about -disableipprio switch and this is not excuse.
XT client has Anti-DDOS tor blocking feature enabled by default which means that user's privacy can be compromised.

@meono, you can comment it from your original forum account

There isn't
It is simply not true, this place if full of trolls and ignorants that simply doesn't know and doesn't want to understand anything about the topic.

It's a feature against dos attack, and if you don't like it? Bam! Just add -disableipprio before running the node/client. OMG!!!
Move on.

Fine. Here some clarifications. Is that better?

There isn't
It is simply not true, this place if full of trolls and ignorants that simply doesn't know and doesn't want to understand anything about the topic.

It's a feature against dos attack, and if you don't like it? Bam! Just add -disableipprio before running the node/client. OMG!!!

Move on.