Bitcoin puzzle transaction ~32 BTC prize to who solves it

[JDScreesh]

Well, I successfully beat any bots that were still in the game.

However, I will admit my first plan did not go as planned because I messed a few things up. But that's ok, I learned from it.

My successful withdrawal, was more of a hail mary versus my thought out, crafted, plan.

I am curious if any bots did get the signal and start working on finding the key and changing the transaction.

I will run another test from learning a few things, and after that test (not 66 bit), I hope to run another one here. Maybe even a lower bit one. We shall see.

Thanks for all of those who built bots and was in the game. I appreciate you.

Hello there 

That was a nice test. It confirmed fast and my bot was confused  It took the pubkey of 1BoTWARSmLQSouDixHvKpLv6J5LgJYtrCy instead the right one.

Thanks for the opportunity  WanderingPhilospher 

[WanderingPhilospher]

Well, I successfully beat any bots that were still in the game.

However, I will admit my first plan did not go as planned because I messed a few things up. But that's ok, I learned from it.

My successful withdrawal, was more of a hail mary versus my thought out, crafted, plan.

I am curious if any bots did get the signal and start working on finding the key and changing the transaction.

I will run another test from learning a few things, and after that test (not 66 bit), I hope to run another one here. Maybe even a lower bit one. We shall see.

Thanks for all of those who built bots and was in the game. I appreciate you.

Hello there  

That was a nice test. It confirmed fast and my bot was confused   It took the pubkey of 1BoTWARSmLQSouDixHvKpLv6J5LgJYtrCy instead the right one.

Thanks for the opportunity  WanderingPhilospher  

Should have gone better, on my end, but I learned. Thanks for the info, I truly appreciate it.

This was interesting. I also learn somethings

By way, how many replacements did you do?

Thanks you!!

I didn't do any replacements nor have any bots running. Like I said, a hail mary of sorts because I messed up the first plan lol.

So what do you think happened? If you were able to find key and replace trans, I'm a little confused as well. Thank you for helping me hone my skills lol.

Also albert0, why was your trans fee still lower than my original. You said it was increased 3 times but still was lower than my one and only fee, correct?

[albert0bsd]

Also albert0, why was your trans fee still lower than my original. You said it was increased 3 times but still was lower than my one and only fee, correct?

My fee was higher than yours, but it wasn't mined, your final output was 438K satoshis, my final output was 297K satoshis, so in my case more than half of the balance would be burned in fees...

My TX were accepted by mempool but not mined. So it was just luck from the miner (That is outside of our control).

By the way why you didn't have any bot?

[WanderingPhilospher]

Also albert0, why was your trans fee still lower than my original. You said it was increased 3 times but still was lower than my one and only fee, correct?

My fee was higher than yours, but it wasn't mined, your final output was 438K satoshis, my final output was 297K satoshis, so in my case more than half of the balance would be burned in fees...

My TX were accepted by mempool but not mined. So it was just luck from the miner (That is outside of our control).

By the way why you didn't have any bot?

So you had a higher final bump?

You say mine was 438k and your final was 297k, so mine was higher than yours, or am I misunderstanding something?  Ahhhh, you are saying that is the final amount you would have received, not the trans fee. Gotcha!

I don't have a bot. I dunno, just don't.

Did you happen to capture how many RBFs were submitted/accepted into the pool?

I am confused if you had to bump 3 times, who were you competing with? Or is yours set at a small default level and goes up every so many seconds when it sees it is not the highest trans fee?

[albert0bsd]

Did you happen to capture how many RBFs were submitted/accepted into the pool?

I am confused if you had to bump 3 times, who were you competing with? Or is yours set at a small default level and goes up every so many seconds when it sees it is not the highest trans fee?

This is the last Other transactions that i see:

Code:

01000000029e8c8c0f85d43b8d6aa7d41a0d6f45d67c0f003a4285f3046bf8413b14cf5578010000006a473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff11d5fc65af501e48a895128fa73cca27fc740e005af8bf47a4eb389ebda34aca030000006b483045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe080121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff01668b0400000000001600146866ea020efa70acd43caee975a4bbddabb67cb700000000

Code:

{
  "version": 1,
  "locktime": 0,
  "ins": [
    {
      "n": 1,
      "script": {
        "asm": "3044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a801 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90",
        "hex": "473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90"
      },
      "sequence": 4294967295,
      "txid": "7855cf143b41f86b04f385423a000f7cd6456f0d1ad4a76a8d3bd4850f8c8c9e",
      "witness": []
    },
    {
      "n": 3,
      "script": {
        "asm": "3045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe0801 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90",
        "hex": "483045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe080121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90"
      },
      "sequence": 4294967295,
      "txid": "ca4aa3bd9e38eba447bff85a000e74fc27ca3ca78f1295a8481e50af65fcd511",
      "witness": []
    }
  ],
  "outs": [
    {
      "n": 0,
      "script": {
        "addresses": [
          "bc1qdpnw5qswlfc2e4pu4m5htf9mmk4mvl9hd527sg"
        ],
        "asm": "OP_0 6866ea020efa70acd43caee975a4bbddabb67cb7",
        "hex": "00146866ea020efa70acd43caee975a4bbddabb67cb7"
      },
      "value": 297830
    }
  ],
  "hash": "3910224758c9b64bf83a724da28a102fbe2b50b33fc6081f068dd4021fbe5933",
  "txid": "3910224758c9b64bf83a724da28a102fbe2b50b33fc6081f068dd4021fbe5933"
}

As you see that output was 297830, so I decrement my output to 292846 near 5K satoshis less.

against who? I don't know.

My bot only increment the fee if it detect a higher fee, different from my last transaction.

Did you happen to capture how many RBFs were submitted/accepted into the pool?

My program only capture what the API return, the API only returns One TX (higher fee), so if there are other transactions that my program didn't see, then i don't have log of them

[WanderingPhilospher]

Did you happen to capture how many RBFs were submitted/accepted into the pool?

I am confused if you had to bump 3 times, who were you competing with? Or is yours set at a small default level and goes up every so many seconds when it sees it is not the highest trans fee?

This is the last Other transactions that i see:

Code:

01000000029e8c8c0f85d43b8d6aa7d41a0d6f45d67c0f003a4285f3046bf8413b14cf5578010000006a473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff11d5fc65af501e48a895128fa73cca27fc740e005af8bf47a4eb389ebda34aca030000006b483045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe080121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff01668b0400000000001600146866ea020efa70acd43caee975a4bbddabb67cb700000000

Code:

{
  "version": 1,
  "locktime": 0,
  "ins": [
    {
      "n": 1,
      "script": {
        "asm": "3044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a801 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90",
        "hex": "473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f78302200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90"
      },
      "sequence": 4294967295,
      "txid": "7855cf143b41f86b04f385423a000f7cd6456f0d1ad4a76a8d3bd4850f8c8c9e",
      "witness": []
    },
    {
      "n": 3,
      "script": {
        "asm": "3045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe0801 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90",
        "hex": "483045022100c495e3eb2f7378925390f038174f7aeb144b02a6972b7e546b539745c90e20fd022034a7aab341552162d3a3768c282a1668b8029a0d73a6b81064b78ebed98ffe080121029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90"
      },
      "sequence": 4294967295,
      "txid": "ca4aa3bd9e38eba447bff85a000e74fc27ca3ca78f1295a8481e50af65fcd511",
      "witness": []
    }
  ],
  "outs": [
    {
      "n": 0,
      "script": {
        "addresses": [
          "bc1qdpnw5qswlfc2e4pu4m5htf9mmk4mvl9hd527sg"
        ],
        "asm": "OP_0 6866ea020efa70acd43caee975a4bbddabb67cb7",
        "hex": "00146866ea020efa70acd43caee975a4bbddabb67cb7"
      },
      "value": 297830
    }
  ],
  "hash": "3910224758c9b64bf83a724da28a102fbe2b50b33fc6081f068dd4021fbe5933",
  "txid": "3910224758c9b64bf83a724da28a102fbe2b50b33fc6081f068dd4021fbe5933"
}

As you see that output was 297830, so I decrement my output to 292846 near 5K satoshis less.

against who? I don't know.

My bot only increment the fee if it detect a higher fee, different from my last transaction.

Awesome. I'm glad you captured those. It's interesting to see. So that means at least 2 other bots were able to put in bump fees, if you had to put in 3. Interesting.

What did you mean by this:

If you see mempool.space didn't see your mined TX before it was mined.

[albert0bsd]

What did you mean by this:

If you see mempool.space didn't see your mined TX before it was mined.

Never mind, I don't know what is happening with the mempool.space page because

My script works with that API (mempool.space), my script actually was trigger by your Transaction to start to work. (I checked it after post that message).

But if you see in the image that i post before:



The label was: "Not seen in Mempool"

But if you check that page right now  ( https://mempool.space/tx/bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 )



Now the label change to: "Expected in Block"

So the page chage that label and i was confused by that.

[JDScreesh]

What did you mean by this:

If you see mempool.space didn't see your mined TX before it was mined.

Never mind, I don't know what is happening with the mempool.space page because

My script works with that API (mempool.space), my script actually was trigger by your Transaction to start to work. (I checked it after post that message).

But if you see in the image that i post before:



The label was: "Not seen in Mempool"

But if you check that page right now  ( https://mempool.space/tx/bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 )



Now the label change to: "Expected in Block"

So the page chage that label and i was confused by that.

Hey albert0bsd 

I just check the page right now and it still show me the message "Not seen in Mempool"



Greetings.

[nomachine]

Here is my log

INFO:root:Running scan...
INFO:root:Running scan...
INFO:root:Extracted Public Key: 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90
INFO:root:Running command: echo '029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90 20000000000000000:3ffffffffffffffff' | nc -v localhost 8080
INFO:root:Keyhunt stdout: 29c8156de964053a9
ERROR:root:Keyhunt stderr: Connection to localhost (127.0.0.1) 8080 port [tcp/http-alt] succeeded!

INFO:root:Private Key: 29c8156de964053a9
INFO:root:WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZhN8faDbJc2NqwACiuJ
Daemon not running; try 'electrum daemon -d'
starting daemon (PID 552717)

INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00022 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 1 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00033 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 2 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00044 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00055 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00066 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 4 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00077 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 5 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00088 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386.
Daemon stopped

[WanderingPhilospher]

Here is my log

INFO:root:Running scan...
INFO:root:Running scan...
INFO:root:Extracted Public Key: 2024-07-24 07:32 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90
INFO:root:Running command: echo '029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90 20000000000000000:3ffffffffffffffff' | nc -v localhost 8080
INFO:root:Keyhunt stdout: 29c8156de964053a9
ERROR:root:Keyhunt stderr: Connection to localhost (127.0.0.1) 8080 port [tcp/http-alt] succeeded!

INFO:root:Private Key: 29c8156de964053a9
INFO:root:WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZhN8faDbJc2NqwACiuJ
Daemon not running; try 'electrum daemon -d'
starting daemon (PID 552717)

INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00022 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 1 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00033 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 2 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00044 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00055 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00066 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 4 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00077 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 5 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00088 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386.
Daemon stopped

So your bot doesn't check for the latest or highest trans fee, it just auto increments until it's the highest? Looks like it reached your set amount of attempts before overtaking the highest fee.

[nomachine]

Here is my log

INFO:root:Running scan...
INFO:root:Running scan...
INFO:root:Extracted Public Key: 2024-07-24 07:32 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90
INFO:root:Running command: echo '029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90 20000000000000000:3ffffffffffffffff' | nc -v localhost 8080
INFO:root:Keyhunt stdout: 29c8156de964053a9
ERROR:root:Keyhunt stderr: Connection to localhost (127.0.0.1) 8080 port [tcp/http-alt] succeeded!

INFO:root:Private Key: 29c8156de964053a9
INFO:root:WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZhN8faDbJc2NqwACiuJ
Daemon not running; try 'electrum daemon -d'
starting daemon (PID 552717)

INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00022 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 1 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00033 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 2 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00044 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00055 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00066 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 4 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00077 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 5 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00088 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386.
Daemon stopped

So your bot doesn't check for the latest or highest trans fee, it just auto increments until it's the highest? Looks like it reached your set amount of attempts before overtaking the highest fee.

Yes. Somewhere at 59.53 USD.

I think this is all nonsense. If we were on a real puzzle 66, we would threw in the garbage 3 BTC  in 5 minutes. That's bad.

[Akito S. M. Hosana]

Here is my log

INFO:root:Running scan...
INFO:root:Running scan...
INFO:root:Extracted Public Key: 2024-07-24 07:32 029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90
INFO:root:Running command: echo '029a3a2ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90 20000000000000000:3ffffffffffffffff' | nc -v localhost 8080
INFO:root:Keyhunt stdout: 29c8156de964053a9
ERROR:root:Keyhunt stderr: Connection to localhost (127.0.0.1) 8080 port [tcp/http-alt] succeeded!

INFO:root:Private Key: 29c8156de964053a9
INFO:root:WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZhN8faDbJc2NqwACiuJ
Daemon not running; try 'electrum daemon -d'
starting daemon (PID 552717)

INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00022 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 1 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00033 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 2 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00044 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00055 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 3 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00066 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 4 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00077 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 5 failed. Trying again...
INFO:root:Running bumpfee command: electrum bumpfee bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386 0.00088 --destination bc1qgtuf2hke00apm2sl6xxu0geeme7g7hnx6k3ydy
WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction bc16e7ce388d936c93583d17c5e691a2677ee9eabbc0ae6d03841fc5e0f1a386.
Daemon stopped

So your bot doesn't check for the latest or highest trans fee, it just auto increments until it's the highest? Looks like it reached your set amount of attempts before overtaking the highest fee.

Yes. Somewhere at 59.53 USD.

I think this is all nonsense. If we were on a real puzzle 66, we would threw in the garbage 3 BTC  in 5 minutes. That's bad.

Well, someone would take half? Or not ?

[nomachine]

Well, someone would take half? Or not ?

I'm not sure if there will be enough left to drink beer. I don't know if it's worse to be a puzzle winner or a bot. Something else must be thought of; this cannot be done like this. It's not worth it to anyone.

[WanderingPhilospher]

Well, someone would take half? Or not ?

I'm not sure if there will be enough left to drink beer. I don't know if it's worse to be a puzzle winner or a bot. Something else must be thought of; this cannot be done like this. It's not worth it to anyone.

That's what I am working on. One failed attempt at a time lol

[nomachine]

Nevertheless, it is a Bitcoin-compliant transaction that can be replaced at any time as long as the original transaction has not been confirmed, isn't it ?

1. You commit your Script behind some address type. Which means, that people won't see for example "OP_RIPEMD160 <puzzleHash> OP_EQUALVERIFY <solverKey> OP_CHECKSIG" immediately, but they will see just some P2WSH hash, or some P2TR public key, nothing else.
2. Then, when you reveal the Script behind your address, it is too late to modify it, because it is already deeply confirmed. And then, nobody can create an identical Script with a different "<solverKey>" or replace solver's key.
3. If you spend coins from the Script mentioned above, then everyone can verify, that you know SHA-256 of the public key. Only the true solver will know that. Then, some huge mining pool can agree to deposit some coins, to learn the solution to the puzzle.
4. The solver will see, that coins are deposited to "OP_SHA256 <revealedHash> OP_EQUALVERIFY <solverKey> OP_CHECKSIG". Everyone will know the address, and the Script behind it, but only the solver will know the public key to the puzzle.
5. The solver can pass a transaction to the mining pool, claiming all coins from his address. Then, the pool can learn the public key, and sweep it with 100% transaction fee.

Edit: In general, it seems to be resistant to some simple attacks:

1. If the solver is lying, he will be unable to produce a proper address, and spend it, while revealing SHA-256 of the public key, so nobody will give him any coins in the first place.
2. If someone is observing the chain, and trying to replicate "I have the key" signal with a different solver's key, then that person will be unable to do that before the solver, because the real solver's address will be deeply confirmed. If we count the earliest attempt as the legit one, then any future solvers will not get anything.
3. Rewarding the solver is not direct, it is more similar to HTLC: there are two conditions: the solver's public key (with signature), and the puzzle's public key (where the hash of it is revealed in the Script). Which means, that the solver cannot run away with coins, without revealing the public key to the puzzle.
4. It is compatible with full-RBF and other network rules: the puzzle can be sweeped with 100% fee, and if it will be done by some pool, then the transaction will start from a single confirmation. Reorging a single block is not that easy. However, if the risk of reorg is too high, then rewarded amounts can be adjusted if needed, and someone may agree to reveal the public key for 6 BTC, instead of 6.6 BTC. We will see.

This is a great idea if it works. Someone would need to test this in the puzzle 66 range to see if it works...

[jacky19790729]

Also albert0, why was your trans fee still lower than my original. You said it was increased 3 times but still was lower than my one and only fee, correct?

My log

Code:

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}

●Response from mempool.space : <html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<center><h2>Sign Up for <a href="https://mempool.space/enterprise">Mempool Enterprise</a> to get increased API limits</h2></center>
</body>
</html>

[albert0bsd]

WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction

I think that you are being limited somehow by that electrum API, it only let you 6 tries?
I think that it should give you a more detailed error of why it fail.

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}

looks like none of your TX were accepted.

the sendrawtransaction RPC errors are something tricky sometimes they told you the required fee to replace the transaction but sometimes in satoshis and sometimes BTC/KvB

We need to parse that error and determine exactly how much fee increase in our TX

Also when the 429 Too Many Requests< error need to be handle correctly, like add some waiting time between requests

[saeedxxx]

WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction

I think that you are being limited somehow by that electrum API, it only let you 6 tries?
I think that it should give you a more detailed error of why it fail.

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}

looks like none of your TX were accepted.

the sendrawtransaction RPC errors are something tricky sometimes they told you the required fee to replace the transaction but sometimes in satoshis and sometimes BTC/KvB

We need to parse that error and determine exactly how much fee increase in our TX

Also when the 429 Too Many Requests< error need to be handle correctly, like add some waiting time between requests

It's better to use different ips (like a pool of ip or proxy) to send such requests.

[nomachine]

WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction

I think that you are being limited somehow by that electrum API, it only let you 6 tries?
I think that it should give you a more detailed error of why it fail.

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}

looks like none of your TX were accepted.

the sendrawtransaction RPC errors are something tricky sometimes they told you the required fee to replace the transaction but sometimes in satoshis and sometimes BTC/KvB

We need to parse that error and determine exactly how much fee increase in our TX

Also when the 429 Too Many Requests< error need to be handle correctly, like add some waiting time between requests

It's better to use different ips (like a pool of ip or proxy) to send such requests.

I don't see anything detailed here. I will have to install the bot directly on
 the Bitcoin Node machine and use Electrs
https://github.com/romanz/electrs/blob/master/doc/usage.md

[Akito S. M. Hosana]

WARNING:root:Fee bump attempt 6 failed.
ERROR:root:Max fee bump attempts reached for transaction

I think that you are being limited somehow by that electrum API, it only let you 6 tries?
I think that it should give you a more detailed error of why it fail.

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}

●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}

looks like none of your TX were accepted.

the sendrawtransaction RPC errors are something tricky sometimes they told you the required fee to replace the transaction but sometimes in satoshis and sometimes BTC/KvB

We need to parse that error and determine exactly how much fee increase in our TX

Also when the 429 Too Many Requests< error need to be handle correctly, like add some waiting time between requests

It's better to use different ips (like a pool of ip or proxy) to send such requests.

I don't see anything detailed here. I will have to install the bot directly on
 the Bitcoin Node machine and use Electrs
https://github.com/romanz/electrs/blob/master/doc/usage.md

So, full-node OS and tweaking directly on it? This is getting more and more complex to keep track of.
Are you going to make a tutorial for n00bs?