ccinet
Jr. Member
Offline
Activity: 44
Merit: 1
|
 |
March 20, 2024, 04:08:10 PM |
|
Let's assume the mempool is low when you do the transaction for the puzzle. If I send the coins with a fee of .1BTC and someone else finds the private key 30 seconds later and sends the transaction with a 1BTC fee, would they both be in the same block and the first transaction would win because it has an earlier timestamp, or would that not matter?
Double spending in Bitcoin is an inevitable feature of the network, regardless of whether it is legitimate or not. So how do you solve the problem of a conflicting transaction? well, through the confirmations of the miners. And how can we "win" a conflicting transaction? increasing the rate... In fact, exchanges usually carry out these transactions to reverse a transaction in which the transaction fee was low and they need to make the transaction faster or even unblock a stuck transaction generating a double spend this time with a higher fee. So this is part of the bitcoin protocol and there is nothing to do. If someone obtains your private address and makes a transaction before it is confirmed, both transactions will "fight" to form a block first, regardless of which was issued first. It turns out you need to win the lottery 2 times)) first win the private key and then also so that your transaction is included in the block. But what if you choose a moment when the network is overloaded and make a transaction with a commission of 100 million sat? Will this increase the chances or does it not matter? Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
|
|
|
|
pbies
|
 |
March 20, 2024, 04:15:35 PM |
|
Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
That is the problem with miners which do not acknowledge that RBF is off for a tx. If tx is with RBF off it should be treated as last and valid only.
|
BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
|
|
|
brainless
Member

Online
Activity: 370
Merit: 35
|
 |
March 20, 2024, 04:23:36 PM |
|
Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
That is the problem with miners which do not acknowledge that RBF is off for a tx. If tx is with RBF off it should be treated as last and valid only. There is 3 sanario Without rbf, any one can load Pk and cancel tx ormodify With rbf, any one can load Pk and generate new tx with higher fee 3rd and last I know how to create tx and relax for sure where coin will move to my assign address
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
WanderingPhilospher
Sr. Member
  
Offline
Activity: 1288
Merit: 253
Shooters Shoot...
|
 |
March 20, 2024, 04:32:56 PM |
|
Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
That is the problem with miners which do not acknowledge that RBF is off for a tx. If tx is with RBF off it should be treated as last and valid only. There is 3 sanario Without rbf, any one can load Pk and cancel tx ormodify With rbf, any one can load Pk and generate new tx with higher fee 3rd and last I know how to create tx and relax for sure where coin will move to my assign address lol. Ok brainless swooping in. Why not just tell people how to do it? No one knows you, so sending private key to you is as just a chance as any other way. Maybe those who find it will send you a nice chunk of change for helping out. I know I would.
|
|
|
|
brainless
Member

Online
Activity: 370
Merit: 35
|
 |
March 20, 2024, 05:08:15 PM |
|
Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
That is the problem with miners which do not acknowledge that RBF is off for a tx. If tx is with RBF off it should be treated as last and valid only. There is 3 sanario Without rbf, any one can load Pk and cancel tx ormodify With rbf, any one can load Pk and generate new tx with higher fee 3rd and last I know how to create tx and relax for sure where coin will move to my assign address lol. Ok brainless swooping in. Why not just tell people how to do it? No one knows you, so sending private key to you is as just a chance as any other way. Maybe those who find it will send you a nice chunk of change for helping out. I know I would. Ahhh, I did not ask send me Pk, within last 2 days I post 2 or 3 message where my statement is, as discussed above issue , I explain what will happen in didrent ways of attempt for withdrawal, and said try your tx create n check what me and similar other said, when get knowledge our explained ( hand on practice), then come to me ask, I will definitely explain, how to do safe n secure, I never ask share your found 66 Pk to me, yes I ask hope u will share coins to me 
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
albert0bsd
|
 |
March 20, 2024, 05:51:45 PM |
|
3rd and last I know how to create tx and relax for sure where coin will move to my assign address
THB this sound like a bait and bullshit, unless you are a miner or have some accesses to miner resources in somehow. Besides that there is not an other method to do that. I been collecting some dust inputs from leaked private keys and that's actually very difficult to do because other are doing exactly the same with those address... so there is no safe way to move an address with leaked private key with 100% of certainty to win that transaction.
|
|
|
|
WanderingPhilospher
Sr. Member
  
Offline
Activity: 1288
Merit: 253
Shooters Shoot...
|
 |
March 20, 2024, 06:57:32 PM |
|
Why win the lottery twice? This is precisely the problem we are dealing with, this is ONLY for low bit puzzles like 66. A bot that is sniffing mempool transactions (transactions that have not yet been placed on the blockchain and are stored in volatile memory) gets the public key and in minutes the private key with kangaroo, then initiates a transaction with a commission larger, which has a better chance of obtaining confirmations than the "original" transaction
That is the problem with miners which do not acknowledge that RBF is off for a tx. If tx is with RBF off it should be treated as last and valid only. There is 3 sanario Without rbf, any one can load Pk and cancel tx ormodify With rbf, any one can load Pk and generate new tx with higher fee 3rd and last I know how to create tx and relax for sure where coin will move to my assign address lol. Ok brainless swooping in. Why not just tell people how to do it? No one knows you, so sending private key to you is as just a chance as any other way. Maybe those who find it will send you a nice chunk of change for helping out. I know I would. Ahhh, I did not ask send me Pk, within last 2 days I post 2 or 3 message where my statement is, as discussed above issue , I explain what will happen in didrent ways of attempt for withdrawal, and said try your tx create n check what me and similar other said, when get knowledge our explained ( hand on practice), then come to me ask, I will definitely explain, how to do safe n secure, I never ask share your found 66 Pk to me, yes I ask hope u will share coins to me  Ok, you said if someone has 66 pk to share with you. Maybe it meant something else.
|
|
|
|
3dmlib
Jr. Member
Offline
Activity: 45
Merit: 2
|
 |
March 20, 2024, 07:23:37 PM Last edit: March 20, 2024, 07:41:00 PM by 3dmlib |
|
Just found the way how to do it... So, we're definitely f....d...  66 puzzle is waste of electricity now. Thanks.
|
|
|
|
nomachine
Member

Offline
Activity: 511
Merit: 38
|
 |
March 20, 2024, 07:39:09 PM Last edit: March 20, 2024, 07:52:37 PM by nomachine |
|
I did about 10 attempts today, trying to change already broadcasted transaction, sent from bitcoin-core with RBF flag off. All attempts fail. First transaction always win.
Then we must do kind of kung-fu. Using older Electrum versions than 4.4.0 with RBF flag off. 
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
zahid888
Member

Offline
Activity: 287
Merit: 21
the right steps towerds the goal
|
 |
March 21, 2024, 12:41:40 AM |
|
I did about 10 attempts today, trying to change already broadcasted transaction, sent from bitcoin-core with RBF flag off. All attempts fail. First transaction always win.
Then we must do kind of kung-fu. Using older Electrum versions than 4.4.0 with RBF flag off.  I already installed and ready to finalize.. needs only 1 more thing  
|
1BGvwggxfCaHGykKrVXX7fk8GYaLQpeixA
|
|
|
mcdouglasx
|
 |
March 21, 2024, 03:05:29 AM |
|
I did about 10 attempts today, trying to change already broadcasted transaction, sent from bitcoin-core with RBF flag off. All attempts fail. First transaction always win.
Then we must do kind of kung-fu. Using older Electrum versions than 4.4.0 with RBF flag off.  I already installed and ready to finalize.. needs only 1 more thing   The problem lies in the rbf according to the configuration of each node, I think that if you do a tx deactivating rbf it must be replaced using another node to be able to replace it.
|
|
|
|
brainless
Member

Online
Activity: 370
Merit: 35
|
 |
March 21, 2024, 06:24:52 AM |
|
I did about 10 attempts today, trying to change already broadcasted transaction, sent from bitcoin-core with RBF flag off. All attempts fail. First transaction always win.
Then we must do kind of kung-fu. Using older Electrum versions than 4.4.0 with RBF flag off.  Have u apply cancel tx, before new tx with rbf ?
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
citb0in
|
 |
March 21, 2024, 07:10:00 AM |
|
You people just don't want to understand. It doesn't matter which program you use to generate the transaction and it doesn't matter whether you have signaled RBF or not.
Every transaction is replaceable if you have knowledge of the private key. Whether you want to admit it or not, that's a fact.
|
_ _ _ __ _ _ _ __ |_) | / \ / |/ (_ / \ | \ / |_ |_) (_ |_) |_ \_/ \_ |\ __) \_/ |_ \/ |_ | \ __) --> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
|
|
|
pbies
|
 |
March 21, 2024, 07:33:58 AM |
|
...
Every transaction is replaceable if you have knowledge of the private key.
...
So anyone could do millions any time. Good luck with that thinking.
|
BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
|
|
|
nomachine
Member

Offline
Activity: 511
Merit: 38
|
 |
March 21, 2024, 10:06:44 AM |
|
So anyone could do millions any time.
It seems so. From Puzzle 66 to 79... It's a waste of electricity to brute force. However, you can wait for someone else to do it and then pick up the money  Maybe Satoshi was just waiting for us to come to this conclusion.
|
bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
brainless
Member

Online
Activity: 370
Merit: 35
|
 |
March 21, 2024, 12:09:49 PM |
|
So anyone could do millions any time.
It seems so. From Puzzle 66 to 79... It's a waste of electricity to brute force. However, you can wait for someone else to do it and then pick up the money  Maybe Satoshi was just waiting for us to come to this conclusion. Raiz you hand, who have 66 Pk ?
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
dextronomous
|
 |
March 21, 2024, 03:45:44 PM |
|
UNSPENTS height: 339085 tx_hash: 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 tx_pos: 65 value: 6600000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 496585 height: 475240 tx_hash: 5d45587cfd1d5b0fb826805541da7d94c61fe432259e68ee26f4a04544384164 tx_pos: 14 value: 59400000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 360430 height: 581637 tx_hash: c725a765997cf82ca4a40cb2166f9ed2c2677e9ad9446112dd94920db7034a07 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254033 height: 581641 tx_hash: 9623ca8da4f10db5ca90a0673674571a3150e568cb82c2e2ad6ca55af77a67f9 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254029 height: 601832 tx_hash: ab571acb61ec96a4759da551ae37a1fe5accbd353dfca3e1a57cb254e5e0e790 tx_pos: 1 value: 666 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 233838 height: 666538 tx_hash: 33ea377a3c0aa2e10f498a41f746d7489e06bf9b6e45b406b817ee96e4cec96b tx_pos: 1 value: 1950 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 169132 height: 755590 tx_hash: 4461b388764735edf0b8b35456846c251dc7e281a8837df42f684b4bfce91f72 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 80080 height: 759213 tx_hash: c1a490e56f7faea9c064fd30023647780d5b3fa330cd7ec10c60c513c3f36813 tx_pos: 0 value: 1533 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 76457 height: 761116 tx_hash: 1602e46f048a7466db2f630f74e6f83a6e72fb2726067ac719c7de3ab784689c tx_pos: 0 value: 600 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 74554 height: 763866 tx_hash: 3615aa6fc46e190a9d542844172a105191c902402ff753c96f6bd591ea2aecad tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 71804 height: 777889 tx_hash: acdf413e69ab69a2628e50225096f14fab57483b1d908387e00d593d56abe425 tx_pos: 0 value: 908 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 57781 height: 778883 tx_hash: 7cce2dde07daaa77a0c2159ae079cf56a1b9ca8196c0b122666d3d40d5314e22 tx_pos: 1 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 56787 height: 785620 tx_hash: 12f34b58b04dfb0233ce889f674781c0e0c7ba95482cca469125af41a78d13b3 tx_pos: 1 value: 594000000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 50050 height: 831116 tx_hash: 6a76cd295c5fe4037511c2e5c2945b99aa52e2fd41d014943c0a975e08a5ce17 tx_pos: 0 value: 6700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 4554 height: 834413 tx_hash: 8da7b3599f9fec422ace5d290443c17f685d6e45ce89ca1ee0a334b711f10745 tx_pos: 0 value: 660 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1257 height: 834609 tx_hash: 8cc982de6db7539fa665840ff774d69807a9d85c01e17620205da67de995ea29 tx_pos: 0 value: 1277 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1061 height: 835645 tx_hash: cff6de5c21176e8cb9d60fcf1e2a2d9a44b9267860126cfddee5d7fa39ab27e1 tx_pos: 0 value: 6018 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 25 height: 0 tx_hash: d7d518a01522f0ac26dddf0595265c9acbfc52361e1e5c7da2c17fd930a5d0c3 tx_pos: 0 value: 616 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0 height: 0 tx_hash: d76dccf84fde447a3fd11d50d70ae7e187ede0e8829f99b39a420962795b7ad2 tx_pos: 0 value: 4700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0 height: 0 tx_hash: 55571ca5e1f86c11a5ec5837aa1edf4262042b4b18379373585047ce8f8938cf tx_pos: 61 value: 546 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0
Confirmed Balance: 660050868 Unconfirmed Balance: 5862
This address was found in 26 transactions and has 26 unspents. guessing no one yet or 26 people
|
|
|
|
brainless
Member

Online
Activity: 370
Merit: 35
|
 |
March 21, 2024, 04:17:40 PM |
|
UNSPENTS height: 339085 tx_hash: 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 tx_pos: 65 value: 6600000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 496585 height: 475240 tx_hash: 5d45587cfd1d5b0fb826805541da7d94c61fe432259e68ee26f4a04544384164 tx_pos: 14 value: 59400000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 360430 height: 581637 tx_hash: c725a765997cf82ca4a40cb2166f9ed2c2677e9ad9446112dd94920db7034a07 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254033 height: 581641 tx_hash: 9623ca8da4f10db5ca90a0673674571a3150e568cb82c2e2ad6ca55af77a67f9 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254029 height: 601832 tx_hash: ab571acb61ec96a4759da551ae37a1fe5accbd353dfca3e1a57cb254e5e0e790 tx_pos: 1 value: 666 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 233838 height: 666538 tx_hash: 33ea377a3c0aa2e10f498a41f746d7489e06bf9b6e45b406b817ee96e4cec96b tx_pos: 1 value: 1950 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 169132 height: 755590 tx_hash: 4461b388764735edf0b8b35456846c251dc7e281a8837df42f684b4bfce91f72 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 80080 height: 759213 tx_hash: c1a490e56f7faea9c064fd30023647780d5b3fa330cd7ec10c60c513c3f36813 tx_pos: 0 value: 1533 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 76457 height: 761116 tx_hash: 1602e46f048a7466db2f630f74e6f83a6e72fb2726067ac719c7de3ab784689c tx_pos: 0 value: 600 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 74554 height: 763866 tx_hash: 3615aa6fc46e190a9d542844172a105191c902402ff753c96f6bd591ea2aecad tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 71804 height: 777889 tx_hash: acdf413e69ab69a2628e50225096f14fab57483b1d908387e00d593d56abe425 tx_pos: 0 value: 908 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 57781 height: 778883 tx_hash: 7cce2dde07daaa77a0c2159ae079cf56a1b9ca8196c0b122666d3d40d5314e22 tx_pos: 1 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 56787 height: 785620 tx_hash: 12f34b58b04dfb0233ce889f674781c0e0c7ba95482cca469125af41a78d13b3 tx_pos: 1 value: 594000000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 50050 height: 831116 tx_hash: 6a76cd295c5fe4037511c2e5c2945b99aa52e2fd41d014943c0a975e08a5ce17 tx_pos: 0 value: 6700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 4554 height: 834413 tx_hash: 8da7b3599f9fec422ace5d290443c17f685d6e45ce89ca1ee0a334b711f10745 tx_pos: 0 value: 660 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1257 height: 834609 tx_hash: 8cc982de6db7539fa665840ff774d69807a9d85c01e17620205da67de995ea29 tx_pos: 0 value: 1277 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1061 height: 835645 tx_hash: cff6de5c21176e8cb9d60fcf1e2a2d9a44b9267860126cfddee5d7fa39ab27e1 tx_pos: 0 value: 6018 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 25 height: 0 tx_hash: d7d518a01522f0ac26dddf0595265c9acbfc52361e1e5c7da2c17fd930a5d0c3 tx_pos: 0 value: 616 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0 height: 0 tx_hash: d76dccf84fde447a3fd11d50d70ae7e187ede0e8829f99b39a420962795b7ad2 tx_pos: 0 value: 4700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0 height: 0 tx_hash: 55571ca5e1f86c11a5ec5837aa1edf4262042b4b18379373585047ce8f8938cf tx_pos: 61 value: 546 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0
Confirmed Balance: 660050868 Unconfirmed Balance: 5862
This address was found in 26 transactions and has 26 unspents. guessing no one yet or 26 people
It's 26 input, still not spent
|
13sXkWqtivcMtNGQpskD78iqsgVy9hcHLF
|
|
|
jacky19790729
Jr. Member
Offline
Activity: 82
Merit: 8
|
 |
March 21, 2024, 05:48:20 PM Last edit: March 21, 2024, 06:05:01 PM by jacky19790729 Merited by Garmo (3), albert0bsd (1) |
|
  private key: 0000000000000000000000000000000000000000000000000000000000000001 address: bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 double spend 0.001 BTC from bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 Transaction ID: 93aeb9bd3eeaa46f68ddd0051a3e617002aef782343fcb9b2824dec676c3df2b (Date: 2024/3/22 01:01) ( Transaction fee: -0.00020000 BTC ) Transaction ID: 6d04e973062c4993dc0eaff2142639dd6d29e1165b6bb494b86ea04f5b0bc132 (Date: 2024/3/22 01:08) ( Transaction fee: -0.00098650 BTC ) The one who broadcast earlier loses , but higher fees win
|
|
|
|
Baskentliia
Jr. Member
Offline
Activity: 69
Merit: 1
34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ
|
 |
March 21, 2024, 07:17:43 PM |
|
Is JLP's Kangaroo program used for puzzle 130, which is original and published on github? Yes or no ?
Some said you can use it because the range width is 125 bits. Some have said that the original version of JLP has 130 puzzles and you cannot use it for more comprehensive puzzles.
Which one is right ?
|
34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ
|
|
|
|