All BTC in mempool can be stolen

[pbies]

As it works for Bitcoin puzzle 1-160 with bsgs, it should also work for all BTC that are in mempool and public keys have been revealed.

It is simple as that.

Only the space is big - from 1 to nearly 2^256.

I invite you to discuss this idea.

[LoyceV]

Only the space is big - from 1 to nearly 2^256.

That's a very big "Only"....

[swogerino]

I want to reply with the complete number of 2 at the power of 256 but that would take quite some forum pages space and how would you possibly steal from such a huge number, the probability to get it right it is negative, less than 0 and that is why the Bitcoin algorithm is one of the strongest. We also have ready made post quantum computers cryptography algorithms and encryption so I wish you luck in your idea and let us know when you will be successful in the year 2140 after all of the Bitcoin has been mined, maybe up until then your theory can hold up and prove itself true  .

[tbct_mt2]

As it works for Bitcoin puzzle 1-160 with bsgs, it should also work for all BTC that are in mempool and public keys have been revealed.

It is simple as that.

Only the space is big - from 1 to nearly 2^256.

It's not simple.

You lost your bitcoin if you lost your private key.

Private keys can not be brute forced.

The range of 256-bit numbers (and therefore the number of possible private keys) is unfathomably large. Just as it's impossible for the human mind to visualize the true scale of the universe, it's impossible for the human mind to comprehend the sheer size of 256-bit numbers.

So if you have any doubts about the safety of your 256-bit number, it's either because you didn't use a reliable enough random number generator, or because you don't appreciate the magnitude of the numbers we are dealing with.

[pooya87]

As it works for Bitcoin puzzle 1-160 with bsgs, it should also work for all BTC that are in mempool and public keys have been revealed.

I have a number in my head, it is between 1 and 5. I'll give you 5 tries to guess that number. Did you get it right? Cool.
Now I have a number between 1 and 1000000 and I'll give you 5 tries to guess it. Did you get it right? No? huh.
Now I have a number between 1 and 115792089237316195423570985008687907852837564279074904382605163141518161494337 and I'll give you billions of guesses. Did you get it right? No. You can't because you aren't fast enough in guessing numbers before the universe ends. And that's what the bitcoin private key range is.

That's exactly what the puzzle is proving as well. You can spend lots of computing power, even pool the work with others and by aggregating your computing powers be able to go through a much larger number of keys but it still is not enough to break a key that is in a much smaller range, as it is evident from how increasingly difficult it is getting to break the subsequent keys in that puzzle. It is impossible to break the 2²⁵⁶ range.

[pbies]

Then why bsgs worked for some of the bitcoin puzzles?

It really did. So there is way to come back from hash to original data, knowing the range.

[pooya87]

Then why bsgs worked for some of the bitcoin puzzles?

Because they are in a much smaller range (between 2⁰ and 2¹ then between 2¹ and 2² and so on) which significantly decreases the number of keys to check (as opposed to being between 2⁰ and 2²⁵⁶) making the time short enough to become possible to break.

So there is way to come back from hash to original data, knowing the range.

Do you mean public key? No, hashes are irreversible meaning you can not compute the public key from its hash. Knowing the range of the key does not give any kind of advantage on that either, because the hash is still irreversible.

[iceland2k14]

Then why bsgs worked for some of the bitcoin puzzles?

It really did. So there is way to come back from hash to original data, knowing the range.

Also remember the bsgs or Kangaroo approach are based on public key using the point mathematics utilizing the birthday paradox for solving it faster. But that's also a limiting factor that it can only be applied to 1 public key at a time. Not for all of them together.

[betswift]

Only the space is big - from 1 to nearly 2^256.

That's a very big "Only"....

The biggest, actually.
Even with talks about quantum stuff that would be able to work around such tasks - it will be in the times when there are probably counter-measures to it. And for it to work, it should become mainstreamed for everybody, which is clearly not the reality we are in, it would be hella expensive and not be targeted at BTC first and foremost.

[bitbollo]

...
 You can spend lots of computing power, even pool the work with others and by aggregating your computing powers be able to go through a much larger number of keys but it still is not enough to break a key that is in a much smaller range, as it is evident from how increasingly difficult it is getting to break the subsequent keys in that puzzle. It is impossible to break the 2²⁵⁶ range.

This experiment will become also useless and a kind of disaster since you will just spend tons of useful resources and not directly mining and supporting the network!
Meanwhile you're trying to get some coins... it will be more safe and sure spend all this effort in just find the next block.

I call this as "the tale malevolent operator". Some one is tricky you to find a key (or to spend resources in a "new bitcoin").
You are spending tons of effort without any guarantee of results. Even if you get a key that has been used, are you still sure you will find a balance ?
 

[OgNasty]

"All BTC in mempool can be stolen"

The only way this statement makes sense to me is if it is perhaps a language barrier thing and OP is talking about double spends.  I don't think that's actually what is happening, but I thought I'd throw it out there.  The only time I've ever seen BTC get "stolen" from the mempool is during periods of expensive fees when someone does a double spend.  I could see someone on the receiving end of the original transaction feeling like their BTC was "stolen" from the mempool in that circumstance...

[hd49728]

As it works for Bitcoin puzzle 1-160 with bsgs, it should also work for all BTC that are in mempool and public keys have been revealed.

It is simple as that.

Only the space is big - from 1 to nearly 2^256.

I invite you to discuss this idea.

If anyone want to steal your bitcoin, they need to have private key of your bitcoin. Having public address or public key can not help them stealing your bitcoin.

When you broadcast your transaction to Bitcoin mempools, it will be there before it get a confirmation by Bitcoin miners. Most popularly Bitcoin mempools have their common configurations on their nodes to drop off waiting Bitcoin transactions with too low fee rates after 14 days, but surely there are nodes and mempools that don't drop too-low-fee-rate tranasactions after 14 days. It depends on their configurations, you can not know, but they can not steal your bitcoin.

How long will a Bitcoin transaction stuck in the mempool for two months be deleted
https://jlopp.github.io/bitcoin-core-config-generator/

[pbies]

As it works for Bitcoin puzzle 1-160 with bsgs, it should also work for all BTC that are in mempool and public keys have been revealed.

It is simple as that.

Only the space is big - from 1 to nearly 2^256.

I invite you to discuss this idea.

If anyone want to steal your bitcoin, they need to have private key of your bitcoin. Having public address or public key can not help them stealing your bitcoin.

When you broadcast your transaction to Bitcoin mempools, it will be there before it get a confirmation by Bitcoin miners. Most popularly Bitcoin mempools have their common configurations on their nodes to drop off waiting Bitcoin transactions with too low fee rates after 14 days, but surely there are nodes and mempools that don't drop too-low-fee-rate tranasactions after 14 days. It depends on their configurations, you can not know, but they can not steal your bitcoin.

How long will a Bitcoin transaction stuck in the mempool for two months be deleted
https://jlopp.github.io/bitcoin-core-config-generator/

Actually public key helps moving the balance (BSGS method), which was proved in bitcoin puzzle search. For any random private key with balance this only changes the range which private key is in.