I think that mempool knows about this problem that the 66 puzzle address is in danger, so the developers could implement protection against bots there
that mempool will only accept the first transaction, the rest will be blocked at least for these puzzle addresses with a low range
Limiting Transactions: Mempool can be configured to only accept the first transaction for specific addresses, thus blocking further exploit attempts
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 66. (Read 230409 times)
Pure self-contained Python Kangaroo with no libraries required. 225K Hops per second.
DO NOT USE THIS TO SEARCH FOR 130. It is just an educational, reference-only example. All the math uses Python integers.
You need to add the lower boundary of the original search range to the found key to get the correct answer (because of the range was shifted to start at 0).
Before:
Code:
_, ops, hashmap_size = kangaroo_with_results(k1, k2, P, dp, herd_size)
After:
Code:
k_cand, ops, hashmap_size = kangaroo_with_results(k1, k2, P, dp, herd_size)
print(f'Final Key: {hex(k_cand[0] + (1 << (idx - 1)))}'). # add back initial offset
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
You don't need to do it.
You skeered? LOL. Let's just try it. It's already set up.
I will be banned by mempool.space due to DDoS attack LOL.
SO, you have a botnet to send transactions ?
Nope. But it's not a bad idea. The more IP addresses and computers involved the better.
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
You don't need to do it.
You skeered? LOL. Let's just try it. It's already set up.
I will be banned by mempool.space due to DDoS attack LOL.
SO, you have a botnet to send transactions ?
You skeered? LOL. Let's just try it. It's already set up.
Wait at least until we finish work, it's 9:26 am and i am just came into office 20 mins too late and got straight motivated by you, but who cares. Will you move the coins today?
No, no time soon (maybe later today - 16 hours or so, at the earliest), I want the people with bots to have the chance to load it into their bot machine lol. So you got time Sasa!
Quote
I will be banned by mempool.space due to DDoS attack LOL.
Nah, your IP had a few days to cool off lol. I know you have tweaked your bot. Mind as well give it a whirl.
Child Pays For Parent (CPFP) in Bitcoin what it does in practice
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
You don't need to do it.
You skeered? LOL. Let's just try it. It's already set up.
I will be banned by mempool.space due to DDoS attack LOL.
You skeered? LOL. Let's just try it. It's already set up.
Wait at least until we finish work, it's 9:26 am and i am just came into office 20 mins too late and got straight motivated by you, but who cares. Will you move the coins today?
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
You don't need to do it.
You skeered? LOL. Let's just try it. It's already set up.
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
You don't need to do it.
You can use nomachine's Rust Kangaroo a few posts back, or write a Python script that does the job according to your requirements (e.g. "that actually works").
Too slow? Well, don't expect to find something that "actually works", is fast, and solves 130, sitting out there for you to snug up and inherit 13 BTC tomorrow.
Too slow? Well, don't expect to find something that "actually works", is fast, and solves 130, sitting out there for you to snug up and inherit 13 BTC tomorrow.
Not in Rust. Pure C++ with GMP. Here is the latest version that goes 470K Hops per second.
Theoretically, with 12 cores, it can achieve 5 million hops per second.
The more cores you have, the better the result will be.
However, it's not worth using this for a puzzle above 70bit. A GPU must be used instead....
Pure self-contained Python Kangaroo with no libraries required. 225K Hops per second.
DO NOT USE THIS TO SEARCH FOR 130. It is just an educational, reference-only example. All the math uses Python integers.
kangaroo.py
Code:
import math, os, sys, time
....
Puzzle 48:
Code:
processors: 2048
num jump distances: 38
max jumps per tame kangaroo: 6899
max jumps per wild kangaroo: 11586
expected total jumps: 18927375 24.17 bits
avg real jump distance: 7233629130 32.75 bits
avg expected jump distance: 6074001000 32.50 bits
expected max tame distance: 190638869267657 47.44 bits
...
Ops: 17607859 Table size: 68719 Speed: 225400 ops/s
Key: 0x2de6d7ce3b9b
Group ops: 18288933
Ops: 18288933 Stored: 71317
Speed: 222616 ops/s
You need to add the lower boundary of the original search range to the found key to get the correct answer (because of the range was shifted to start at 0).
In regards to all the RBF issues lately, would it not be more productive to push on the Bitcoin developers themselves to fix it? What's so bad about making no RBF actually mean NO RBF? You know, the first-seen spend transaction with NO-RBF/Opt-out-of-RBF flag is the only transaction that the network accepts and cannot be replaced/modified by any other means? It will either get mined into a block eventually, or in the case the fees are too low, sit in the mempool for an indefinite amount of time. Or does their say not even matter because the mining pools themselves would not adopt such a fix, given that it is actually not in their best interest to do so?
Bitcoin is not broken on it's full strength. The thing that is broken is this puzzle on this restricted range.
It would be wiser if the reward was placed on a regular address and you could calculate the private key of the reward address from the private key of the restricted address with a published deterministic algorithm.
Ok, all of you BOT owners. Get ready for round 2 of RBF test.
I am a newb with ding certain things on the blockchain and what I am trying to do. I probably shouldn't be doing this, but sometimes, mistakes, are the best things to learn from.
I would like all to participate as they did in the last 66 bit bot test. But def at least the winner, albert0bsd. But I know the more, the better chances to test different strategies or programs/processes, so I would like to get all bot owners on board.
Same setup, key is in the 66 bit range.
Address:
166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb
It seemed like everyone has an auto bot...meaning all you are doing is putting in the address on some type of watch list, and once your program gets a hit for the address, the bots do their thing to find the key and alter the original transaction.
So if everyone who is going to participate, put in the above address into your bot ASAP. I would like to get a response back from at least albert0bsd that he is entered the address and is ready to proceed.
All I ask, if one of you are successful in diverting the coinage, you PM me and tell me how you did it. That's all. Just a request, not a requirement lol.
I'm not sure I will say the exact time I send funds out of the address, because that is more realistic to 66's transfer, no one is going to let us know they are about to sweep the coins...but that could change.
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
I am a newb with ding certain things on the blockchain and what I am trying to do. I probably shouldn't be doing this, but sometimes, mistakes, are the best things to learn from.
I would like all to participate as they did in the last 66 bit bot test. But def at least the winner, albert0bsd. But I know the more, the better chances to test different strategies or programs/processes, so I would like to get all bot owners on board.
Same setup, key is in the 66 bit range.
Address:
166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb
It seemed like everyone has an auto bot...meaning all you are doing is putting in the address on some type of watch list, and once your program gets a hit for the address, the bots do their thing to find the key and alter the original transaction.
So if everyone who is going to participate, put in the above address into your bot ASAP. I would like to get a response back from at least albert0bsd that he is entered the address and is ready to proceed.
All I ask, if one of you are successful in diverting the coinage, you PM me and tell me how you did it. That's all. Just a request, not a requirement lol.
I'm not sure I will say the exact time I send funds out of the address, because that is more realistic to 66's transfer, no one is going to let us know they are about to sweep the coins...but that could change.
This may fail, may be successful. We all shall see.
Am I missing any information/anything else to put out there?
Ok, bot owners, let's get ready to rumble. Who is ready? Let's do it.
In regards to all the RBF issues lately, would it not be more productive to push on the Bitcoin developers themselves to fix it? What's so bad about making no RBF actually mean NO RBF? You know, the first-seen spend transaction with NO-RBF/Opt-out-of-RBF flag is the only transaction that the network accepts and cannot be replaced/modified by any other means? It will either get mined into a block eventually, or in the case the fees are too low, sit in the mempool for an indefinite amount of time. Or does their say not even matter because the mining pools themselves would not adopt such a fix, given that it is actually not in their best interest to do so?
Fix what? There is nothing broken here, buddy. RBF, no RBF, are irrelevant at the protocol level. If you push a TX to pool A and I push a TX to pool B, the network gives zero f**ks about RBF or no RBF. If I push a TX and change my mind, it is my right to be able to change the destination, and this is what RBF is about. You are asking for adding a feature that forbids such rights, resulting in a disaster. Are you sure about that?
Nah. There are too many numbers on the screen.
I have almost the same script with Jacobian coordinates in C++ but using #include
It's not a million per second, but it's very close.
Are you sure about that? If my script runs at 225k op/s in shitty Python interpreted code, a native version won't run 4 times faster. It would run 50 times faster. On a single core. I'm too tired to prove this. Using libsecp256k1 instead of GMP or whatever, and doing the same batched addition as in my script (which is the core reason of the performance multiplier) reaches 10 M+ op/s, no questions asked. So on an i9 with 6 performance cores it does 60M op/s, and also the rest of 14 efficiency cores each contribute an additional 8M op/s. So a total of around 170 M op/s. But this is futile, it's just a complete waste of electricity. It's not a million per second, but it's very close.
In regards to all the RBF issues lately, would it not be more productive to push on the Bitcoin developers themselves to fix it? What's so bad about making no RBF actually mean NO RBF? You know, the first-seen spend transaction with NO-RBF/Opt-out-of-RBF flag is the only transaction that the network accepts and cannot be replaced/modified by any other means? It will either get mined into a block eventually, or in the case the fees are too low, sit in the mempool for an indefinite amount of time. Or does their say not even matter because the mining pools themselves would not adopt such a fix, given that it is actually not in their best interest to do so?
Just for those who want to know here are all my RAWTX for the RBF challenge from some days ago and the TXID or Error code returned from the mempool API:
You can decode RAWTX on: https://www.blockchain.com/explorer/assets/btc/decode-transaction
Just to check if something is odd or not.
Code:
Address 197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ found public key 029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583
Keyfound 000000000000000000000000000000000000000000000002357CAC24E9C2D41D for address 197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ
UXTO TXID:3ee3fa9738d6f3357966f2283c8cc9409bd24ec1033762b936152717977ce520 index 0 balance 492600
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 490104 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a473044022031f4cf9bf5a9dc03b7ee11e8f31c8d362f225b8a9db0c8ed9bce24a833d1301f02201417d3564599b67aeffd53818e004898b7f884ffc6000a691f1e9e232a4927120121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff01787a070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 7e91e4f33f6ead7ebb0d441e180a1ff0f66071b466ea3c6aab2ef9e36f4c98b3
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 5967ccefbaeee59a85c8f8689cd85684089a91a09b56b3a67d9e7845b237592c
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: sendrawtransaction RPC error: {"code":-26,"message":"txn-mempool-conflict"}
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 5967ccefbaeee59a85c8f8689cd85684089a91a09b56b3a67d9e7845b237592c
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488024 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006b483045022100b6daea5a333af8f3d52134f9b4cab6a59721fcd2a23538c5e29c55d23e21d64802202c7e5799d91ff7921cc6cc3de84bc710aa9e8c9c49841b30a30f3b7e5142e65b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff015872070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: sendrawtransaction RPC error: {"code":-26,"message":"txn-mempool-conflict"}
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 5967ccefbaeee59a85c8f8689cd85684089a91a09b56b3a67d9e7845b237592c; new feerate 0.00019914 BTC/kvB <= old feerate 0.00029872 BTC/kvB"}
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 5967ccefbaeee59a85c8f8689cd85684089a91a09b56b3a67d9e7845b237592c; new feerate 0.00019914 BTC/kvB <= old feerate 0.00044255 BTC/kvB"}
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 5967ccefbaeee59a85c8f8689cd85684089a91a09b56b3a67d9e7845b237592c; new feerate 0.00019914 BTC/kvB <= old feerate 0.00052825 BTC/kvB"}
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 480536 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006b4830450221009b36b01ae4710f13457428156736df8d1188e38caf0c0f4ef86ac052823da82d022077abf7b6c2fd28f1b86ecfbb5c7ae3fe452e48102dbae829d3343969c20b77e70121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff011855070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 699fb5b81c331abaa0fd11ed3f7c6b542cfbd180ccb0357d8d159663a7e96ca4
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 475128 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402202927628b704125bd1322d7293fb1a9c0fa203ba8e323f46fb195239e917d25ac0220623f9eeee892a4abd1671578c40ace03b34dd8797b45a635904d7182c11f74960121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff01f83f070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 23f023729eb3be2b4c1004bb1610043ecc1befb5b9223db7284c337ac06e9d64
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 488856 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a47304402200c97ff52a39e5a42907617847e979c89ff7d660f10862f8c9edd0d32e90fa17802200c74a1117890f4b8248ad0fa2a14d66e283b66732c2fd0e3a59d27d657bbb95b0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff019875070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID:429 Too Many Requests 429 Too Many Requests
Sign Up for Mempool Enterprise to get increased API limits
Output to bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 with 467224 satoshis, network bitcoin
Raw TX:
010000000120e57c9717271536b9623703c14ed29b40c98c3c28f2667935f3d63897fae33e000000006a473044022068357d38b55b987e139ce069de456cb399b04f37861879bb7e425ef84b11816a0220425c3fb1c6fa90ca1d7ab6971375a94d62e36a49041d7cfda338d51f4169a08e0121029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583ffffffff011821070000000000160014c0f3278346024832e71d25a24d5ae4b73885f85d00000000
TXID: 354dbcb6fd3532a051e1e363c9122d862949c3d075280d4144f719d6ba99e14a
You can decode RAWTX on: https://www.blockchain.com/explorer/assets/btc/decode-transaction
Just to check if something is odd or not.
I think that kangaroos that have been forked or modded from JLp's original kangaroo do not work. and I'm really asking about kangaroo running on 125 bit and above.
how do you know it doesn't work? in this last one there is no number 125 in the code. it's all 256...there is NO way to prove it doesn't work because it's impossible to solve puzzle 130.
So how do you know if it's working? Do you have proof?
Many people claim that they forked and modified the original JPL kangaroo 125-bit program and created new 256-bit kangaroo programs. So do these work? What happens if there is a code error? What if it was created incorrectly?
How would you feel if, after using it for months, someone told you that the program didn't really work?
Let me give an example: the keyhunt bsgs program definitely works.
So, is there anyone who has used the modded kangaroo program and can say this?
What you mean "works"?
How do YOU know keyhuntbsgs works?
Jump to: