Next level Bitcoin stress test -- June 29-30 13:00 GMT 2015

[hodlmybtc]

1 BTC transaction from OKCoin to Bitfinex with a fee of 0.0001 got through in the block that took ~48 minutes to be found, I made the transfer ~10 minutes before it was found.

[1713586698]

1713586698

[1713586698]

1713586698

[1713586698]

1713586698

[sturle]

Thankfully Eligius pool is working against the DOS attack and that fact is encouraging, that at least some miners are willing to prioritize transactions based on something other then pure fee---in this case, the Eligius miners are standing up for the small guy and regular users who are being disrupted by this "experiment".

I moved my C1 to Eligius, and will keep it there until the DoS attack is over.  Mining to their donation address, because I think their anti DoS measures should be rewarded.

[wizkid057]

I've been keeping an eye on Eligius's memory pool (which doesn't contain the attacker's transactions) as other pools find blocks and for the most part it is cleared each time, which means that most legitimate transactions are being mined regardless of this DoS attack.  Good for bitcoin.

It appears BTC China is filtering the spam, also, as it doesn't appear to be showing up in their recent few blocks.  Good for them.

As for Eligius, I feel the need to point out that Eligius's normal spam filtering is public for the most part, with the exception of the portions added recently that combat this specific attack (which would be silly to release during the attack and let the attackers work around it).  Suffice it to say, as I mentioned before, the attacker's transactions are very easy to spot and thus very easy to filter.  Admittedly, I'm kind of surprised that the attack is so simple to filter out.  Leads to questions about the attacker's actual knowledge about bitcoin, or more specifically the lack thereof...

Thankfully Eligius pool is working against the DOS attack and that fact is encouraging, that at least some miners are willing to prioritize transactions based on something other then pure fee---in this case, the Eligius miners are standing up for the small guy and regular users who are being disrupted by this "experiment".

I moved my C1 to Eligius, and will keep it there until the DoS attack is over.  Mining to their donation address, because I think their anti DoS measures should be rewarded.

Thanks for this.

[ChetnotAtkins]

How about all other miners refuse to include transactions from Eligius' payout address. Since addresses are not people that should really not be an issue, right?

[wizkid057]

How about all other miners refuse to include transactions from Eligius' payout address. Since addresses are not people that should really not be an issue, right?

First, there is no "from" address on a transaction.  This is a pretty big misconception that is spread around.  So no one, including Eligius, refuses to include transactions based on it being "from" an address.

Second, Eligius's payouts are generated payouts in the coinbase transaction, which is mined when a block is mined.  No node even sees this transaction until it appears in an Eligius block (except the miners who are mining for Eligius).

*sigh*  The amount of misinformation in this thread is staggering.

[lorylore]

Few people are having issue about blockchain tx. confirming, how long will this take?

[RealMalatesta]

Still an unanswered question is: Who is behind it. Cui bono.

coinwallet.eu wants to store and trade Bitcoins. Well. They have set up a virtual office. The company Coinwallet does not exist in GB. They promote their services and claim that they don't need to know their customers identity. So it is obviously not a British firm, otherwise, they would implement KYC, AML and CTF-policies.

So who would entrust an entity his coins without knowing anything about them? This sounds like a total scam.

Interesting, thoug, that coinwallet claims to be partnering with Multibit. Maybe they can shed some light on it?

I, as a miner, consider this "stress test" being a ddos-attack. Never mind what "results" they may present. And what they have presented until now isn't really useful.

[micromen]

Wow this is a very cool initiative, I heard it worked very good, even better as planned. 

[lorylore]

Wow this is a very cool initiative, I heard it worked very good, even better as planned. 

It's planned good, but i just wonder when will this finished. It makes delay in tx.

[Panthers52]

I am not even sure that the current transactions being pushed to the network is even part of the so-called stress test:

There are a large number of no/low fee transactions in the current mempool. As of recently, there were only around .2 BTC worth of tx fees in the mempool, but still thousands of unconfirmed transactions (over 10k) and a mempool size of well over 10 MegaBites.

It also appears that the brainwallet for cat has been flooded with no fee transactions; the private key with "cat" is 5JiznUZskJpwodP3SR85vx5JKeopA3QpTK63BuziW8RmGGyJg81 which translates to a public key of 04a45ebc40f95cc06ef93a5f5e9daa22774a5c9a120ac14d87c328b44c1158f81cddd109246a4d8 bff5f93cbba79a17f2dc6e7c73da8d6bd0d98615d1bf353f8be which translates to an address of 162TRPRZvdgLVNksMoMyGJsYBfYtB4Q8tM)

[LFC_Bitcoin]

Few people are having issue about blockchain tx. confirming, how long will this take?

I've got 0.18 & 0.095 BTC incoming transactions lost in the wilderness somewhere. They're both coming to the same address. Blockchain.info explorer shows them in said address but my Bitcoin Core client (wallet) shows nothing, not even pending.
They're both unconfirmed transactions after several hours, both the medium, recommended fee. They're payment for a signature & avatar campaign I participate in.

I understand they're not confirmed transactions but a little worried they're not even in my core wallet as pending.

[lorylore]

Few people are having issue about blockchain tx. confirming, how long will this take?

I've got 0.18 & 0.095 BTC incoming transactions lost in the wilderness somewhere. They're both coming to the same address. Blockchain.info explorer shows them in said address but my Bitcoin Core client (wallet) shows nothing, not even pending.
They're both unconfirmed transactions after several hours, both the medium, recommended fee. They're payment for a signature & avatar campaign I participate in.

I understand they're not confirmed transactions but a little worried they're not even in my core wallet as pending.

I hope this will be finished asap, it's getting people in trouble. Any one have information how long must we wait?

[NiceHashSupport]

I've been keeping an eye on Eligius's memory pool (which doesn't contain the attacker's transactions) as other pools find blocks and for the most part it is cleared each time, which means that most legitimate transactions are being mined regardless of this DoS attack.  Good for bitcoin.

It appears BTC China is filtering the spam, also, as it doesn't appear to be showing up in their recent few blocks.  Good for them.

As for Eligius, I feel the need to point out that Eligius's normal spam filtering is public for the most part, with the exception of the portions added recently that combat this specific attack (which would be silly to release during the attack and let the attackers work around it).  Suffice it to say, as I mentioned before, the attacker's transactions are very easy to spot and thus very easy to filter.  Admittedly, I'm kind of surprised that the attack is so simple to filter out.  Leads to questions about the attacker's actual knowledge about bitcoin, or more specifically the lack thereof...

I wouldn't be so sure abou that. There are plenty of legit transactions still waiting to be confirmed. For example, we have few here: https://www.nicehash.com/?p=miners&payments

If your mempool empties out with each block, then perhaps these legit transactions are never broadcasted to you?

[ticoti]

Is test stress happening right now?

I don't see the network is being really busy

[Quickseller]

I've been keeping an eye on Eligius's memory pool (which doesn't contain the attacker's transactions) as other pools find blocks and for the most part it is cleared each time, which means that most legitimate transactions are being mined regardless of this DoS attack.  Good for bitcoin.

It appears BTC China is filtering the spam, also, as it doesn't appear to be showing up in their recent few blocks.  Good for them.

As for Eligius, I feel the need to point out that Eligius's normal spam filtering is public for the most part, with the exception of the portions added recently that combat this specific attack (which would be silly to release during the attack and let the attackers work around it).  Suffice it to say, as I mentioned before, the attacker's transactions are very easy to spot and thus very easy to filter.  Admittedly, I'm kind of surprised that the attack is so simple to filter out.  Leads to questions about the attacker's actual knowledge about bitcoin, or more specifically the lack thereof...

I wouldn't be so sure abou that. There are plenty of legit transactions still waiting to be confirmed. For example, we have few here: https://www.nicehash.com/?p=miners&payments

If your mempool empties out with each block, then perhaps these legit transactions are never broadcasted to you?

It looks like that eligius just found two blocks (https://blockchain.info/block/00000000000000000638218146b8c0ac807315174c0104f390481853188df124 and https://blockchain.info/block/0000000000000000071359c423077912ed499e7351de61b9462d4178f2b45e94), both of which were under 52 kb and 82b43c7617e9bf1afcfbda94152da4fa9ccd2f477a6b5ed203326789d510847a and 5db4631aea702ee3ac6e0895f019e06d7c24b896e76f8cf1f1ba1e51e66d6acf are still showing as unconfirmed and are on the above link with recent mining payments from NiceHash. They do each have 8+ inputs and a large number of outputs.

[gringo1990]

I started a transaction today around 12pm noon EST and it has yet to have 1 confirm. BTC mining price is .0003.. amount of 1.7774


Is there anything I can do to make it go any faster??

[NiceHashSupport]

I've been keeping an eye on Eligius's memory pool (which doesn't contain the attacker's transactions) as other pools find blocks and for the most part it is cleared each time, which means that most legitimate transactions are being mined regardless of this DoS attack.  Good for bitcoin.

It appears BTC China is filtering the spam, also, as it doesn't appear to be showing up in their recent few blocks.  Good for them.

As for Eligius, I feel the need to point out that Eligius's normal spam filtering is public for the most part, with the exception of the portions added recently that combat this specific attack (which would be silly to release during the attack and let the attackers work around it).  Suffice it to say, as I mentioned before, the attacker's transactions are very easy to spot and thus very easy to filter.  Admittedly, I'm kind of surprised that the attack is so simple to filter out.  Leads to questions about the attacker's actual knowledge about bitcoin, or more specifically the lack thereof...

I wouldn't be so sure abou that. There are plenty of legit transactions still waiting to be confirmed. For example, we have few here: https://www.nicehash.com/?p=miners&payments

If your mempool empties out with each block, then perhaps these legit transactions are never broadcasted to you?

It looks like that eligius just found two blocks (https://blockchain.info/block/00000000000000000638218146b8c0ac807315174c0104f390481853188df124 and https://blockchain.info/block/0000000000000000071359c423077912ed499e7351de61b9462d4178f2b45e94), both of which were under 52 kb and 82b43c7617e9bf1afcfbda94152da4fa9ccd2f477a6b5ed203326789d510847a and 5db4631aea702ee3ac6e0895f019e06d7c24b896e76f8cf1f1ba1e51e66d6acf are still showing as unconfirmed and are on the above link with recent mining payments from NiceHash. They do each have 8+ inputs and a large number of outputs.

Yea, what kind of filters you are using are most likely filtering out most of legit transactions or your pool does not have good connectivity with other nodes. If it is the second, then you should really establish connections with big bitcoin service providers (like BitGo for example).

[Pathi]

Over 8 hours to get todays payment from Westhash.

[kano]

Are you saying that all miners are blacklisting addresses? That's news to me and I'm sure other bitcoiners as well.

Blacklisting is by definition about people, and no miner has ever attempted that to my knowledge.
Addresses are not people, and do not even exist in the Bitcoin protocol. Instead, they are converted into scripts.
Bitcoin Core has filtered what scripts it will relay or mine since Satoshi Nakamoto himself added filtering in 0.3.18 (2010 Dec 8th).
To disable this, you must use (or rewrite) patches that I have maintained almost as long as I have been involved in Bitcoin.
As far as I know, however, not a single miner is currently mining without any script filtering whatsoever.

Eligius is treating certain inputs differently then other inputs. Plain and simple. They are saying that Bitcoin owned by one entity is not allowed to have their transactions confirmed by their found blocks.

This is not the first time that eligius (via Luke-jr) has done something similar to harm Bitcoin. Gambling sites were previously blacklisted by default by mining software when this was pretty clearly not a wanted "feature" of such software. In other words the software did things that its users did not want. This is how a lot of people describe malware.

This is 100% false/FUD/lies.

Luke - it's important to remember when any of your regular lies, can be easily shown to be lies, and thus it's a bad idea to post those lies publicly.
If you can't even remember what you said 5 minutes ago, you need check your facts about yourself before you post about something in the past

When you write code to Blacklist something and even in the code, you call it a Blacklist, it's rather bazaar that you'd then go and say it isn't a Blacklist. Even worse, you added this code on by default in gentoo bitcoin so that anyone who didn't disable your Blacklist, got it.

Current code:
https://github.com/luke-jr/bitcoin/blob/0.10.x-ljrP/src/main.cpp#L943

Note that the name was originally BlacklistedPrefixes:
https://github.com/luke-jr/bitcoin/blob/19cc5c03a0448f8c88cc81538bf3e54594867e5e/src/script.cpp#L1834

Code:

static struct BlacklistEntry BlacklistedPrefixes[] = {
    {0x06f1b600, 0x06f1b6ff, "SatoshiDice"},
    {0x74db3700, 0x74db59ff, "BetCoin Dice"},
    {0xc4c5d791, 0xc4c5d791, "CHBS"},  // 1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T
    {0x434e5452, 0x434e5452, "Counterparty"},
    {0x069532d8, 0x069532da, "SatoshiBones"},
    {0xda5dde84, 0xda5dde94, "Lucky Bit"},
};

Of course you can (yet again) say that dictionaries are wrong and you are right, but even the Oxford dictionary says your definition is wrong:
http://www.oxforddictionaries.com/definition/american_english/blacklist
"Person" or "Product"

( By "Yet again" I am referring to: https://bitcointalk.org/index.php?topic=28402.msg1369274#msg1369274 )

While you are at it, don't forget to tell the real bitcoin devs that their use of the term Blacklist in the code is wrong
https://github.com/bitcoin/bitcoin/blob/master/src/qt/paymentserver.cpp#L163

Code:

// Blacklisted certificate
if (cert.isBlacklisted()) {
   ReportInvalidCertificate(cert);
   continue;
}

So I take it since a "certificate" isn't a "person" then that code is wrong in main bitcoin

You like playing word games to pretend you aren't doing what people say you are doing, due to some technicality (that is also false)
Here's an example of how I'd expect you'd get out of murdering someone:
Luke:
"Your honour, I didn't shoot him to death, which is the charge levelled against me, thus I am not guilty of murder.
You see, what happened was, a bullet from the gun I had in my possessions left the barrel of the gun and pierced his body, but he was still alive.
When I pushed him, staggering, off the cliff, the entire fall to the ground far below, he was still alive, thus the bullet didn't kill him, it was the rocks below that killed him.
Thus I am not guilty of murder."

It's funny to see wizkid play these same games of yours also ...
Palpatine, you are training your padawan well ...

[tspacepilot]

I've been keeping an eye on Eligius's memory pool (which doesn't contain the attacker's transactions) as other pools find blocks and for the most part it is cleared each time, which means that most legitimate transactions are being mined regardless of this DoS attack.  Good for bitcoin.

It appears BTC China is filtering the spam, also, as it doesn't appear to be showing up in their recent few blocks.  Good for them.

As for Eligius, I feel the need to point out that Eligius's normal spam filtering is public for the most part, with the exception of the portions added recently that combat this specific attack (which would be silly to release during the attack and let the attackers work around it).  Suffice it to say, as I mentioned before, the attacker's transactions are very easy to spot and thus very easy to filter.  Admittedly, I'm kind of surprised that the attack is so simple to filter out.  Leads to questions about the attacker's actual knowledge about bitcoin, or more specifically the lack thereof...

I wouldn't be so sure abou that. There are plenty of legit transactions still waiting to be confirmed. For example, we have few here: https://www.nicehash.com/?p=miners&payments

If your mempool empties out with each block, then perhaps these legit transactions are never broadcasted to you?

It looks like that eligius just found two blocks (https://blockchain.info/block/00000000000000000638218146b8c0ac807315174c0104f390481853188df124 and https://blockchain.info/block/0000000000000000071359c423077912ed499e7351de61b9462d4178f2b45e94), both of which were under 52 kb and 82b43c7617e9bf1afcfbda94152da4fa9ccd2f477a6b5ed203326789d510847a and 5db4631aea702ee3ac6e0895f019e06d7c24b896e76f8cf1f1ba1e51e66d6acf are still showing as unconfirmed and are on the above link with recent mining payments from NiceHash. They do each have 8+ inputs and a large number of outputs.

So hard to figure out what people mean by that damn eye-rolly smiley face.  You do understand that mining is a stochastic procedure right?   Finding a block isn't going to be predetermined in size or number of inputs.  I'll try it too: