johoe
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 18, 2015, 06:13:39 PM Last edit: September 18, 2015, 06:31:00 PM by 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.
|
Donations to 1CF62UFWXiKqFUmgQMUby9DpEW5LXjypU3
|
|
|
wladston
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 157
Merit: 102
Always remember to be awesome.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 18, 2015, 07:15:41 PM |
|
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
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 60
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 19, 2015, 02:57:45 AM |
|
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
Newbie
Offline
Activity: 56
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 19, 2015, 02:17:37 PM |
|
how i use this keys? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
7788bitcoin
Legendary
Offline
Activity: 2282
Merit: 1023
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 22, 2015, 07:02:33 AM |
|
how i use this keys? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Just import them into your blockchain wallet or bitcoin core. BTW, they are all empty now.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 22, 2015, 04:26:21 PM |
|
Yes, importing to Core is a good idea! Just be patient... ALOT! ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
|
wroniewicz
Newbie
Offline
Activity: 56
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 22, 2015, 07:19:52 PM |
|
this is not over yet ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
wroniewicz
Newbie
Offline
Activity: 56
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 04:31:58 PM |
|
so wen nev keys will be posted ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
CohibAA
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 04:33:06 PM |
|
so wen nev keys will be posted ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Maybe you're not looking in the right place.
|
|
|
|
wroniewicz
Newbie
Offline
Activity: 56
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 05:03:14 PM |
|
wat you mean ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
amaclin
Legendary
Offline
Activity: 1260
Merit: 1019
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 05:03:26 PM |
|
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 { 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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 05:06:52 PM |
|
how i use this keys? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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
Newbie
Offline
Activity: 56
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2015, 05:36:46 PM |
|
so wer is the rest of keys that was not posted yet ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
bytezero
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 25, 2015, 04:18:40 AM |
|
so wer is the rest of keys that was not posted yet ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Who has told there will be more keys? Because the op hasn't come back since 11th september 2015.
|
|
|
|
striders4
Newbie
Offline
Activity: 28
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 26, 2015, 07:50:05 AM |
|
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
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 60
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 07, 2015, 10:28:04 AM |
|
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
Legendary
Offline
Activity: 3262
Merit: 1141
Up to 300% + 200 FS deposit bonuses
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 07, 2015, 07:38:45 PM |
|
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. 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
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 60
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 08, 2015, 12:39:24 AM |
|
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.
|
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3514
Merit: 1126
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 18, 2015, 01:09:51 AM |
|
1aa5cmqmvQq8YQTEqcTmW7dfBNuFwgdCD just seemed to have stolen 2+BTC from me a couple days ago.... how is this possible?
|
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
|