CoinWallet.eu Stress Test Cancelled + Bitcoin Giveaway

[johoe]

28 BTC from inputs or outputs? I mean, 28 BTC including fees?

28 BTC is what was sent to the published addresses and what was subsequently sweeped from them.  So it includes the fees that the sweeping transactions payed.  It doesn't include the fee that coinwallet.eu payed to produce the dust output.  This fee could be another 20-40 BTC; I'm too lazy to write a program to count it.   What people trying to collect the dust received was probably in the range of 5-7 BTC, but that is a wild guess.  I guess amaclin is the only one who made more than a bitcoin.  Okay, there is also the 3J9AGq2aHeqjW13jj1LkaK5kCgZ8EyAjXZ address.  When I have time I write a script that counts the fees and sweeped amount for every major reused address.

[1713914755]

1713914755

[1713914755]

1713914755

[1713914755]

1713914755

[1713914755]

1713914755

[wladston]

I got less than half a bitcoin, but I spent a lot of time writing scripts and babysitting bitcoin nodes, and adjusting size/fee ratios. It was fun however.

[basil00]

I guess the reason is that large transactions are more likely to conflict with something in the mempool and are therefore much harder to push to the miners, correct?

Yes.  Smaller txs have more overhead, but this is still more efficient than most of the sweeper spam that creates utxos and uses big sigs.  Ideally the miners would OP_RETURN it themselves in big txs but it seems they were too lazy.

Does this mean that the keys for the remaining 172 BTC will be published later?

My guess is that coinwallet overestimated the impact of the "giveaway", so gave up.  The problem is, of course, that one can only construct low-fee txs with dust inputs, which has no real impact on the network (apart from artificially inflating the average blocksize).  Normal-fee traffic was unaffected.

I guess coinwallet will consolidate the remaining dust outputs themselves at some point since there is no real point in giving it away.  But if they publish more keys then our bots are ready...

[wroniewicz]

how i use this keys?

[7788bitcoin]

how i use this keys?

Just import them into your blockchain wallet or bitcoin core. BTW, they are all empty now.

[rav3n_pl]

Yes, importing to Core is a good idea!
Just be patient... ALOT!

[wroniewicz]

this is not over yet

[wroniewicz]

so wen nev keys will be posted

[CohibAA]

so wen nev keys will be posted

Maybe you're not looking in the right place.

[wroniewicz]

wat you mean

[amaclin]

But if they publish more keys then our bots are ready...

I have one more suggestion for your bot.
You should not just replace output to OP_RETURN and re-sign the inputs.
The bot should combine inputs to a set of 10-20-30 (up to you) items per one tx.
Have a look to the following code: it parses the incoming transactions and pushes txs with 11 (why not?) inputs and one output

Code:

{
  static UxToList list; // note: this is static variable!
  const QByteArray str ( QString ( "%1:%2" ).arg ( in.getHash ( ).toString ( ) ).arg ( in.getHashIndex ( ) ).toLatin1 ( ) );
  const UxTo uxto ( str.constData ( ), 1000, MyKey20::calc ( pub ).toString ( ).toLatin1 ( ).constData ( ) );
  if ( !list.contains ( uxto ) )
    list.append ( uxto );
  if ( list.size ( ) == 11 )
  {
    const QByteArray tx ( Transaction::rawTransaction ( list, ( ( 136 * list.size ( ) ) + 54 ) * 55 / 10 + 1 ) ); // 5.5 satoshi per byte
    const QByteArray packet ( NetSocket::packet ( TYPE_TX, data ) );
    emit pushTx ( packet );
    list.clear ( );
  }
}   

[bytezero]

how i use this keys?

Just import them into your blockchain wallet or bitcoin core. BTW, they are all empty now.

blockchain can't handle so many inputs at the same time.

[wroniewicz]

so wer is the rest of keys that was not posted yet

[bytezero]

so wer is the rest of keys that was not posted yet

Who has told there will be more keys? Because the op hasn't come back since 11th september 2015.

[striders4]

Only bitcoin core can handle loading the private keys, trying to get coins out needs to use coin control.

Even with that, the size of transactions is unbearable so for most addresses it's not worth it to get big chunks of coins out because it would require a huge fee due to the size of the transaction.

[basil00]

It seems Coinwallet have cancelled the 'giveaway' and have started consolidating the remaining dust presumably for themselves.  Example tx.  They have not released anymore keys AFAIK.

[snipie]

It seems Coinwallet have cancelled the 'giveaway' and have started consolidating the remaining dust presumably for themselves.  Example tx.  They have not released anymore keys AFAIK.

can me get keys 

Boys stop resurrecting this topic and let it die in peace...
The user that posted the mines keys didn't connect since the 11 September, he did his job and i suppose the waves stopped from weeks ago.

[basil00]

The user that posted the mines keys didn't connect since the 11 September, he did his job and i suppose the waves stopped from weeks ago.

As I said in my post (which was overlooked?): coinwallet are not releasing more keys and are consolidating the remaining spam for themselves.  The current >1GB mempool backlog is directly related to this.

[amaclin]

It seems Coinwallet have cancelled the 'giveaway' and have started consolidating the remaining dust presumably for themselves.  Example tx.  They have not released anymore keys AFAIK.

I confirm.
There are a lot of low-fee transactions past hours in the network.
I can not analyze everything, but seend to me that these are withdrawing dust outputs to
https://blockchain.info/address/135zDqhbNcmPk3gbyeJmH75yiLdVZechsK


img source: http://statoshi.info/dashboard/db/transactions

[crackfoo]

I'll try a syllogism:

1. 1aajpztNecNzGBDjJhGfkrsUJFgeyhBgY and 1aa5cmqmvQq8YQTEqcTmW7dfBNuFwgdCD and other addresses starting with "1aa" are collecting efficiently the dust with amaclin methods (same 'k' and P2PK outputs) . "1aa5cmqmv...." was reported here from amaclin too as an example: https://bitcointalk.org/index.php?topic=1175321.msg12405319#msg12405319. To me they seem amaclin addresses.

2. 1aaf64VJGMuYuRBMmM9y2s2pPADFpuqDE started to collect dust before priv keys were announced on internet. It stopped 1 hour before to release the keys. An example, 8 september: https://www.blocktrail.com/BTC/tx/e198f3608705e1654a3d0d2ce56bdc5b81f0bfc9e1597a268eebcd124881773b

3. "1aa5cmq..." is an input for a transaction to "1aaf64...." here: https://www.blocktrail.com/BTC/tx/b80ca4aa385f2a0a91b7625eab05df6e8e20fd81c53ba4c3fd1a1efc2fe056fd

4. "1aajpz..." is an input TOGETHER a "1aaf64...." input for a transaction here: https://www.blocktrail.com/BTC/tx/ca0447b99a1fd68fc157b9cd45343f4793ec9d47818d0375d51675113110d99a

5. Supposed result: these addresses belongs to amaclin and amaclin is behind coinwallet.eu stress-test/giveaway.


EDIT: point five was just a bad joke. A right 5 could be:

5. "1aaf64..." started to collect dust before priv keys were publicly announced and it is probably an amaclin vanity address.

1aa5cmqmvQq8YQTEqcTmW7dfBNuFwgdCD just seemed to have stolen 2+BTC from me a couple days ago.... how is this possible?