Re: Bitcoin bounty 0.5 btc challenge

[praveen aj]

Hai Guys,
             I managed to crack private and get uploaded into the wallet and able to send but the issue is the transaction is neither picked by any node or peer to broadcast into the network once broadcasted into node due to high fees i kept the transaction gets confirmed quickly
i am hereby the transaction signing details given to me by the wallets once i sent the bitcoin to my address.
so if anyone able to broadcast the transaction i get 3+btc i am ready to give 0.5 btc as bounty
i am here with attaching the transaction signature and raw details those who can resolve this first gets the bounty,
tx hash generated by wallet:- e17eaf148dcae51c32aa56eda87295ab91474d6a4c8817d9b4588f01b9d4b131
Raw transaction data:-
in   [304402203b77a6dff38ec72a7e4167dc1d977be95a9c86412885c5aa407efb8bd93c474f0220609f0c6824152c290c2f4123212613d4a5b17b75d29bacf9938b7906c690000e01] [00]
          outpoint:352275bb5ea9153779c4acb62d8a1919d39618a412e587e5137fad30287da699:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402203a4739860138e08237c7bc3f90d5114d8da85b464f168ee32e2f43d4280fbea702205c77854727d8f56eff7dd2e0dfd2b9d676d3dba1124a32dec700409160186d3201] [00]
          outpoint:14cc96b6d9fdba483ab297f6dd7ead3ac271b6074808ab3ade84c4a0d40a92db:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022007c74fc832c04d8549f09dad2fbad8eb7a5b1807b61c75212c10b24b916a9a9402200feb64b5871f631dffd0d6e87971e06c4747dc8e03728e6dd954df7bc05ebc5701] [00]
          outpoint:dc2c336d4eb6a3fbe1c9833c32a625413ce8845185660395d4aa4d443b03b5d7:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022015da192d1e9c7bfdbbab985430e4e68b73cb174719ffd46b4dee2f9967a68f930220768061f811285544c50ad15fce4c9034b7aed63b97390a986b6983f6bc9ecdb601] [00]
          outpoint:652367e4b5879c2707eef5a27c82416102669f7ec784d63141962a4a1c73365d:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100837956be44712602d8054f5235436f9e285d72905e2b1d58641194d17177491c0220243874c1d5ef0f6b973249d63c71ea3a265b13c3b1da24e4fd5bdcdd1751dea901] [00]
          outpoint:220e99b4640f22dc561c3a9f5c92e0a2452a4912b7e75bbe957c1cb86cf6ef32:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [30440220363f8ebbb6545bb0397a36eeecad0e626dad3dc6df97b965e4ca88226726f9d502207f8fa7c1223256159d514f43660da13cde6bc93ee49d9aeb66d1513b94f103f901] [00]
          outpoint:0f86ef78c86b565b8ffe9bccebcb609c89f55f43e2adbc4b88079898b3baecc0:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402207f0f1284a9fb45c44ee0897b68e39a274220f1b2893bbea6bc6daba1fcdc5f2602202d3b91f0ef61e3a96d716f3e8b21bb4b3f7c949d01a3ca2edb6fb00fff903f4a01] [00]
          outpoint:5d58a62cb677727e1506aaf2ef5b492cee8995fb294c0c625c541907529d4097:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022014a1eb3f4e77f8deed62bf47d58f54ad8f2901f75599a40b031ddf2a79fd57b802206f9634ce5fd0b405c77d9b65a0b457947f66e9fabae96a6e298a72f46c60458601] [00]
          outpoint:96f9bf3534e5e0c4f65d9ace93f01fd9601660d145fc69c0a301dc673c903865:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100d75e20f1f8b2262a1208fd9b6f7d7321552b09759a68a6d47c3d320811bc041b022079292bfc2dcd827d47cc0d4a3afd07fa26042f9cf6c4f629a2ee26a880e194c601] [00]
          outpoint:7e209e6d5e283ac80078586c3ce85ef74f7c4270d4e036cceef33daf0ff31307:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100bfb462b02a251f33d147cdf65e36f67ec384dbed625ba3326c6c614e915591690220530dc5609fbd205849e7f2ba3b713c30f8a0c46f40a361b1d89a4da07a4c6ad801] [00]
          outpoint:79b6661af25399593a24efb2c60b4fb9da795045bf115c9021224e92c6a9fa56:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [30450221009ce8d18e81f39cfba34ec9f15c6b1e83c9d5a22b2175e07ae063c0f95e7ed152022067baeebdce7538e0b015298884cd37ce1b8f583b0407992d5d5225d22f680ee401] [00]
          outpoint:3262eb956deb6e66d113cc14b20e7d0fcc00ac58a94c032ec4a2a7fbaa5fb52a:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402201bdcce4d4df3569b3b449ce153fabd642ae3d8a693e730b08112bd7eb1c32546022020e046189109eb163082b6496a15671d166809c2bacbae304ba098dd46a9c25d01] [00]
          outpoint:a8ac8efe4ad653642aea6e375ea9a0f06a0303308445d35970afe9df3a920d1e:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100f74478ff5e520b8c25e07c268d92ca0a9f9ba77486204f4fb814fa660e11ec0702205f97596b74b488d7d2d97227bb196d70687123a22f774be93adaca461872595301] [00]
          outpoint:6ef23e01b47245ea43481e9db8e1095417591067702a2221fb3cf4f036b156bc:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022067a6920d9667da93c636ae2e7f7899b702db35bcbd6eab678b43a92a7d55773b0220641fbac7ee03ed5f5362e94271080334ffb76e7580999bef41cb96da9d19695c01] [00]
          outpoint:7aabe144e7d083302a9956d5fc927fa166187b6345277018233daab18e5dab82:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402203da38c8de41d25706bcdb9f10a028ffeb8cc7721c3b48432b14b6a7dc26aa05a02200c30d9884cb18d50bf6505d94bb239955b3e0e02a419f7b4c2f9c5e42951329601] [00]
          outpoint:f3fb03285e6ddfc0c66e97b48565e11a1993bc38b3748b467434b8543631aaaa:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100b8544c7a1c9955aa42dec94ebaa8dc2c10ee6da47c7ec7b88ebe6af831887eb20220063f5f36c4695e9da5a5840ae6862e22948928069563afe8b3b9013b3a4e013401] [00]
          outpoint:d6915bc2b092e35a6df2e5190709f777313e6c74f5ea3b929276f6ae316a1d4a:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402207e886f0b91ca5898ba152474493b66349e6cd402329a974af8f31231a929b9fc022020015d0ccf7cb650c8f9c5510fd8595b303b8e65cadd0ec04974008671cd8e7f01] [00]
          outpoint:2d4621ddcfdc7eae231007b14856688f00b248da7447d85f7b23297c7ac118fb:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100df1c1d532691d18a0a1dc705477340be60d386e150da40d312e60d445e2ad834022015807fbea05dee57a2d0cd7bcea7fe684ede5e33f5aaf01091505f63252373a901] [00]
          outpoint:73db04ca6848820803b530513b3432a0018defa6c80e9713703f8915a6885719:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022078fb48739ee5605a27b2aaa6f6a6f2c03a1ad384c6013d2f2dc5d6cd11aa85d902201cf96103ebbb95f2dbc87ccccca73e097fef24635c40a2745e702f1b4102937901] [00]
          outpoint:b2d1b5999a06596c21f46792ca3ed3a5bf65b81f30c09b26c1a1419b2f101434:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100fca0a626e89350968228e0d8da04ebd3842558480549658063719d58101d05b1022005a9c07c038a39a8d4afe695eb948b09602447139416f76300f38497ec88de9c01] [00]
          outpoint:325f9df0c9cac98e30b02ce9e35d02eda8f15be9f89cb302454a2bb6c6bc9aeb:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022003004e1c5d35a2d9871e3249dc72d4d825dd3a268828a46f31356a448936d7a10220393a2ebc0e1d7b4894eab29bdd95fd25e7d5095bcbe94d17ccd3ac54dde3efdb01] [00]
          outpoint:a1929453b13d356cc4c46af7a06b3a6bf70d6ea97e8665aa05e35b817e6571a6:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100d3e8b0fec2acc985ab9be4a22678b70676762ae39aed646d54f4c9a09c7828760220247e754119302c21f32ee561b63d6e4a78c0068ec6427a5f305a3d74eb0e437801] [00]
          outpoint:84dc293f4d6afaa417978630e80cba6a29d3b057ab25e82b2010a4d2e39ef18c:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100e35822ba0b715c83eb9a80c97697679a09e333f99edac2f26215b23517228d8902206835b6afaef601aa4f8db4dee27869a92f7c74ec8cee959099e9ddfb5613561301] [00]
          outpoint:c29b4529c43637c3c3cb86ff4d32980a055a8a58f8b0ff83abfac924bb7d5a53:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [30440220454ae261d2b8cd4f316b3878a5a02388293dd710db4e92696d3eb093348d58e402203f4ec6f237be4323f595542918d82af2bc90a87360e31e8f8cff22c86b3581bb01] [00]
          outpoint:159d9697d9c542af4036e22897b7b4ba8ff986548f8be642b54faf948e9050c9:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022074d66e3f5b0c54cd96f6ccda98b09f012d066257c5f73e2fa86f3ec438931b830220441a59222f88851a8166ab482d860df203e4c3bacb61afb9872a5750fd92fe2001] [00]
          outpoint:c73eace587dbde385675efe97604a4d1c04b84874e48b285bfd4eb344491dfa7:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402207a67807f9878b181d63de1ac0fb2622063cf9d143f2b8b06cfef4ea896edbd0d02206054cd6bbed64fa9ef41a2968dd73aff7a2aef27d3dd1222a67d35b011a2071401] [00]
          outpoint:bd256eddb8bd570c66f101997ae41045306f1cea18f6d5f12d0e81f6383a0754:0 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3045022100cfb2407b2c96508bcc1a9c215acd5158d0cd31bf19ecb864012cb798cd951cd4022039fe041f5864a83659babd957167f1950d068fd15d8e774d4eb9f1fe56d4366201] [00]
          outpoint:e801fef675aa45cdfea623cd24d0a5c37ab8b0a32e6323c319472936ac63ad32:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [3044022064c0e8d164814c0f74a58f958703adf186f5af701e346284824d58fc1447e10902200e196d6c9a988df7bb8b3f4d66149590c192a459ccfb5c2d2c4aa18108c963cc01] [00]
          outpoint:cd03c2c6526bac5149be85b7021d0a853f9e50242e9f6b21686cf291b8d52854:0 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     in   [304402203216e4a67090cc56665738bcd78a66d4071ca31d115e84c4a6e0f3685ce80682022078854200a1d4621c4a60928562a4d2e0d4425f7155605e9eff1e4aa420c6c98b01] [00]
          outpoint:19adadbbec36fc2c14d0965da5600c099b3f4a8ec19d549d48853d4ca439abf4:1 hash160:9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68
     out  DUP HASH160 [d880f4772ccae13030f67c89436d96ee74e7a635] EQUALVERIFY CHECKSIG 3.71 BTC
     out  DUP HASH160 [9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68] EQUALVERIFY CHECKSIG 0.00125204 BTC
