"I'll try a syllogism"
In my language the "syllogizm" is a "statement of the two preconditions"this was an example of bad logic and spreading rumors, not a syllogizm
Topic: CoinWallet.eu Stress Test Cancelled + Bitcoin Giveaway - page 4. (Read 98906 times)
this was an example of bad logic and spreading rumors, not a syllogizm
@elmad
my cards are always opened in this game.
i share my knowledge with everyone who wants to listen me.
you do not need to "discover secrets". you can just ask me and i will answer.
I know, I thanked you before in this thread for your hints
. It was a sort of joke, indeed I started with: "I'll try a syllogism". And anyway if were you I wasn't thinking bad of your actions. Sorry if it seemed so. For 200BTC, you could generate 444444 such transactions.
I am not interested in spamming bitcoin network. [for free and/or spending my funds]I am not a rich person and bitcoin network is only a tool (or may be a "field"?) for earning funds for me and my family.
And of course I do not have 200 btc.
I do not hold btc as savings at all.
And we (both you and me) know how bitcoin network can resist in case of this attack.
@elmad
my cards are always opened in this game.
i share my knowledge with everyone who wants to listen me.
you do not need to "discover secrets". you can just ask me and i will answer.
I suggested them to use https://bitcointalksearch.org/topic/cheap-way-to-attack-blockchain-1166928 for stress-testing
For 200BTC, you could generate 444444 such transactions.
This is 444444 * 225 = ~100,000,000 sigOps!
Or 100000000 / 20000 = 5000 blocks = 35day backlog.
This is for a fee rate of 0.0006BTC per KB (six times the standard rate).
Or even better, a 7day backlog for a fee rate of 0.003BTC per KB (30 times the standard rate).
This would have been a much more interesting
That he "started early" could easily be explained if these addresses were weak brainwallets
No I've received several privatekeys directly from coinwallet.we were in email contact
and I suggested them to use https://bitcointalksearch.org/topic/cheap-way-to-attack-blockchain-1166928 for stress-testing
So I was right for the most part
That he "started early" could easily be explained if these addresses were weak brainwallets
No I've received several privatekeys directly from coinwallet.we were in email contact
and I suggested them to use https://bitcointalksearch.org/topic/cheap-way-to-attack-blockchain-1166928 for stress-testing
Quote
BTW, are there 791 published private keys now or have I been missing a post?
I've counted the same number.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://bitcointalksearch.org/topic/m.12405319. 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.
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://bitcointalksearch.org/topic/m.12405319. 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.
I agree that most 1aa.. addresses probably belong to amaclin (he has been using vanity addresses like this since December last year). However I doubt that 5. is a correct conclusion unless you can show me a transaction where one of the 1aa addresses is used as input for the original high-fee dust creating spam transactions.
That he "started early" could easily be explained if these addresses were weak brainwallets (coinwallet.eu used brainwallets in their first stress test). Also amaclin has the programs and the knowledge how to sweep these addresses. This is why he got a big part of the "Bitcoin Giveaway". There is nothing wrong with that, of course.
BTW, are there 791 published private keys now or have I been missing a post? I count about 6.5 BTC left in 650k coins (all are probably already triple- or quadruple-spent but still unconfirmed).
Theres no more than 0.00061342btc there. They're all double spends
That is strange... But there is more there. blockchain.info shows 0.00073887 btc on confirmed outputs
(no outputs from coinwallet spam confirmed, as expected)
https://blockchain.info/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
Finally got it working and fully automated!!! Took long enough. Let's see how much BTC I can make
https://blockexplorer.com/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
https://tradeblock.com/bitcoin/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
Slowest part is loading in each private key. I guarantee ill sweep everything within the next day though.
https://blockexplorer.com/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
https://tradeblock.com/bitcoin/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
Slowest part is loading in each private key. I guarantee ill sweep everything within the next day though.
That is quite an amount of inputs
Total Received 2391.33012313 BTC
Total Sent 2387.45339118 BTC
Final Balance 3.87673195 BTC
Lot of recieved amounts for a few Bitcoins.
Don't think its even that. Theres no more than 0.00061342btc there. They're all double spends 
Finally got it working and fully automated!!! Took long enough. Let's see how much BTC I can make
https://blockexplorer.com/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
https://tradeblock.com/bitcoin/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
Slowest part is loading in each private key. I guarantee ill sweep everything within the next day though.
https://blockexplorer.com/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
https://tradeblock.com/bitcoin/address/1AyRmvqe99mRWU69w8Hbaeej8twMpdeiKm
Slowest part is loading in each private key. I guarantee ill sweep everything within the next day though.
That is quite an amount of inputs
Total Received 2391.33012313 BTC
Total Sent 2387.45339118 BTC
Final Balance 3.87673195 BTC
Lot of recieved amounts for a few Bitcoins.
i personally didnt participate in this bullshit 200btc giveaway but ive kept up with the thread a bit. how many of you actually got something from this?
@elmad
I am Oz, the Great and Terrible! But don't strike me - please don't - and I'll do anything you want me to.
I am Oz, the Great and Terrible! But don't strike me - please don't - and I'll do anything you want me to.
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://bitcointalksearch.org/topic/m.12405319. 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.
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://bitcointalksearch.org/topic/m.12405319. 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
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.
Why would you want to use P2PK instead of P2PKH?
Because I have to count the size of withdrawing from it later. The whole cycle is:
p2pk:
p2pkh:
So, p2pk are smaller
Why would you want to use P2PK instead of P2PKH?P2PKH tx's are smaller for comparison this is P2PKH https://live.blockcypher.com/btc/tx/67986a2484d2880fb7f172bfe992fb6dea0142b98794f0b9706938b006b24ad0/ and this is P2PK https://live.blockcypher.com/btc/tx/657b57238c7e442227f30c40e6f7a621eaed66087cace0ff66394c28bcf4162c/ differs huh?
Is it possibile to forge a P2PK transaction instead of a P2PKH transaction, using bitcoind rpc reference client? It seems no to me, just asking to be sure.
I'm impressed by that trick.
The only thing to do is use SIGHASH_NONE | SIGHASH_ANYONECANPAYI've never used it myself.
But this allows miners to concatenate all your transactions into one.
https://en.bitcoin.it/wiki/OP_CHECKSIG
Quote
Procedure for Hashtype SIGHASH_NONE
The output of txCopy is set to a vector of zero size.
All other inputs aside from the current input in txCopy have their nSequence index set to zero
Think of this as "sign none of the outputs-- I don't care where the bitcoins go."
The output of txCopy is set to a vector of zero size.
All other inputs aside from the current input in txCopy have their nSequence index set to zero
Think of this as "sign none of the outputs-- I don't care where the bitcoins go."
Quote
Procedure for Hashtype SIGHASH_ANYONECANPAY
The txCopy input vector is resized to a length of one.
The subScript (lead in by its length as a var-integer encoded!) is set as the first and only member of this vector.
Think of this as "Let other people add inputs to this transaction, I don't care where the rest of the bitcoins come from."
The txCopy input vector is resized to a length of one.
The subScript (lead in by its length as a var-integer encoded!) is set as the first and only member of this vector.
Think of this as "Let other people add inputs to this transaction, I don't care where the rest of the bitcoins come from."
Do not forget that you should append 0x82 (as 32-bit low-endian) on step 13 http://bitcoin.stackexchange.com/questions/3374/how-to-redeem-a-basic-tx instead of 0x01
And 0x82 as byte on step 15
But I am quite sure that no miner today merges transactions
They are too lazy 
Slowest part is loading in each private key.
I guarantee ill sweep everything within the next day though.
You've made my day I guarantee ill sweep everything within the next day though.
My program goes so fucking quick that I know they will all be confirmed eventually even if dropped once or multiple times 
I'm dropping transaction bombs on the blockchain every few minutes
You've made my week! I'm dropping transaction bombs on the blockchain every few minutes
Quote
This is not my address.
Yeah sorry I misread. Collecting dust in those "special" P2SH addresses probably won't do much though. To be effective the fee still needs to outbid the standard transaction traffic.
3J9AGq2aHeqjW13jj1LkaK5kCgZ8EyAjXZ - who knows the inner script?
Give us a clue, how many bytes? But it was very inefficient to fill such address with small outputs.
I doubt that the owner reads this topic.
Jump to: