ttdpool and ttdclient already have this. Fastest client, secure server and startup scripts.

  priv2addr.py 2832ed74f2b5e35ee
  Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

     Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

    Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

       Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

 Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

    Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

Clown music here


There is a lot of bitcoin holders that are just waiting to see their holdings increase the value..

showing an address is not evidence of anything.

I can't prove the the puzzle creator not move that balance.
You can't prova the puzzle creator move it...

anything that we write here is pure speculation, is just an opinion of what you or me personally believe.

I bet it was immediately after solving puzzle 64

Key was 2832ed74f2b5e35ee.


No idea, the prize was send to two different addresses.

my bot was off this week sadly Murphy's law has been fulfilled

Gratz to the first that the puzzle  66 got confirmed 

If "if" was a fifth, the whole world wold be drunk lol.

You can do it however suits you. I've done some research and testing and I am telling people one way to do it. To each their own.

But I do not think you understand Mara.

Even if they did have this rogue employee, it would be easy to investigate and find out who, what, where, when, why.

Mara is worth 5.76 Billion dollars, are publicly traded, just bought $100 million in bitcoin, and mine and average of 7 bitcoin blocks a day.

You think they would risk public scrutiny, investigation, etc. over 6.6 BTC, over $429,000? When they are worth billions and have a lot at stake, in the public's eye?

I don't. If it did happen, I am pretty sure they would figure out who did what, and settle the matter, quietly and fair versus risking millions of dollars over 6.6 BTC.

And you crack me up. You would make an agreement with just a run of the mill mining pool/miner? Ok, so you have it in writing. Now let's say the same thing happens in your scenario. The person/miner who you have whatever in writing with, slides that info over to another miner. Same thing could happen there, but people who are miners in that pool won't care. Why would they? That miner you signed whatever with probably isn't under rules and regulations. Then it's just he said, she said.

But at least with slipstream, you have some comfort in knowing they are a legit, legal entity, publicly traded, have to answer to shareholders, officials, etc.

But again, everyone do what you think is best for you/what you can stomach.

People wanted a way to do this, and I have shown one option, a super great option IMO. That is all.

I would say that the silver lining is, they are a publicly traded company...not a side street vendor. Meaning they have shareholders/stockholders, traded on an exchange. Very public. They are on the NASDAQ. They aren't just a simple mining pool.

If that happened, the coincidence would be too huge, and would be an easy investigation.

Would a company like that want that investigation and open up everything, and go through the public scrutiny. And possibly lose millions in stock value?

I dunno, but I doubt it.

You may never get those specific BTCs back, but I bet you would be compensated, somehow, someway.

True, it's hard to trust anything these days, but IMO, this seems to be one of the best, secure, safest ways to transfer 66's funds, if not the best. (Unless you run your own pool mining outfit and can include it in your owned mined block )

Forget the old bot script. I'm making a new one that will work directly on node.
No API - no external domains. BTC network only.


 Sure. And a telegram channel for support.    

perfect, since you are the guy, tomorrow at 15:30 (UTC -3. Brasilia Time), the creator will do the transaction and expose the public key, put your knowledge into practice and prove what you are saying, otherwise , and if it is not hacked, it can be said that we still have hope.

Good to know that even after 12 minutes the fork coins were intact. So probably the situation is not that bad as we are anticipating

jean luc kangaroo just added to his github's readme.


#130, 129bits private key [2¹¹⁹,2¹²⁰-1], [1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua](https://www.blockchain.com/explorer/addresses/btc/1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua) **13.0BTC**

Expected time: several years on 256 Tesla V100 (Not possible with this program without modification)
damn

Are you sure? When I tested many moons ago, if I ran a higher range than 128 (b/c hash table only stores 32 hex characters for point and distance (32x4 = 128)), the distances and points were correct, but obviously the leading characters were left out/off because of the 128 bit max storage.

I may have to run again and retest, and extract the hash table....I will check it now.

Update:

It is as how I remembered it. I just ran a super quick test for the 130 bit range. As you know, the program subtracts starting range so we are working with 0 thru 1ffffff.....(129 bit range)
Here is extracted DP, DP of 20:

178559a1004e94449e90d76ca10b3600 26311140a6e43a1530526461aed458e4

On the surface, if you just plugged in 26311140a6e43a1530526461aed458e4, it seems false, but we know that the only other possible number that could be added in front is a 1, so add a 1 to 26311140a6e43a1530526461aed458e4 and you get 126311140a6e43a1530526461aed458e4, now cross reference that distance and you get this point:
0300000B71D19F5FCD4AC6184EDE7C000C178559A1004E94449E90D76CA10B3600
which matches up to:
178559a1004e94449e90d76ca10b3600
178559A1004E94449E90D76CA10B3600

So that is what I mean by doing some manual work if you use JLPs unmodded version and find a collision in the 130 bit range. But if you go up to 135, it gets a little more tricky/complicated.

But you could be correct! Maybe I didn't let the program run long enough to see how any subsequent keys would be handled.

Honestly, I wouldn't use the unmodded version, nor the 256 bit one on github (doesn't work).

To be safe, use Etayson's Kangaroo on github or mod your own version. That's the safer bet.

Well not all the miners but some of them yes that depend of the version and custom configuration, the exact number is unknown

It is a Node configuration and it may vary depending of the Bitcoin Core Version.

The full name is Full RBF

Check this link:

Replace-by-fee (RBF)


Also this link:

https://en.bitcoin.it/wiki/Transaction_replacement

Just to mention that when the nodes have many FullRBF transacions not always win that one with more fee, here some examples, Dot with Green margin was mined, some are Testnet and other are mainnet

Is somehow now near of 100%?

I haven't bothered to read the article because it seems OP is also looking for clicks (based on his username @seoexpert555), but can someone tell me why he does not deserve a red tag and flag. From what I can deduce from the post and comments, he is misinforming people and perhaps even scam them in the name of securing their private keys.