error i am getting in wallet is transaction showing pending/uncofirmed with error " the transaction is not yet confirmed, it is unknown how many peers has seen this transaction"
If any able to successfully broadcast the transaction and help me i am happy to give 0.5 btc bounty
image to view transaction https://imgur.com/a/QS3OwX5
Thank you

[1713535805]

1713535805

[1713535805]

1713535805

[1713535805]

1713535805

[1713535805]

1713535805

[n0nce]

Congratulations for solving a Bitcoin challenge - which one was it, if I may ask?
Can you post the link to blockchain.info of this transaction?
To me it seems you just have to wait a little! Or when did you publish that transaction?

You can also use blockchain.info 'pushtx' feature: https://www.blockchain.com/btc/pushtx

[praveen aj]

this transaction is not picked by up by any node or peer till yet so it may not be visible in blockchain now i shared tx hash generated by my wallet above

[n0nce]

this transaction is not picked by up by any node or peer till yet so it may not be visible in blockchain now i shared tx hash generated by my wallet above

Can you export the raw transaction as hex and paste it here? Maybe something's wrong with it, causing nodes to reject it.

[NotATether]

this transaction is not picked by up by any node or peer till yet so it may not be visible in blockchain now i shared tx hash generated by my wallet above

Can you export the raw transaction as hex and paste it here? Maybe something's wrong with it, causing nodes to reject it.

