P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
alredy confrmed
ur replacement is uselss
Topic: Help me relay a double-spend transaction (Read 5163 times)
P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
alredy confrmed
ur replacement is uselss
first transaction confirmed
doublespend tx orphaned
doublespend tx orphaned
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
Quote
I will give some BTC to you for pushing.
Pushed to network. By me. 07:34:27 UTC
http://respends.thinlink.com/tx/6ef783dd4b83530d8c8e73f7a6a63abde420a07749c4dc3b25247deb50c7e86c
Now you should wait.
What is a fee for your second tx?
My address 1ENnzep2ivWYqXjAodTueiZscT6kunAyYs
UPD: OK, bc.i shows a double-spending
https://blockchain.info/tx/ef03919accdbc977244ab0dd58b72698d4582d1b381495433f54d4019101dd28
The second tx fee is 0.0001
Thank you very much! Please wait till it get 1 conf, then only I can spend from the change.
0.02 will be enough, right? Reply in PM if you can't reply here! Edit: Paid! ad1ffc3339d3992af385e615634c9a2b0f91d9906fc7e2af5a1fdfc9bccc3c7c
~~MZ~~
Quote
I will give some BTC to you for pushing.
Pushed to network. By me. 07:34:27 UTC
http://respends.thinlink.com/tx/6ef783dd4b83530d8c8e73f7a6a63abde420a07749c4dc3b25247deb50c7e86c
Now you should wait.
What is a fee for your second tx?
My address 1ENnzep2ivWYqXjAodTueiZscT6kunAyYs
---------------
UPD: OK, bc.i shows a double-spending
https://blockchain.info/tx/ef03919accdbc977244ab0dd58b72698d4582d1b381495433f54d4019101dd28
The second tx fee is 0.0001
---------------
UPD: respends.thinlink.com shows the timestamp 07:34:27
bc.i shows the timestamp 2014-11-02 07:33:09
Can anybody push this tx? I have signed it. I am trying to double spend the tx I spend earlier, brainwallet removed the fees when I sent it. I will give some BTC to you for pushing. I tried online services like Blockchain, Eligius and btc.blockr.io . Thanks in advance!
P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
You will probably need to wait 24~ hours for the previous TX to be 'forgotten' by the nodes mempool. You also have the possibility that your TX will get confirmed despite the no fee attached Code:
010000000128dd019101d4543f439514381b2d58d49826b758ddb04a2477c9dbcc9a9103ef010000008a473044022076802a193958fdc98bc8992f889a49b90925ca6c88531ef94a75eec814d055b30220676286b74e47a371ddfac1fafb4ba404e62ed6f18eeb84bc268a1259cd538c82014104f71963151bd53277add62216d6c1c3a1a8f6a46bc1c9288b8b2039cdd18887d6179866001c73a8d0bc74d1e19b2e1f8e6bfa45de9b4d49de0263fcacf035503affffffff2170820300000000001976a914952445b1e82ed24f892406b28706cd3bab518c0888ac00e20400000000001976a914a5553544e95a9671d5b41f8879fbe5e47d072a4888ac70820300000000001976a91494a6be5604a911aa0e7ec0880fa24f955db977b788ac70f30500000000001976a9148dda645e24d74ad2f07dbe598b2aef52da8191a788ac70f30500000000001976a914ebcb634ba47e228a2ebf240131735c9facb5c52b88ac605b0300000000001976a91433af8c8ef6d9a02c5869e02d799d7470e5679da388ac90940d00000000001976a9145152710749e66b7cc50a88f58e272fb4cb0a294588ac90650000000000001976a9145da521ffb3da3670266432e060f5a81ae9e7a9d488ac48ee0000000000001976a9141a1e892bd0497ad62e11fe42c96151227bb3ad2e88ac88f50400000000001976a914775f847e431edb1dac4424599f3b35e43782a49088ace86e0300000000001976a91484b98509115977b56fde515c3a53fa304b7fbc3c88acf0ba0400000000001976a9143edab6dfa95a748885a9767787f3edd803a677c088ace0930400000000001976a9146d4f1503a7b73983b6a16484a5a957f9a552332088ac38c10100000000001976a914f42696b3fcf9732b56013a925190a9dfae2c586188acc0d40100000000001976a914ddf337461b833c6fc0348d8f586cb6489ddbb43b88aca0860100000000001976a9148e1a160b5d2890221ee6bacbc92537a5a0a0eba488ac38c10100000000001976a914c606556ded35d2bc229b07450fac05ffb823831b88acf0ba0400000000001976a914b7f02d80c966a40dca906193bd35cd69bb8aec8788aca0800200000000001976a914551afaf1ae65edb7401d6fd1e77f98d12ceeb01788ac785d0200000000001976a91486ff6fa5841aea10d424cd57dad2eaec304f9e9088ace0220200000000001976a914a41c8d117bc6b939aff5a352a49fb19ec235889388ac00e20400000000001976a9140f8926fb561c546cae37dee6cfe8adfdb003799588acc0b60600000000001976a914135016b33963a979e77f46fa5daa0bd0013502fb88ac80a90300000000001976a9143ba23e0d9667206b4f953f316363c523b56c341c88acc0570100000000001976a914d0772df29886d2eb31ed011dc78347ebbdc3815588ace01c0300000000001976a914fb5c4e270abbd89a8b9f062d97d53a5a974c8e4588ace00a0600000000001976a914803a1be759f99ba82212f34180d6ee7e7cd3344288ac60610200000000001976a9146ae6f15a5f1605b585a6068f054a9cc64200e54088ac60e40100000000001976a91427db10db8c3c3192eb2d65018303cd5f8095772e88acd8590000000000001976a9148a2789791db82ed41a88f37b6c821bd62befaf4588acf09c0900000000001976a914f03cb7b3ac29f254163d3aadfe14a82c50d2741e88ac400d0300000000001976a9143fe8901eea7f38e3e97093a7286b37187b10347f88ac082b4500000000001976a914e64666d3324804202551768f76ac7c8447cfa92c88ac00000000
P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
Can anybody push this tx? I have signed it. I am trying to double spend the tx I spend earlier, brainwallet removed the fees when I sent it. I will give some BTC to you for pushing. I tried online services like Blockchain, Eligius and btc.blockr.io . Thanks in advance!
P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
Code:
010000000128dd019101d4543f439514381b2d58d49826b758ddb04a2477c9dbcc9a9103ef010000008a473044022076802a193958fdc98bc8992f889a49b90925ca6c88531ef94a75eec814d055b30220676286b74e47a371ddfac1fafb4ba404e62ed6f18eeb84bc268a1259cd538c82014104f71963151bd53277add62216d6c1c3a1a8f6a46bc1c9288b8b2039cdd18887d6179866001c73a8d0bc74d1e19b2e1f8e6bfa45de9b4d49de0263fcacf035503affffffff2170820300000000001976a914952445b1e82ed24f892406b28706cd3bab518c0888ac00e20400000000001976a914a5553544e95a9671d5b41f8879fbe5e47d072a4888ac70820300000000001976a91494a6be5604a911aa0e7ec0880fa24f955db977b788ac70f30500000000001976a9148dda645e24d74ad2f07dbe598b2aef52da8191a788ac70f30500000000001976a914ebcb634ba47e228a2ebf240131735c9facb5c52b88ac605b0300000000001976a91433af8c8ef6d9a02c5869e02d799d7470e5679da388ac90940d00000000001976a9145152710749e66b7cc50a88f58e272fb4cb0a294588ac90650000000000001976a9145da521ffb3da3670266432e060f5a81ae9e7a9d488ac48ee0000000000001976a9141a1e892bd0497ad62e11fe42c96151227bb3ad2e88ac88f50400000000001976a914775f847e431edb1dac4424599f3b35e43782a49088ace86e0300000000001976a91484b98509115977b56fde515c3a53fa304b7fbc3c88acf0ba0400000000001976a9143edab6dfa95a748885a9767787f3edd803a677c088ace0930400000000001976a9146d4f1503a7b73983b6a16484a5a957f9a552332088ac38c10100000000001976a914f42696b3fcf9732b56013a925190a9dfae2c586188acc0d40100000000001976a914ddf337461b833c6fc0348d8f586cb6489ddbb43b88aca0860100000000001976a9148e1a160b5d2890221ee6bacbc92537a5a0a0eba488ac38c10100000000001976a914c606556ded35d2bc229b07450fac05ffb823831b88acf0ba0400000000001976a914b7f02d80c966a40dca906193bd35cd69bb8aec8788aca0800200000000001976a914551afaf1ae65edb7401d6fd1e77f98d12ceeb01788ac785d0200000000001976a91486ff6fa5841aea10d424cd57dad2eaec304f9e9088ace0220200000000001976a914a41c8d117bc6b939aff5a352a49fb19ec235889388ac00e20400000000001976a9140f8926fb561c546cae37dee6cfe8adfdb003799588acc0b60600000000001976a914135016b33963a979e77f46fa5daa0bd0013502fb88ac80a90300000000001976a9143ba23e0d9667206b4f953f316363c523b56c341c88acc0570100000000001976a914d0772df29886d2eb31ed011dc78347ebbdc3815588ace01c0300000000001976a914fb5c4e270abbd89a8b9f062d97d53a5a974c8e4588ace00a0600000000001976a914803a1be759f99ba82212f34180d6ee7e7cd3344288ac60610200000000001976a9146ae6f15a5f1605b585a6068f054a9cc64200e54088ac60e40100000000001976a91427db10db8c3c3192eb2d65018303cd5f8095772e88acd8590000000000001976a9148a2789791db82ed41a88f37b6c821bd62befaf4588acf09c0900000000001976a914f03cb7b3ac29f254163d3aadfe14a82c50d2741e88ac400d0300000000001976a9143fe8901eea7f38e3e97093a7286b37187b10347f88ac082b4500000000001976a914e64666d3324804202551768f76ac7c8447cfa92c88ac00000000
P.S. The tx I sent earlier : e0f484aa830447a1c589e1be89d9d605dee9823f303abd757784d0d6449a78ca
~~MZ~~
Shady stuff you are trying here, but im hope it is to audit bitcoin code and to improve bitcoin secuirty in the end
Neither of those.I don't do any shady stuff and I don't want to "audit the bitcoin code" all I want is to learn more about bitcoin. Quote
Yes I understand, so I guess the only thing that I could do is just wait for it to drop or connect to other nodes and try rebroadcasting the double-spend tx again.
OK, you have got it.Do not just wait. Connect to as many nodes as you can. And rebroadcast tx manually.
Quote
but apparently it didn't got here http://respends.thinlink.com/ even though I left my client running for like 2 hours.
Have you read this sentence from the site you mention:
Quote
Most of the bitcoin network silently drops double-spends, so this list is far from complete.
Do you understand the meaning?No reason to help for free for "saving" a couple of cents.
Maybe there are few generous and kind people who could help me out 
Shady stuff you are trying here, but im hope it is to audit bitcoin code and to improve bitcoin secuirty in the end
Quote
but apparently it didn't got here http://respends.thinlink.com/ even though I left my client running for like 2 hours.
Have you read this sentence from the site you mention:
Quote
Most of the bitcoin network silently drops double-spends, so this list is far from complete.
Do you understand the meaning?Quote
So I fault maybe you guys could help me(and him) to return those coins by double-spending.
No reason to help for free for "saving" a couple of cents.
Ok I am unlocking this thread again as recently I saw this https://bitcointalksearch.org/topic/m.9235371 in that thread dude posted this transaction https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 he said it doesn't confirm and people were saying just don't broadcast it but I fault maybe there is a way to double-spend. So I created this transaction https://blockchain.info/tx/0c9b97eabf40271ef4f5061903e9731ac95d0bbe6bc9fb9e93fc9a18e16af2f2 I tried to double-spend it and pushed it on my bitcoin-qt debug console and got this 5d7a1d6a648fc1944c750e48c65e3204b09a2e93bdd4370c7666398e14b25508 but apparently it didn't got here http://respends.thinlink.com/ even though I left my client running for like 2 hours. So I fault maybe you guys could help me(and him) to return those coins by double-spending.
P.S I guess I haven't learned how to double-spend properly.
P.S I guess I haven't learned how to double-spend properly.
Attackers do not read these topic! They do write it 
You are a funny dude aren't you? Up to you. It is certainly your right to do it on not.
Not gonna delete it just gonna lock it and leave it rest. Quote
Because of this i want to close this topic(i already learned what i want) (should i?)
Up to you. It is certainly your right to do it on not.Quote
as an attacker can read this topic learn how to double-spend
Attackers do not read these topic! They do write it Quote
and attack those "stupid merchant's" which i don't really want as bitcoin will get a bad name for it.
I think that the real attacker is much more clever than you and me.So, the real tools against them are truth, knowledge and publicity
Double-spending 0-confirmations is accepted as possible. Satoshi Dice was the first large player to experience the error of their ways in accepting 0-confirmation transactions - a player could immediately see that their bet (a transaction with low fees) lost, and then double-spend a much more favorable transaction that might be mined instead. Even a 2% success rate beat the house.
Bitcoin accepts the first spend of a UXTO that it sees, accepting it into the memory pool, and rejects later transactions outright. Miners are free to alter this behavior in their own software, perhaps accepting later double-spends that have more fee. It is not documented that any prominent miners have done so, because it against the interest of Bitcoin.
The 0 confirmation "attack" (it's not really an attack, because you were warned) canonically takes the form:
1. Find a stupid merchant that will give you something irrevocable for a 0-confirmation transaction.
2. Discover something about network topology that allows you to narrowcast a payment to just the merchant or nodes around him,
3. simultaneously broadcast a double-spend transaction directly to mining nodes and their backbone.
This may cause the merchant's Bitcoin to show the bad transaction and reject the later one more likely to be mined. Techniques to mitigate such an attack and still have some confidence in taking a 0-confirmation transaction within ~10 seconds of receipt involve employing many nodes and many connections to diverse nodes throughout the network which listen for any double-spend attempts and block the purchase if such an attempt is made. Merchant software should also know about fees and be less trusting of transactions without an adequate fee for immediate mining.
Because of this i want to close this topic(i already learned what i want) (should i?) as an attacker can read this topic learn how to double-spend and attack those "stupid merchant's" which i don't really want as bitcoin will get a bad name for it. Bitcoin accepts the first spend of a UXTO that it sees, accepting it into the memory pool, and rejects later transactions outright. Miners are free to alter this behavior in their own software, perhaps accepting later double-spends that have more fee. It is not documented that any prominent miners have done so, because it against the interest of Bitcoin.
The 0 confirmation "attack" (it's not really an attack, because you were warned) canonically takes the form:
1. Find a stupid merchant that will give you something irrevocable for a 0-confirmation transaction.
2. Discover something about network topology that allows you to narrowcast a payment to just the merchant or nodes around him,
3. simultaneously broadcast a double-spend transaction directly to mining nodes and their backbone.
This may cause the merchant's Bitcoin to show the bad transaction and reject the later one more likely to be mined. Techniques to mitigate such an attack and still have some confidence in taking a 0-confirmation transaction within ~10 seconds of receipt involve employing many nodes and many connections to diverse nodes throughout the network which listen for any double-spend attempts and block the purchase if such an attempt is made. Merchant software should also know about fees and be less trusting of transactions without an adequate fee for immediate mining.
Quote
It is not documented that any prominent miners have done so, because it against the interest of Bitcoin.
There is no such thing as "interest of Bitcoin".
There is "interest of me" and "interest of all others".
FYI https://en.wikipedia.org/wiki/Tragedy_of_the_commons
Double-spending 0-confirmations is accepted as possible. Satoshi Dice was the first large player to experience the error of their ways in accepting 0-confirmation transactions - a player could immediately see that their bet (a transaction with low fees) lost, and then double-spend a much more favorable transaction that might be mined instead. Even a 2% success rate beat the house.
Bitcoin accepts the first spend of a UXTO that it sees, accepting it into the memory pool, and rejects later transactions outright. Miners are free to alter this behavior in their own software, perhaps accepting later double-spends that have more fee. It is not documented that any prominent miners have done so, because it against the interest of Bitcoin.
The 0 confirmation "attack" (it's not really an attack, because you were warned) canonically takes the form:
1. Find a stupid merchant that will give you something irrevocable for a 0-confirmation transaction.
2. Discover something about network topology that allows you to narrowcast a payment to just the merchant or nodes around him,
3. simultaneously broadcast a double-spend transaction directly to mining nodes and their backbone.
This may cause the merchant's Bitcoin to show the bad transaction and reject the later one more likely to be mined. Techniques to mitigate such an attack and still have some confidence in taking a 0-confirmation transaction within ~10 seconds of receipt involve employing many nodes and many connections to diverse nodes throughout the network which listen for any double-spend attempts and block the purchase if such an attempt is made. Merchant software should also know about fees and be less trusting of transactions without an adequate fee for immediate mining.
Bitcoin accepts the first spend of a UXTO that it sees, accepting it into the memory pool, and rejects later transactions outright. Miners are free to alter this behavior in their own software, perhaps accepting later double-spends that have more fee. It is not documented that any prominent miners have done so, because it against the interest of Bitcoin.
The 0 confirmation "attack" (it's not really an attack, because you were warned) canonically takes the form:
1. Find a stupid merchant that will give you something irrevocable for a 0-confirmation transaction.
2. Discover something about network topology that allows you to narrowcast a payment to just the merchant or nodes around him,
3. simultaneously broadcast a double-spend transaction directly to mining nodes and their backbone.
This may cause the merchant's Bitcoin to show the bad transaction and reject the later one more likely to be mined. Techniques to mitigate such an attack and still have some confidence in taking a 0-confirmation transaction within ~10 seconds of receipt involve employing many nodes and many connections to diverse nodes throughout the network which listen for any double-spend attempts and block the purchase if such an attempt is made. Merchant software should also know about fees and be less trusting of transactions without an adequate fee for immediate mining.
... and paid for the lesson
Alright this time i tried to double-spend this transaction https://blockchain.info/tx/93ea867e014898d17d9d2de9399b031cb16761b76627913fd075c2ab16034846 i put a generous 0.0005 fee on a 3006 bytes tx and pushed it on eligius i got this
Update Holy shit took less than one minute to confirm https://blockchain.info/tx/03ad2dfe49617c4744629a1d2d3f49323ef4b13fc22fe74883dbf2b057f5452d
Update2 I guess i have learned a lesson on how to double-spend
Thanks for everyone who answered my question's especially amaclin and danny
Code:
Trying to send...
array(3) {
["result"]=>
string(64) "03ad2dfe49617c4744629a1d2d3f49323ef4b13fc22fe74883dbf2b057f5452d"
["error"]=>
NULL
["id"]=>
string(1) "1"
}
Response = 0
I assume it will be mined in the next eligus block, lets see how it goes...array(3) {
["result"]=>
string(64) "03ad2dfe49617c4744629a1d2d3f49323ef4b13fc22fe74883dbf2b057f5452d"
["error"]=>
NULL
["id"]=>
string(1) "1"
}
Response = 0
Update Holy shit took less than one minute to confirm https://blockchain.info/tx/03ad2dfe49617c4744629a1d2d3f49323ef4b13fc22fe74883dbf2b057f5452d
Update2 I guess i have learned a lesson on how to double-spend
Thanks for everyone who answered my question's especially amaclin and danny
I thought that http://respends.thinlink.com/ server itself relays double-spend transaction's (yeah kind of dumb) So i assume there is no way to add http://respends.thinlink.com/ as a node or there is?
It says on the site that they run a node. Contact them to find out?
Jump to: