The death of the monitoring bots for the low bit challenge/puzzles such as the 66, 67, 68 bits.
The sure fire way to get all of your hard earned 6.6 BTC into one of your safe wallets...or is it a sure fire way?
Let me know what you think.
Ok, so here is the current, thoughtout way to beat the bots when dealing with the puzzle/challenge low bit wallets.
I tried this on my first test, but it didn't quire work. I thought it was probably because I fat fingered something, although I knew I didn't.
Turned out to be a lack of monitoring, possibly.
I did run a follow up test (privately) with success, and also had someone else test the process. They encountered what I first encountered and had to send a gentle reminder, lol. More on this below.
So I know of two tests, that have worked, so I am laying this out here so maybe someone can shoot holes in it, and/or whoever solves the 66 bit challenge, can rest a little easy.
What I would do if I found the 66 bit key.
First:Take the 66 bit found key and import it into whatever wallet. In my tests, I used electrum (older version because I can unselect RBF, just in case). You can use whatever wallet (as long as it allows you to export a signed raw transaction hex.)
Second:Go to Go to
https://slipstream.mara.com/ and see what their current minimum fee rate is.
Third:Now, create a payment to a safe wallet of yours (From the found, imported, 66 bit wallet.)
Go through all of the pay options in your particular wallet, pay to, amount, fee, and sign. (Make sure your transaction fee covers the minimum over at slipstream.) BUT DO NOT BROADCAST.
Fourth:Export the signed transaction, save it somewhere safe and that you will remember. Electrum allows this but I am not sure about every wallet.
Fifth:Now, open that exported transaction document and you should see something like this (using one that albert0 posted earlier, just as an example:
01000000029e8c8c0f85d43b8d6aa7d41a0d6f45d67c0f003a4285f3046bf8413b14cf557801000
0006a473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f783
02200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2
ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff
or it could start with a 02
02000000029e8c8c0f85d43b8d6aa7d41a0d6f45d67c0f003a4285f3046bf8413b14cf557801000
0006a473044022019defb9f5402b1458982ba7e60813ee8824c8882a9551741c20a883895c3f783
02200fcc27f0040c519723edc792bd3a08911618c4e33f1ba06f2edf2362b1f332a80121029a3a2
ae3ad3858cf49421e6ff547598bb8da72c2bce50490067d9ce7b2e2dc90ffffffff
Sixth:Copy that raw transaction.
Seventh:Head back over to
https://slipstream.mara.com/ and paste that raw transaction into the applicable space and select the "Activate Slipstream" button. You should now receive a confirmation message like this:
"In Marathon's mempool, waiting to be mined. You can view the status here."
Eighth:Select on that view status here button from above. This will open up a new window and will show your tx's status in their mempool and the Transaction ID.
Ninth:Copy that transaction ID from above and save it somehwhere you will remember.
Ok, now you have successfully bypassed the regular mempool, or have you? Just sit back and wait for the transaction to be mined into Mara's next block, right? It depends...
On my first test, my tx just sat there for days, block after mined block lol. I eventually "cancelled" it.
But I did reach out to slipstream via their email and asked questions, such as, had I done something wrong, not big enough fee, etc. But now since my transaction was gone from their mempool, I didn't get an answer.
So I ran another test, ensuring no fat fingers, and still nothing. So I reached back out to slipsteam again, but this time I had my tx id (from eighth step) and I included that into the email I sent them, and low and behold, the transaction was included in
their next mined block.
The other individual who ran the test (and I did not warn them because I wanted to see if they had the same results as me) had to do the same thing; email slipstream, and then their tx was included into Mara's next mined block.
So I am not sure if they just don't monitor the transactions entered into their site because there aren't many or what. I did reach back out to them via email and waiting for a reply.
Either way, that is two tests completed with the process above with expected results/outcome.
So is this the death of the monitoring bots? You tell me.
The sent from address's tx is never sent to the mempool, exposing its public key. Only after it has been mined into a block, is it exposed.
Thoughts, comments, questions?