I second this. It will be much easier to parse the transaction details than this jumble of data in the first post (from which program did you copy that data from anyway?  )

[BlackHatCoiner]

Is there, for real, a forum member who received so much money from a bounty of another user? Why do I think the users never intend to share such prize, but hang from your help and believe they're gonna give them to you afterwards, but never do?

Someone please contradict me.


The reason for the denial of the nodes to relay a transaction could be from the transaction's invalidity (such as false signature) to exceedingly low fee. You should provide us the raw tx to be able to tell you for sure.

[NotATether]

Someone please contradict me.

Last year, someone once offered me (by email) at least 0.3BTC to find the password for their bitcoin wallet hash. Some other members PMed me about rewarding smaller sums in exchange for seedphrase et al. recovery.

[Minase]

don't even bother   the funds on that address cannot be spent because the private key generating the empty public key is the infinity point....

[n0nce]

Is there, for real, a forum member who received so much money from a bounty of another user? Why do I think the users never intend to share such prize, but hang from your help and believe they're gonna give them to you afterwards, but never do?

Someone please contradict me.


The reason for the denial of the nodes to relay a transaction could be from the transaction's invalidity (such as false signature) to exceedingly low fee. You should provide us the raw tx to be able to tell you for sure.

I don't care about the bounty, I'm right now more intrigued by that 'raw transaction' dump. It includes all utxo's of the address with 3+ BTC on it, and 'hash160' values for each, which are all equal (9f7fd096d37ed2c0e3f7f0cfc924beef4ffceb68) = 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh to the address with the coins.

