CoinWallet.eu Stress Test Cancelled + Bitcoin Giveaway - page 6.

elmad

member

Activity: 119

Merit: 10

Quote from: amaclin on September 13, 2015, 08:36:23 AM

Quote

Some of the older encoded txs (XX, XY, XW, R, DS) will likely bounce around for a while. I've set my script to double-spend them.

No need to do it. Because my script converts everything to "my address".
And your script converts my result to OP_RETURN.
Unfortunately to me, I can not beat you

OK, the game is over. From this moment all dust outputs from compromised private keys will go to miners only. Grin

@basil00, You took my profits, the son of a bitch ! Grin

@amaclin what fee were you using when you took profit? How many satoshis for byte?

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

This message was too old and has been purged

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

This message was too old and has been purged

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: yakuza699 on September 13, 2015, 01:22:35 PM

Either f2pool mines non-standard tx's or either https://bitcoin.org/en/developer-guide#non-standard-transactions was wrong.

The correct is: Exception: standard null data outputs may receive any amount, even zero satoshis.
"standardness" - is not consensus protocol rule. Any client may use its own rules.

elmad

member

Activity: 119

Merit: 10

Quote from: amaclin on September 12, 2015, 11:59:16 PM

Quote from: basil00 on September 12, 2015, 11:37:02 PM

I thought this was an interesting experiment, so I tried it:
double-spending the 0-conf coinwallet "sweeper" spam.
Below is a quick write-up:

@elmad, this is an answer how to create the transaction without retrieving utxo from the blockchain Grin

Thanks, later I thought that you meant double spending but I have not researched the procedure. Thanks to you and @basil00 for these posts.

yakuza699

hero member

Activity: 935

Merit: 1002

Quote from: amaclin on September 13, 2015, 12:37:38 PM

Quote from: yakuza699 on September 13, 2015, 12:07:42 PM

I am NOT saying that, that transaction is invalid.I am saying that, that transaction is non-standard.Try to relay the given tx and see yourself.

take it confirmed
https://tradeblock.com/bitcoin/tx/ba1ed5b4b036f9adddc4092273b19381b525698b7cf51a6fbe1112466ba3d085

Either f2pool mines non-standard tx's or either https://bitcoin.org/en/developer-guide#non-standard-transactions was wrong.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: yakuza699 on September 13, 2015, 12:07:42 PM

I am NOT saying that, that transaction is invalid.I am saying that, that transaction is non-standard.Try to relay the given tx and see yourself.

take it confirmed
https://tradeblock.com/bitcoin/tx/ba1ed5b4b036f9adddc4092273b19381b525698b7cf51a6fbe1112466ba3d085

yakuza699

hero member

Activity: 935

Merit: 1002

Quote from: amaclin on September 13, 2015, 11:25:14 AM

Quote from: yakuza699 on September 13, 2015, 10:12:23 AM

Still think I am wrong?

Yes. I think you are wrong.

I am NOT saying that, that transaction is invalid.I am saying that, that transaction is non-standard.Try to relay the given tx and see yourself.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: yakuza699 on September 13, 2015, 10:12:23 AM

Still think I am wrong?

Yes. I think you are wrong.
This is the actual code:

BOOST_FOREACH(const CTxOut& txout, tx.vout) {
   if (!::IsStandard(txout.scriptPubKey, whichType)) {
   reason = "scriptpubkey";
   return false;
   }

   if (whichType == TX_NULL_DATA)
   nDataOut++;
   else if ((whichType == TX_MULTISIG) && (!fIsBareMultisigStd)) {
   reason = "bare-multisig";
   return false;
   } else if (txout.IsDust(::minRelayTxFee)) {
   reason = "dust";
   return false;
   }
   }

   // only one OP_RETURN txout is permitted
   if (nDataOut > 1) {
   reason = "multi-op-return";
   return false;
   }

The reference client either increases the total count of null-data outputs in tx or checks for dust limits.
But not both.
So, it is possible to burn any amount via OP_RETURN, even zero.

Note, that bc.i still treats null-data output as non-standard

yakuza699

hero member

Activity: 935

Merit: 1002

Quote from: amaclin on September 13, 2015, 08:53:54 AM

Quote from: yakuza699 on September 13, 2015, 08:22:49 AM

Sending more than 0BTC to an OP_RETURN output would be non-standard.

No, this is standard output. The amount will be burned

Wrong. https://bitcoin.org/en/developer-guide#non-standard-transactions "As of Bitcoin Core 0.9.3 standard null data outputs must receive zero satoshis".Still think I am wrong?

Code:

010000000133c3d38bb4a30bd4595707e13ca17d948d051365b166f50da26527680f0bddf0000000008a47304402205a277704ca398dfdfee958ab6eb3af098d88b60c34712ff5bceab9401a715c4d02202523894f0924136bde8ae07b8b6cf06cb2e75c175172c31e6800db7d9adca648014104f64e3d965b8f4aa507665a7a765dab9a78192c1dc7d87743696ee7adc714de336b8435c3e21ae72d917fe1e588f54e632a8448611a8a1b20bbe9066c0ec78a75ffffffff0290512d00000000001976a91474824ef4fc87f5e6a9c7800ca5afd67e49dac34188ac0000000000000000066a045445535400000000

Good luck relaying it.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: yakuza699 on September 13, 2015, 08:22:49 AM

Sending more than 0BTC to an OP_RETURN output would be non-standard.

No, this is standard output. The amount will be burned

amaclin

legendary

Activity: 1260

Merit: 1019

Quote

Some of the older encoded txs (XX, XY, XW, R, DS) will likely bounce around for a while. I've set my script to double-spend them.

No need to do it. Because my script converts everything to "my address".
And your script converts my result to OP_RETURN.
Unfortunately to me, I can not beat you

OK, the game is over. From this moment all dust outputs from compromised private keys will go to miners only. Grin

@basil00, You took my profits, the son of a bitch ! Grin

yakuza699

hero member

Activity: 935

Merit: 1002

Quote from: Evil-Knievel on September 13, 2015, 08:21:04 AM

The fees for these small outputs are higher than the values in those outputs.

Yes that's what you need to do if you want your tx to get confirmed.

Quote from: Evil-Knievel on September 13, 2015, 08:21:04 AM

So here is what I think: The OP wanted to perform the stress test but realized that he will not be able to accumulate those dust outputs (which he before created by splitting 250 BTC up in small amounts) without spending another 250 BTC on transaction fees.

I think it's wrong.Maybe OP was just too lazy to do it himself so instead released the priv keys so that other people would do the "stress test" for him.And you know if OP would have gave me the keys I would have got at least 100BTC from it.

Quote from: Evil-Knievel on September 13, 2015, 08:21:04 AM

Now he realized that he essentially burned 250 BTC and the release of those private keys is one last desperate move to reestablish his good reputation (by appearing generous). The private keys however are entirely useless.

As amaclin said useless for who?

basil00

member

Activity: 60

Merit: 10

Quote from: amaclin on September 13, 2015, 08:13:53 AM

Congratulations!
https://blockchain.info/tx/f3aca5442d7e0129d1060d34406bdfa6bb052e60977313dd56b7d8a589f4af78
Now remove unused bytes from OP_RETURN to make your result perfect! Grin

Thanks. After fiddling around with openSSL and getting nowhere I switched to libsecp256k1 and got it working first try. All you need to do is make the nonce function return the magic value for K.

The new txs are tagged 'S' or 'SS'. I will remove this byte soon.

Some of the older encoded txs (XX, XY, XW, R, DS) will likely bounce around for a while. I've set my script to double-spend them.

Also, only SIGHASH_ALL works, otherwise other nodes reject the transaction. Non-standard or maybe I stuffed something up?

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: Evil-Knievel on September 13, 2015, 08:21:04 AM

The private keys however are entirely useless.

I took ~4BTC from these keys. What do you mean by "useless"? Useless for you? Grin

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: rz20 on September 13, 2015, 08:16:26 AM

0 btc transacted. Damn this really doesn't work and the OP is just spamming the blockchain.

The OP is doing nothing. Everything you see here has been done by others.
This is some kind of cleenup the dust.

yakuza699

hero member

Activity: 935

Merit: 1002

Quote from: rz20 on September 13, 2015, 08:16:26 AM

Quote from: amaclin on September 13, 2015, 08:13:53 AM

Quote from: basil00 on September 13, 2015, 01:24:48 AM

I tried but no luck so far, still get big sigs. What exactly is the K-value required (kinv for ECDSA_sign_ex)?

Congratulations!
https://blockchain.info/tx/f3aca5442d7e0129d1060d34406bdfa6bb052e60977313dd56b7d8a589f4af78

0 btc transacted. Damn this really doesn't work and the OP is just spamming the blockchain.

Wrong.Sending more than 0BTC to an OP_RETURN output would be non-standard.As you can see he gave everything as fees for the miners and you should know that OP_RETURN outputs does not increase UTXO.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

This message was too old and has been purged

rz20

legendary

Activity: 1330

Merit: 1001

Quote from: amaclin on September 13, 2015, 08:13:53 AM

Quote from: basil00 on September 13, 2015, 01:24:48 AM

I tried but no luck so far, still get big sigs. What exactly is the K-value required (kinv for ECDSA_sign_ex)?

Congratulations!
https://blockchain.info/tx/f3aca5442d7e0129d1060d34406bdfa6bb052e60977313dd56b7d8a589f4af78

0 btc transacted. Damn this really doesn't work and the OP is just spamming the blockchain.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: basil00 on September 13, 2015, 01:24:48 AM

I tried but no luck so far, still get big sigs. What exactly is the K-value required (kinv for ECDSA_sign_ex)?

Congratulations!
https://blockchain.info/tx/f3aca5442d7e0129d1060d34406bdfa6bb052e60977313dd56b7d8a589f4af78
Now remove unused bytes from OP_RETURN to make your result perfect! Grin

Topic: CoinWallet.eu Stress Test Cancelled + Bitcoin Giveaway - page 6. (Read 98924 times)