Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Frequence]

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct way to withdraw

1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

             Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

Attackers are waiting for someone to send funds so they can use the exposed public key and reverse-engineer the private key. Since the key range is only 71 bits, it becomes easy for them to find the key within seconds.

Regarding Marapool, you can submit the transaction and it will be confirmed without appearing in the mempool. After 1–2 blocks, the transaction will be broadcasted. This method prevents anyone from seeing the public key in the hex.

[crytoestudo]

and kowalla/Bram disappeared in...does anyone know about him? he deleted his profile on X too.

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct way to withdraw

1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

             Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

Attackers are waiting for someone to send funds so they can use the exposed public key and reverse-engineer the private key. Since the key range is only 71 bits, it becomes easy for them to find the key within seconds.

Regarding Marapool, you can submit the transaction and it will be confirmed without appearing in the mempool. After 1–2 blocks, the transaction will be broadcasted. This method prevents anyone from seeing the public key in the hex.

[Frequence]

and kowalla/Bram disappeared in...does anyone know about him? he deleted his profile on X too.

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct way to withdraw

1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

             Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

Attackers are waiting for someone to send funds so they can use the exposed public key and reverse-engineer the private key. Since the key range is only 71 bits, it becomes easy for them to find the key within seconds.

Regarding Marapool, you can submit the transaction and it will be confirmed without appearing in the mempool. After 1–2 blocks, the transaction will be broadcasted. This method prevents anyone from seeing the public key in the hex.

Kowala is still active on X and last time told me...
"
..............
I would 100% work on 71 if it was profitable. But at current GPU prices and BTC price, sadly it’s not

"

[onepuzzle]

@bibilgin I don’t believe in your theory, but if you do, then prove it:

Code:

79EBD97F5EF1EF7B46
1PWo3JeB9jpsTbuCPumgqhpq5VRwKGyr5C
f6f5431d25bbf71badfcc241f76aca68cd6146ac

7A38AA4343C6130922
1PWo3JeB9k3NzZGpbMSkzsXYHVQxM8DSZi
f6f5431d25bbfc4ed9e2ce09a9fb6c0079cbb4b9

[bibilgin]

@bibilgin I don’t believe in your theory, but if you do, then prove it:

Code:

79EBD97F5EF1EF7B46
1PWo3JeB9jpsTbuCPumgqhpq5VRwKGyr5C
f6f5431d25bbf71badfcc241f76aca68cd6146ac

7A38AA4343C6130922
1PWo3JeB9k3NzZGpbMSkzsXYHVQxM8DSZi
f6f5431d25bbfc4ed9e2ce09a9fb6c0079cbb4b9

what exactly do you want me to prove?

Other 1PWo3JeB9j prefix calculation (jump)?
Or sister wallet wallet?
Or something else? Which one do you want?

[onepuzzle]

@bibilgin I don’t believe in your theory, but if you do, then prove it:

Code:

79EBD97F5EF1EF7B46
1PWo3JeB9jpsTbuCPumgqhpq5VRwKGyr5C
f6f5431d25bbf71badfcc241f76aca68cd6146ac

7A38AA4343C6130922
1PWo3JeB9k3NzZGpbMSkzsXYHVQxM8DSZi
f6f5431d25bbfc4ed9e2ce09a9fb6c0079cbb4b9

what exactly do you want me to prove?

Other 1PWo3JeB9j prefix calculation (jump)?
Or sister wallet wallet?
Or something else? Which one do you want?

How exactly do the prefixes help you solve the puzzle? Or which prefixes have you found?

[teguh54321]

@bibilgin I don’t believe in your theory, but if you do, then prove it:

Code:

79EBD97F5EF1EF7B46
1PWo3JeB9jpsTbuCPumgqhpq5VRwKGyr5C
f6f5431d25bbf71badfcc241f76aca68cd6146ac

7A38AA4343C6130922
1PWo3JeB9k3NzZGpbMSkzsXYHVQxM8DSZi
f6f5431d25bbfc4ed9e2ce09a9fb6c0079cbb4b9

what exactly do you want me to prove?

Other 1PWo3JeB9j prefix calculation (jump)?
Or sister wallet wallet?
Or something else? Which one do you want?

How exactly do the prefixes help you solve the puzzle? Or which prefixes have you found?

Mybe some idea is to skip brute /jump several keyspace range after match that prefix. But i dont know how efficient compare to standard brute ...

[mahmood1356]

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct way to withdraw

1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

              Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

In my opinion, no website should be used to send transactions at all. The best way to send a secure transaction is through the Electrum wallet, so the transaction won't be stolen and there's no need to worry about the delivery.

[nochkin]

In my opinion, no website should be used to send transactions at all. The best way to send a secure transaction is through the Electrum wallet, so the transaction won't be stolen and there's no need to worry about the delivery.

Electrum will use public pool to submit your transaction. And because it's public, everyone can see before it's confirmed and so everyone can steal if the private key uses low entropy like in this case.
And no, disabling RBF won't do anything at all.

This is why it's suggested to use private pool to submit your TX. It's not visible until mined/confirmed.

[mahmood1356]

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct way to withdraw

1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

             Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

I completely agree with you, and I don’t consider any website to be secure for sending transactions. In my opinion, those who insist on sending transactions through sites like Stream might even be the very same ones who are stealing the funds

How to safely withdraw BTC from puzzle wallets (71 included)

Hey everyone, since I’ve seen more interest lately around the puzzles and some people getting sniped, I thought I’d post a quick guide on how to do it right. Especially since puzzle 71 is very close to being found and it has over 7 BTC in it.

This method works for any puzzle where the private key is in a low range and you're able to recover it. If you just found the key and you're planning to import it in Electrum and click send... stop right now and read.

Why you shouldn't use the mempool

Once you broadcast a transaction to the public mempool (even with a high fee), the pubKey becomes visible. That means anyone monitoring the network can instantly start brute-forcing the private key and if the range is small (like puzzle 71), they'll find it in seconds. Even if you broadcast first, someone can RBF you with a higher fee and steal it.

It already happened with multiple puzzles. Some bots are running 24/7 and replacing transactions 50+ times until they win.

Correct


1. Generate a secure BTC address

Don’t send funds to an old or reused address. Use a new address from a wallet you control. Sparrow wallet is good, Electrum works too, or hardware wallet. Segwit is fine. Save the seed and verify it works.

2. Craft the transaction offline

Import the puzzle private key into an offline wallet or use command-line tools (bitcoin-tx or Sparrow in offline mode). Build a transaction that sends the funds to your new BTC address.

Set a high fee. I’d recommend something like 30k to 100k sats depending on size. If the TX is 300 vbytes, go with 300 sat/vB or more. Don’t cheap out on this, it’s less than $50 to secure over $700k worth of BTC.

Export the signed raw transaction as HEX. Do not broadcast it yet.

3. Use a miner relay (not public broadcast)

Now go to: https://slipstream.mara.com/

This is a private relay to the Marathon mining pool. Paste your signed TX hex and submit it. That way, your transaction goes directly to the miner and isn’t seen by the public mempool or sniping bots.

Once it’s mined, the BTC will be in your address. At that point, it’s too late for anyone to do anything the UTXO is already spent.

What if I don’t use slipstream?

Then your transaction will show up in the mempool, bots will see it, and if you’re not using RBF defense or an aggressive strategy, they can and will steal it. You’ll see your TX dropped and someone else’s version with a higher fee getting confirmed.

If you’re not 100% sure how to use slipstream or build a raw TX, ask before you risk it.

Puzzle 71 warning

We’re almost there. Someone will solve 71 soon, maybe already has. If you’re the one who gets the key, please don’t lose the funds by broadcasting it naively. Follow the steps above and you’ll be fine.

Happy hunting and stay safe.

             Dear  sir why do the attackers wait for someone to send transaction ? does sending on our wallet can show them what the hex for the address ? does the hex is shown on the mempool ? or what is the reason for using the spilstrem?  I mean if they have such capability why don't they scan by them selfs and take the funds ?

What you're saying makes no sense. Because if there were a bot that could access the private key of Puzzle 71 in just a few seconds by revealing its public key and steal the funds, then surely it could access the private key of Puzzle 135 in just a few minutes as well! And you're claiming this is due to the public key of Puzzle 135 being exposed? Your claim is completely baseless and biased. It seems your only intent is to deceive and mislead other users. If you really found a puzzle's private key, you can go ahead and use your own method to send your transaction—but don’t try to lay that trap for us again

[nochkin]

What you're saying makes no sense. Because if there were a bot that could access the private key of Puzzle 71 in just a few seconds by revealing its public key and steal the funds, then surely it could access the private key of Puzzle 135 in just a few minutes as well! And you're claiming this is due to the public key of Puzzle 135 being exposed? Your claim is completely baseless and biased. It seems your only intent is to deceive and mislead other users. If you really found a puzzle's private key, you can go ahead and use your own method to send your transaction—but don’t try to lay that trap for us again

I think you are missing the point on how big numbers work. Puzzle 135 is way-way-way bigger space to search through compared to 71.
It's not double, it's several quintillions more. No way you could find it in "a few minutes".

[mahmood1356]

What you're saying makes no sense. Because if there were a bot that could access the private key of Puzzle 71 in just a few seconds by revealing its public key and steal the funds, then surely it could access the private key of Puzzle 135 in just a few minutes as well! And you're claiming this is due to the public key of Puzzle 135 being exposed? Your claim is completely baseless and biased. It seems your only intent is to deceive and mislead other users. If you really found a puzzle's private key, you can go ahead and use your own method to send your transaction—but don’t try to lay that trap for us again

I think you are missing the point on how big numbers work. Puzzle 135 is way-way-way bigger space to search through compared to 71.
It's not double, it's several quintillions more. No way you could find it in "a few minutes".

I based my statements on what you yourself said. The keyspace of Puzzle 71 is not particularly small either, but according to your claim, bots are capable of accessing the private key in a very short time simply by having the public key. Now, considering that Puzzle 135 has a larger keyspace—which I acknowledge—with the speed you attribute to these bots, don’t you think there has been ample time since the creation of these puzzles for the private key of Puzzle 135 to be discovered and the funds to be transferred? It appears that some of these claims may be misleading. Could it be that you are the same individual who took the Puzzle 69 funds from the person who found it?

[nochkin]

I based my statements on what you yourself said. The keyspace of Puzzle 71 is not particularly small either, but according to your claim, bots are capable of accessing the private key in a very short time simply by having the public key. Now, considering that Puzzle 135 has a larger keyspace—which I acknowledge—with the speed you attribute to these bots, don’t you think there has been ample time since the creation of these puzzles for the private key of Puzzle 135 to be discovered and the funds to be transferred? It appears that some of these claims may be misleading. Could it be that you are the same individual who took the Puzzle 69 funds from the person who found it?

The keyspace of 71 is small enough to get the private key within short period of time.
But 135 is much larger space. No, I don't think there is enough time to get the private key of 135 within similar period of time.
Your claim about "there has been ample time since the creation of these puzzles for the private key of Puzzle 135 to be discovered" is incorrect.
It seems like you did not read my message above. Please do.

It does not matter if i'm the same individual or not. The space for 135 is significantly larger compared to 71. My individuality would not make it smaller.

[3dmlib]

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.
30 usd price.
Public key will be exposed tomorrow 27 June 2025 between 13.00 and 14.00 UTC.
Every participant BTC address which will be visible at least once in mempool RBF timeline will get 10 usd in BTC.

Thanks.

[bibilgin]

How exactly do the prefixes help you solve the puzzle? Or which prefixes have you found?

I have explained this topic before.
I have 252 1PWo3JeB9j prefixes.
I have a lot of wallets with 48+ bit matches. (over 3k +)

My wallets that are close to me;

1PWo3JeB9jrpyPqE6SjTbwjLYKxKYUoJp5
1PWo3JeB9jrUyFawqGsVdTfd1tTvQCrWGN
1PWo3JeB9jrSXEFRQRdQx8h8Zsz49raZr9

It helps me find prefixes similar to 1PWo3JeB9j with a few calculations and also helps with the sister wallet.

https://t.me/+JCW1umP2hN05MzQ0

You can join my group. I have decided not to correspond with anyone here on prefix or other issues.

[kTimesG]

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.

I don't understand what's the point of doing this.

I can solve your pubKey (or any other 75-bit public key for that matter) in at most 10 seconds from the moment it's grabbed from the mempool initial TX.

[E36cat]

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.

I don't understand what's the point of doing this.

I can solve your pubKey (or any other 75-bit public key for that matter) in at most 10 seconds from the moment it's grabbed from the mempool initial TX.

he wants to test if his bot is faster than other bots i guess

[andrzejalatkows]

great!

[3dmlib]

he wants to test if his bot is faster than other bots i guess

Exactly.
Other participants also can do it.
And this is free for them, instead of me.

[Akito S. M. Hosana]

I can solve your pubKey (or any other 75-bit public key for that matter) in at most 10 seconds from the moment it's grabbed from the mempool initial TX.

And the Philosopher, Alberto and Nomachine, they just remain quiet on the topic of bots. Even though they were the first here to discuss it.