Trying to find a decoder for this format yielded nothing helpful so far. Never seen it so far in Bitcoin Core or Electrum. I'm used to the hex and json formats only.

Edit: Yeah, looking at that 'raw transaction' data, it seems it's basically just inputs and outputs, there's definitely stuff missing.

[BlackHatCoiner]

Last year, someone once offered me (by email) at least 0.3BTC to find the password for their bitcoin wallet hash. Some other members PMed me about rewarding smaller sums in exchange for seedphrase et al. recovery.

Notice that this happens only if you've given the necessities to spend them yourself. For instance, the seed phrase, the private keys etc. They, essentially, trust you to recover the money and you can spend them yourself due to the access you have; you could even rip them off if you wanted. If they promise they'll give you a spare once you help them find the solution to their problem, they'll most likely disappear without giving you a 'toshi.

don't even bother   the funds on that address cannot be spent because the private key generating the empty public key is the infinity point....

How did you understand that the public key is empty? I don't see any public keys posted except a 160-bit number.

Trying to find a decoder for this format yielded nothing helpful so far. Never seen it so far in Bitcoin Core or Electrum. I'm used to the hex and json formats only.

What exactly are you trying to decode? The tx raw?

[praveen aj]

this is the exact thing happened i managed upload the private key in an old wallet and after syncing finished it shown available balance i managed to attempt to send btc to my address it created a transaction and showing 'transaction is not confirmed yet, it is unknown how many peers has seen this transaction"
when i clicked on the transaction details it shown the raw transaction details which i posted above and bitcoin deducted from the wallet i uploaded it is not picked by any peer or node, if somebody help me to broadcast the transaction and when its get confirmed i am happy to send 0.5 btc this is 100% as i promised.
the image of the transaction i shared above

[Minase]

just a simple conversion from ripemd160 to address which equals to 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh
if you google that address you will see some topics even here on bitcointalk about that address  

0x00: Uncompressed private key: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
Uncompressed WIF: 5Km2kuu7vtFDPpxywn4u3NLpbr5jKpTB3jsuDU2KYEqetwr388P
Uncompressed public key: EMPTY
Uncompressed address: 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh
Compressed private key: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD036414101
Compressed WIF: L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFqRzExJJ
Compressed public key: EMPTY
Compressed address: 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh

don't even bother  the funds on that address cannot be spent because the private key generating the empty public key is the infinity point....

How did you understand that the public key is empty? I don't see any public keys posted except a 160-bit number.

[n0nce]

don't even bother   the funds on that address cannot be spent because the private key generating the empty public key is the infinity point....

How did you understand that the public key is empty? I don't see any public keys posted except a 160-bit number.

Trying to find a decoder for this format yielded nothing helpful so far. Never seen it so far in Bitcoin Core or Electrum. I'm used to the hex and json formats only.

What exactly are you trying to decode? The tx raw?

Yeah I was trying to understand the dump that was posted.

https://www.reddit.com/r/Bitcoin/comments/2t3vn0/i_cant_send_my_btc_a_triangle_apear_i_use_multibit/
The utxo's are unspendable indeed, due to a bug. Coins are lost forever.

@praveen aj these funds are unspendable because of the unallowed 0 exponent.

[BlackHatCoiner]

just a simple conversion from ripemd160 to address which equals to 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh

I know the address and the fact that there's a private key, which gives an empty public key which once hashed with hash160 and encoded with base58 gives it, but spending from that address isn't impossible. I have no fuckin' idea what's OP doing, but there are around 2^96 - 1 besides that invalid one that can indeed be used to unlock the outputs.


@praveen aj, did we find it? Is it because the public key you've used is disallowed? It's highly unlikely to be a different case. Still, though, you could give us the tx raw to verify it.

[praveen aj]

https://imgur.com/a/QS3OwX5
even with mining pool people so that they can force to broadcast the transaction.
if the transaction is broadcasted then i think it gets confirmed
Means the transaction is rejected by nodes or some peers are not seeing the transaction

[Minase]

just a simple conversion from ripemd160 to address which equals to 1FYMZEHnszCHKTBdFZ2DLrUuk3dGwYKQxh

I know the address and the fact that there's a private key, which gives an empty public key which once hashed with hash160 and encoded with base58 gives it, but spending from that address isn't impossible. I have no fuckin' idea what's OP doing, but there are around 2^96 - 1 besides that invalid one that can indeed be used to unlock the outputs.

That is true, there are ~2^96 valid private keys but it's highly unlikely that the OP found an address collision. (didn't hear that to happen even a single time, but maybe it's just me)

[nc50lc]

Your other post in the services board says:

Hai Guys,
             I managed to crack private of an old dormant wallet and -snip-

You mean "found" this private key?: Bitcoin Elliptic curve point multiplication results in key ZERO
Is that why you're using an unknown client, probably something that accepts invalid private keys that are outside of the curve.

[praveen aj]

the error i am getting when i tried to decode raw tx is
https://imgur.com/a/4LeOqCE
the public key in hex for this address is 049663999D864D6D1A79FFB0C547D19CB5A51123888AD4BDAE5CCEDB61CC3239BA4182C2088B09D 67ADEDF1BDC543B5F336D017017FF8D83E44D75A00A3D6BEE
i read it from other post

[BlackHatCoiner]

https://imgur.com/a/QS3OwX5
even with mining pool people so that they can force to broadcast the transaction.
if the transaction is broadcasted then i think it gets confirmed
Means the transaction is rejected by nodes or some peers are not seeing the transaction

If the transaction uses an empty public key, then it's invalid. This means that a block containing the signature from that key would also be invalid. So it doesn't have to do with the miners. It simply isn't valid, that's why they reject it.

the error i am getting when i tried to decode raw tx is
https://imgur.com/a/4LeOqCE

That isn't a raw tx. It should look like this in length:

decoderawtransaction "0100000001dfee7c0aa6cb1cf8f4c9ac9339d9b6078d792a106267f93802ac75b52a6ad0de00000 0006a47304402203e408f62cf85e326dc4066636c306b85ce0b94dd94c001fbfd35da58979def3f 022075255c85e927340d4777963357cb03482566e29f93cc9f590398dfb3a89cbb970121028ce82 9db535d42389defbf9ba58731f56ddb1cc7a189e5e30a85d63eb225b5d2ffffffff018813000000 0000001976a91496a07833918317f2e0e23eea585970831da66f8988ac00000000"

Unless if I'm missing something from your screenshot.

That is true, there are ~2^96 valid private keys but it's highly unlikely that the OP found an address collision. (didn't hear that to happen even a single time, but maybe it's just me)

Me neither, but we shouldn't take it for granted. It's wrong to assume for a certain public key if the person hasn't stated they hashed that one before.

[_Counselor]

the public key in hex for this address is 049663999D864D6D1A79FFB0C547D19CB5A51123888AD4BDAE5CCEDB61CC3239BA4182C2088B09D 67ADEDF1BDC543B5F336D017017FF8D83E44D75A00A3D6BEE
i read it from other post

This public key belongs to 1BbBEt3uuNTo867wXnD2p4iv478Tcs3h1H and 1FG37pnmz9WPB413hMnn3VZEg3nF2QkUPA addresses