CoinWallet.eu Stress Test Cancelled + Bitcoin Giveaway

[chaoman]

waiting for the next post xD

[RustyNomad]

waiting for the next post xD

  I think you can forget that, i reckon 90% of the people on this forum is refreshing this page every second and will not be surprised if some have already written scripts to grab the keys from here to automatically sweep those private keys when they get posted.

I wonder what the load on the nodes are with everybody doing this, maybe it has switched to a 'node load test' 

[chaoman]

lmfao I just looked at the private keys of the first post and every single corresponding addresse has 0 btc in it. No btc ever sent to the address.

[Yofun]

lmfao I just looked at the private keys of the first post and every single corresponding addresse has 0 btc in it. No btc ever sent to the address.

....Wrong. Some are empty, Some have random amounts in them.

[chaoman]

post one that had an amount inside it.

[7788bitcoin]

lmfao I just looked at the private keys of the first post and every single corresponding addresse has 0 btc in it. No btc ever sent to the address.

Did you check the compressed or uncompressed public addresses? 

[Lauda]

What a clever brilliant move.  I really didn't see this coming.  Curious if it's gonna be enough to properly stress test Bitcoin.

Actually after testing it myself last night I do not agree. Basically not everyone is going to have the hardware to do this. Also an address with a huge amount of inputs (over 53k transactions) can't be easily cleaned. It is not like once could send the whole balance at once (you will get some errors). This actually isn't as easy as it seems.

post one that had an amount inside it.

I imported one with 0.53BTC and my wallet.dat is around 80MB big.

[chaoman]

post the public address of the key or it didnt happen.

[jacktheking]

If this is true, kindly announce the time CoinWallet will post the thousand private keys. So I can plan my schedule to get some Bitcoin.

[Lauda]

post the public address of the key or it didnt happen.

I don't usually care about random people that do not believe me, but here you are:



There is at least 1 more person that has imported this address and is trying to take the coins. I've figured out a way that works, but without a bot or something this will be painful.

Everything can't be sent out because the TX would be 7949454 bytes big (this results in a error in Core for me).

[chaoman]

hmmm why cant you import your private key into another wallet then send it from there?

[Lauda]

hmmm why cant you import your private key into another wallet then send it from there?

I think that you do not understand how this works. Once a private key is announced publicly (like in this case), anyone can import it. Once two users import the same private key and start sending transactions, this is what happens. They can both send Bitcoins from the address simultaneously. From what I can see whoever else imported the same address, they're using a bot or script to extract the money.

Without a bot or script I can't extract myself anything because it usually ends up as conflicted.
Update: I have never used bitcoind, nor can I write a script myself.

[sAt0sHiFanClub]

post the public address of the key or it didnt happen.

I don't usually care about random people that do not believe me, but here you are:



There is at least 1 more person that has imported this address and is trying to take the coins. I've figured out a way that works, but without a bot or something this will be painful.

Everything can't be sent out because the TX would be 7949454 bytes big (this results in a error in Core for me).

Dont use bitcoinqt. Use bitcoind, write a script ( i used php) that cycles through the outputs (via rpc) to create inputs for rawtransaction and sendtransaction them to the rpc port. You can chain a load of them that way in rapid succession.

you are still bottlenecked by waiting for the keys....

[coinpr0n]

Well this is an interesting turn of events. My feeling is it was planned like this all along though. Expecting fees to go crazy.

[monsanto]

Here are 5 private keys, each containing 0.53918 BTC. Thousands more will be posted tomorrow.

L1JgvFFgUi1MLCaq5ToXR16es8KrbpakV8mWZRvfebHiaeabNuJB
L3Yyqu7PXsn74AYUWp3iom4GHVR3MxeNEigMcYVvf3jPoP8Vf1YY
L2VwYXcWkXuk93PPwWQZgxahtAcPsun5ao8yHNnwZz96EVBaydos
L1uxiDhGgDDLqcmof1D3sbGqe9aZTNnkAPtHnPGbFKE5kgSiJi73
KxSzV3yCyaQEufJ8PQkkk8FvF4tKcwh1mpbumTjCJt3UPoc9QjAT

Our stress testing days are officially over. We thank the community for its patience. These tests have spurred much needed discussion on the block size debate.

Until I receive some BTC at the address below I just don't believe it 

12qRSbk8gFJd8dXVtNcTk63SVbvKL5wuSJ

[Lauda]

Until I receive some BTC at the address below I just don't believe it  

12qRSbk8gFJd8dXVtNcTk63SVbvKL5wuSJ

Please read my post. This is all valid, the only problem is that it is hard to actually use it. The address that had around 0.53 BTC had over 50k inputs. Importing that takes a while and sending BTC is also problematic.
Unless you're the only one using the private key at the time and you have a bot/script then it is almost impossible. I've tried sending 0.002 using coin control by manually selecting 200 inputs. This worked until the other person who was using a bot or script caused a 'conflicted' status on the transaction and thus it was invalidated.

Some private keys have more than others, and I suspect that some addresses have already been emptied. Without proper assistance most users will not be able to acquire the coins. The optimal fee is rising drastically because of this; currently: 0.0014930 9BTC per KB.

[dave111223]

Is there an ETA of when the keys will be released?

[hoian0809]

Is there an ETA of when the keys will be released?

When he online, he will release. OP said: "Thousands more will be posted tomorrow".

[monsanto]

Until I receive some BTC at the address below I just don't believe it  

12qRSbk8gFJd8dXVtNcTk63SVbvKL5wuSJ

Please read my post. This is all valid, the only problem is that it is hard to actually use it. The address that had around 0.53 BTC had over 50k inputs. Importing that takes a while and sending BTC is also problematic.
Unless you're the only one using the private key at the time and you have a bot/script then it is almost impossible. I've tried sending 0.002 using coin control by manually selecting 200 inputs. This worked until the other person who was using a bot or script caused a 'conflicted' status on the transaction and thus it was invalidated.

Some private keys have more than others, and I suspect that some addresses have already been emptied. Without proper assistance most users will not be able to acquire the coins. The optimal fee is rising drastically because of this; currently: 0.0014930 9BTC per KB.

Interesting, so it's a crowd sourced stress test 

[Gianluca95]

It's incredibile what was happened some minutes ago ! I've tried to export some bitcoin to one of my address (in the interested address there was something like 0.43 BTC) but I wasn't able to do this because there were many error about my send. (Error getting outputs, etc.)