Bitcoin puzzle transaction ~32 BTC prize to who solves it

[alexxino]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

Do you have a binary to search vanity which runs on Silicon CPUs? I could not find any nor make it work, a lot of libraries are only for intel.
Could you share it ?

[Anonymous User]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

There are already plenty of people using the same trick or method to find private keys within a similar range, as I mentioned. It's not surprising or new information to most of us. Developers have known for a while that there are tens of thousands of addresses like this clustered in the same range. You spent time, energy, and resources on this approach, but it may not be as productive as you hoped. My intention is not to stop you but to educate you.

[ihsotas91]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

Do you have a binary to search vanity which runs on Silicon CPUs? I could not find any nor make it work, a lot of libraries are only for intel.
Could you share it ?

It is very simple vanity search using "random" and written in Python


<sup>import sqlite3
import random
from bit import Key
import bitcoin

# Connect to vanity_addresses.db for storing found vanity addresses
vanity_conn = sqlite3.connect('vanity_addresses.db')
vanity_cursor = vanity_conn.cursor()

# Create a table in vanity_addresses.db to store vanity addresses and private keys
vanity_cursor.execute('''
    CREATE TABLE IF NOT EXISTS vanity_addresses (
        address TEXT PRIMARY KEY,
        private_key TEXT
    )
''')
vanity_conn.commit()

def generate_vanity_address(prefix):
    while True:
        # Generate a new private key
        private_key = random.randint(147573952589676412927, 295147905179352825855)
        # Compute the corresponding public key
        key = Key.from_int(private_key)
        addr = key.address
        addr_uncompressed = bitcoin. privkey_to_address(private_key)

        if addr.startswith(prefix):
            # Insert found vanity addresses into the vanity_addresses.db database
            vanity_cursor.execute(
                'INSERT INTO vanity_addresses (address, private_key) VALUES (?, ?)', (addr, str(private_key)))
            vanity_conn.commit()

        if addr_uncompressed.startswith(prefix):
            # Insert found vanity addresses into the vanity_addresses.db database
            vanity_cursor.execute(
                'INSERT INTO vanity_addresses (address, private_key) VALUES (?, ?)', (addr_uncompressed, str(private_key)))
            vanity_conn.commit()

            # Log that a vanity address was found
            # print(
            #     "Vanity Address found and inserted into the vanity_addresses.db database:", addr)


prefix = '1MVDY'
generate_vanity_address(prefix)</sup>

[ihsotas91]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

There are already plenty of people using the same trick or method to find private keys within a similar range, as I mentioned. It's not surprising or new information to most of us. Developers have known for a while that there are tens of thousands of addresses like this clustered in the same range. You spent time, energy, and resources on this approach, but it may not be as productive as you hoped. My intention is not to stop you but to educate you.

Thank you. I thought the same in the beginning. However check the range for the addresses I shared, it is not a small range to cluster. That's why I could not understand how. I mean system should cluster some portion of different ranges in the defined range, if so, this is amazing, because it can give a chance to solve small puzzles like in #67 or #68 (extremely low probability but still good) to any personal computer with silicone chips.

[Anonymous User]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

There are already plenty of people using the same trick or method to find private keys within a similar range, as I mentioned. It's not surprising or new information to most of us. Developers have known for a while that there are tens of thousands of addresses like this clustered in the same range. You spent time, energy, and resources on this approach, but it may not be as productive as you hoped. My intention is not to stop you but to educate you.

Thank you. I thought the same in the beginning. However check the range for the addresses I shared, it is not a small range to cluster. That's why I could not understand how. I mean system should cluster some portion of different ranges in the defined range, if so, this is amazing, because it can give a chance to solve small puzzles like in #67 or #68 (extremely low probability but still good) to any personal computer with silicone chips.

If you check the probability of finding the exact same address, it might take 100 or even 1,000 years using random numbers. But if you think you're lucky enough, you might find it today itself!

[alexxino]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

Do you have a binary to search vanity which runs on Silicon CPUs? I could not find any nor make it work, a lot of libraries are only for intel.
Could you share it ?

It is very simple vanity search using "random" and written in Python


<sup>import sqlite3
import random
from bit import Key
import bitcoin

# Connect to vanity_addresses.db for storing found vanity addresses
vanity_conn = sqlite3.connect('vanity_addresses.db')
vanity_cursor = vanity_conn.cursor()

# Create a table in vanity_addresses.db to store vanity addresses and private keys
vanity_cursor.execute('''
    CREATE TABLE IF NOT EXISTS vanity_addresses (
        address TEXT PRIMARY KEY,
        private_key TEXT
    )
''')
vanity_conn.commit()

def generate_vanity_address(prefix):
    while True:
        # Generate a new private key
        private_key = random.randint(147573952589676412927, 295147905179352825855)
        # Compute the corresponding public key
        key = Key.from_int(private_key)
        addr = key.address
        addr_uncompressed = bitcoin. privkey_to_address(private_key)

        if addr.startswith(prefix):
            # Insert found vanity addresses into the vanity_addresses.db database
            vanity_cursor.execute(
                'INSERT INTO vanity_addresses (address, private_key) VALUES (?, ?)', (addr, str(private_key)))
            vanity_conn.commit()

        if addr_uncompressed.startswith(prefix):
            # Insert found vanity addresses into the vanity_addresses.db database
            vanity_cursor.execute(
                'INSERT INTO vanity_addresses (address, private_key) VALUES (?, ?)', (addr_uncompressed, str(private_key)))
            vanity_conn.commit()

            # Log that a vanity address was found
            # print(
            #     "Vanity Address found and inserted into the vanity_addresses.db database:", addr)


prefix = '1MVDY'
generate_vanity_address(prefix)</sup>

I was thinking something in objective C or C++ native langs for MacOs. Thanks for sharing the python script anyways 

[oddstake]

IMO the Creator is using you and your brute-forcing software available on Github to help him recover a big wallet which maybe was lost in the past, it could be even a 160 bits key with a known pubkey. (eg this one https://bitinfocharts.com/bitcoin/address/12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr )
He can't do it alone so sacrificed some of his bag by creating this puzzle.

[AloneNow]

Hello.

First thing first: i am the solver of Puzzle 66.
But i lost it soon as it was spend.

i was searching for a couple of years and finally i had some "bad" luck on puzzle 66.

after importing the key, i was withdrawing it so so fast in the hope of finally can change my life and stop eating this bad food here. ( i dont want to say which contry i am from and sorry for my bad english )
but sadly... it was only a dream for a short time...

so....
hey stealer, if you read this, please give me 50% and get me right back up after falling in a deep depression after this... i am really sad... i put so much energy in it and it was all for nothing...
bc1qgfeg5kxzpk9dkxla9lkpcuucdjjtu9swqntl7l



.. good bye guys

[citb0in]

Hello.

First thing first: i am the solver of Puzzle 66.
But i lost it soon as it was spend.

i was searching for a couple of years and finally i had some "bad" luck on puzzle 66.

after importing the key, i was withdrawing it so so fast in the hope of finally can change my life and stop eating this bad food here. ( i dont want to say which contry i am from and sorry for my bad english )
but sadly... it was only a dream for a short time...

so....
hey stealer, if you read this, please give me 50% and get me right back up after falling in a deep depression after this... i am really sad... i put so much energy in it and it was all for nothing...
bc1qgfeg5kxzpk9dkxla9lkpcuucdjjtu9swqntl7l



.. good bye guys

unimaginative and very bad drama what you are trying to stage here, simply pathetic
go get some life, don't blame others, stop begging

[Kelvin555]

Hello.

First thing first: i am the solver of Puzzle 66.
But i lost it soon as it was spend.

Sign a message with the first address that tried to withdraw puzzle 66 because I don't believe you, I think you're a scammer.

[gygy]

Hello.

First thing first: i am the solver of Puzzle 66.
But i lost it soon as it was spend.

Sign a message with the first address that tried to withdraw puzzle 66 because I don't believe you, I think you're a scammer.

He IS a scammer. He shows no proofs. The original solver address is 1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd and there is no use to beg using any other address. Anyone can send to the proper address. The one who stole the fund was sending a mocking message to there. I don't think he is willing to send half of the stack.

[bibilgin]

Hello.

First thing first: i am the solver of Puzzle 66.
But i lost it soon as it was spend.

i was searching for a couple of years and finally i had some "bad" luck on puzzle 66.

after importing the key, i was withdrawing it so so fast in the hope of finally can change my life and stop eating this bad food here. ( i dont want to say which contry i am from and sorry for my bad english )
but sadly... it was only a dream for a short time...

so....
hey stealer, if you read this, please give me 50% and get me right back up after falling in a deep depression after this... i am really sad... i put so much energy in it and it was all for nothing...
bc1qgfeg5kxzpk9dkxla9lkpcuucdjjtu9swqntl7l



.. good bye guys

TTD (ttdsales) changed the name to Chris.

New Member - 1 Message

Nice tactic.

[Cricktor]

First thing first: i am the solver of Puzzle 66.

Bullshit until you properly prove it that you're in control of the first destination address you presumably tried to transfer the funds of #66 to. Without a proof anybody can make such a pathetic claim who's willing to embarrass himself in public.

But i lost it soon as it was spend.

And now tell us, why didn't you use slipstream.mara.com to transfer the funds non-publicly? Not the brightest candle on the cake?

Anyway, nobody will believe you until you prove it. I say: won't happen. Surprise me!

[lordfrs]

Isn't it strange that the 130th puzzle was solved just 10 days after the 66th puzzle?? 

[bibilgin]

Isn't it strange that the 130th puzzle was solved just 10 days after the 66th puzzle??  

Yes, interesting.

17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT 27/02/2023
1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5 09/07/2023
1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua 24/09/2024

All of these are being transferred to 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs.

But for some reason, as of 27/02/2023, not even $1 can be withdrawn or processed? Another person who doesn't need it?

[karrask]

I realized something strange after some tests.
I have a lot of equipment. All running for searches about these puzzles.

To have fun, I chose to search via vanity in last days.
I have desktops and notebooks with latest and powerful intel chips, nvidia graphics, 120GB DDR5 etc. each. On vanity, these setups find ~20 addresses per day for each.

However, when I applied vanity via apple silicone chips (M1, M2, M3), daily found vanity addresses ~500 per each setup.
I observed the behavior, and when it finds a vanity address in the pool I search, immediately it finds 5-6 addresses more in milliseconds, it is moving to the numbers to check that might have the vanity around some near numbers while I'm generating those numbers using "random".

For example:


^{1MVDYUvrcMqdprCTYuthuaQxWWAL8Ty2KS 220647290646478288674
1MVDYE2EHY3VR3AXKrD7mYvpSgD2SGgqZb 257335783054352585279
1MVDYuE5HGPjYaEH72sZukwNXhdtdKSQRY 280101386265359359876
1MVDYNcMjPsAW1PQgjwCGRNwijJMSW1UcR 274962343828436157207
1MVDYGms9qGRsrDD7AuoyYJBZnJTzAj9B8 213173989571665196391
1MVDYnfq7s3yG8fdnhQ66cqDa4h2DNoGeB 247904416465366500764
1MVDYY8GUU8or4WfLSrsbHip8F7pwA4xpv 243282287509672730681
1MVDYxMNG8fKf9fvX3r5PmwNXY8tjfESsu 245042251007899478320
1MVDY8aYEQsCWqU2MVWRjhrLHaX28SHFky 270190501490895327846}


These are found in the same second and it keeps this behavior.

This behavior made me crazy guys. I do not understand how it can do this.

 

HEX: 2a2048efa014916a94c, Address: 1FWGcV4QKWuhCKGtHQpQ76uuLEuZa3feZC, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3upXcSULTF237swFahZyC
HEX: 3e0b29c0340b23426f5, Address: 1FWGcV5YXZPwk2867pjoqPk4jpw93E88rs, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wqgkULjAcBY2ta9smdQR
HEX: 39e1c8d5174d8fd823d, Address: 1FWGcV6vXqQHTMw1gohb3QFGiFRDh4atHX, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wRCwyzgqnUQoegoyjwoe
HEX: 3732132020d56032743, Address: 1FWGcVGKrcgG3vE9Fx5ksbd6hDDDbFHteH, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3w9QTRSox58FdipAMX7CF
HEX: 3c648905d9648913c7f, Address: 1FWGcVHH9fiEDqWaJArbF3QfecihhxbtuJ, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wfyXS4UFy5K1MRjNzs7V
HEX: 21b7b0b4751c184d7cf, Address: 1FWGcVHZTVezXXAH9XptJREyFaEXHbPpAo, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3ty4uXuV5meBWMDX7FaBC
HEX: 28b69ae1961fb9f1cde, Address: 1FWGcVKqsay43c3NxifnhRZ4bVpih1ohAn, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3ugDcNgr4giLLrSRZGrqy
HEX: 3dfca2d6821437a42e9, Address: 1FWGcVPgVxLmqxhUfpEPBhnHrUnwWBi8tS, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wqMPc9TBXoZ4FQwA2BAy
HEX: 3be1328123962326815, Address: 1FWGcVSvCAG1yWo9NB5CTeCrAZTyzMaMmY, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wcxVfAVMvEWyL8tJXK4y
HEX: 30b5d6d13e82301be2d, Address: 1FWGcVT4s8wpJQm2NLF7omfhiSCTfckMsu, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3vVFuS8Uw7Au3iJZefv1W
HEX: 3c05b396bc124762768, Address: 1FWGcVUwYjdysoc1eHgAKvn4bbLe1ZrTME, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wdo9FmbribpQRkKuGfr7
HEX: 2c307aefe023769c2f0, Address: 1FWGcVVR24oNLaZidNfQjygq6YPxmBgbQC, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3v2fXKdus4UBYEG12s9RP
HEX: 3ef4ecf2a58d5a7379c, Address: 1FWGcVaoaLzkYkwCRFLsZxjp2ENpCm6vj2, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3ww4H9wJAp8EYhXstqZb8
HEX: 2bd3d5606c69f02ab1f, Address: 1FWGcVbBHmX2atsPo7wT8RjdSLjJ4m2T37, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3uzY4BwfzW5FzkSR4VNHJ
HEX: 3e9ac3fdc5b75324c97, Address: 1FWGcVcJ6fugNwfUjUFS9nK36MwDgP9DfC, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wtz8EYtZtVz2ZQot2dxq
HEX: 35392131d84f18372a7, Address: 1FWGcVgJoVQTQWDt2RCQaDHDTS1awD9C1p, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3vwoXft5ojei2mqb1nK96
HEX: 213a274705870e04cd4, Address: 1FWGcVggq8hh3kwU22VrfEvf5CFFkroCyM, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvBcAA83z8UKmsUYrQz3
HEX: 2c74842c1fd4dc25369, Address: 1FWGcVnwDMfa5nm8KaxguWs9fnonDkacjH, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3v4ECB33kyfp1jJFULMbj
HEX: 321af0a0807e8ac4d06, Address: 1FWGcVshxeRSR272S8y47TD9gSnivChacr, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3vdToZNLyBeGtwJuxqQqp
HEX: 23d5972dc7afeaf2510, Address: 1FWGcVsiJsx2YEZEEGKFotnWKfAJF8Zf2J, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3uBX5k1PrhkuZdFWDwmi1
HEX: 394c61b3ef2f6878fd5, Address: 1FWGcVuha19wPdzGo1pRpXgokuSjKzAshn, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wMmqtAyjrcmCm859Ti3V
HEX: 3c6d168615bcb4a0b3a, Address: 1FWGcVujVUA66yDQT8VYVvE93mJLBx9WAs, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3wgAvWx27NwDNwyDxX334



HEX: 2107a670d82712594d5, Address: 1FWGcs27ucDbbnDZUzDgt7YVy32bkaUYMe, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tu2JWK4eqt58u21DpdiP
HEX: 210b8c40827024d2c8a, Address: 1FWGcEofmayEn5JygGkiHiZwAeJEtiXJf2, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tu7Vn97gWkUVubmZ1QD6
HEX: 210bd850691681858c7, Address: 1FWGcedgLsmFzRkvLWDoL4dUCSeY281Rgi, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tu7tk9oWHfeexU5U3Qyz
HEX: 210c258464d1765792d, Address: 1FWGcEouKnSARwnt3ZqPwHB5Zu3bxNSYFu, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tu8J49MXbjMuzFEFM7GY
HEX: 210c93620e0104d13a2, Address: 1FWGc4rFN8jNySihhwJaZg7DJrUwJbqFjf, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tu8sE8gnpCU3y9H3Dumq
HEX: 210df30c421f12dc4bc, Address: 1FWGcpGTmc4HWjtJxuVY32VgXWccu8nvTS, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tuAhQYXMSYBQAK43RthA
HEX: 212d8c438f214508af4, Address: 1FWGchzf4WtdZY3x3iE7rsFy9rbL45NqFd, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tutopBb5uoP7XZwcrUJA
HEX: 21313854d0515f8590c, Address: 1FWGcCGYaYUNkPUTicNqgjbE8twi4MEDVu, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tuyhenyCGQn7S3Qyzruq
HEX: 2135b5c156cfc28042c, Address: 1FWGcFizjeguVdTx12VA5Af6pk5u3ccTv6, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tv5ghgsTZGjNVLjJx2cy
HEX: 213a274705870e04cd4, Address: 1FWGcVggq8hh3kwU22VrfEvf5CFFkroCyM, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvBcAA83z8UKmsUYrQz3
HEX: 213ba1df07c7d462438, Address: 1FWGcHCJYMwf96aZvcoZjjD2EMpk1Ha4hc, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvDaU9p1ysAmignGCw1U
HEX: 213e1f10741b7db306c, Address: 1FWGczLiB1YMGPSVXuFbdqoPi3rAZwQ1qj, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvGtrn8xEVcF3WgDZ8fY
HEX: 2140e6f0c8cdfafc949, Address: 1FWGcFwgKm1g7yRnYW96Cjti5hpTdtZK9d, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvLboGcePrbitcrAunrR
HEX: 214747c0960bc9a75ac, Address: 1FWGcKZ9L8txj5KUXshqM8mbAbZzFY3JBt, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvV6oL2w6cpzawXkUzXH
HEX: 214c7f9d8f34c3d8f47, Address: 1FWGcXaSKyP92HJ2eHjPr9YuL2FSCfYnSf, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvc49BFsoN3tJoRzV7Hj
HEX: 214de5c9345ab7e45d8, Address: 1FWGceDmnti5NJBLYCRnk7EckiPouP8N6M, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvdvHWu3B4aqRYGmPUsv
HEX: 215420f7b9153b2edb4, Address: 1FWGcJTL1WbATM2atDe3c82gqCdBa79mQQ, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvnDvbKGjdjtXm51mAVE
HEX: 2158e4253b464edb2a1, Address: 1FWGcHaQ8LhqaJquW9naPt8cfYF2F6bNLY, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvta32ZKaHU4fAGWHcEQ
HEX: 21590b1a3e507973e67, Address: 1FWGcLNvf7ewcsvhZ882eE8PsQ3NeyaW7Z, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tvtmoFTyAMkpVf4Bch7J
HEX: 21719292f4be134dce4, Address: 1FWGcqxNJrQ9htaDXzDVUz4bKnTFdHH7J5, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3twTTnMaecxXW4MmYEx6Q
HEX: 2179d73fd19e79451bd, Address: 1FWGc6oGEc7zFx26e3vK4UbhDSfaGbbJ3s, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tweUsui9YMXyppKodRqg
HEX: 2183c4e864d3ef97ac8, Address: 1FWGcwchJayNhm97WGtJAvkuSvyQLQuTFm, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3twsiHqZ1Nv9RPpf6EQzX
HEX: 21846038cd1b7464fa6, Address: 1FWGcjeUbrDyW4MChG4i3FvFvhunHS9uMG, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3twtXBitUNri6vsWSivCY
HEX: 21861c15cfc1c104012, Address: 1FWGcSk6u9jrDeBciiSq7wc12GXvxn4Hp6, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3twvqCjBs2zq2MorcStvQ
HEX: 2186576c4c5a5e54f4e, Address: 1FWGcQuRnMsPVjJrTzvcSxPmunUCUzYz8D, WIFcompressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3tww97rwZbvjoyGfZmeHW

[nomachine]

so....
hey stealer, if you read this, please give me 50% and get me right back up after falling in a deep depression after this... i am really sad... i put so much energy in it and it was all for nothing...

Ah yes, the classic story of Puzzle 66, where the key was faster than my Wi-Fi! I, too, was ready to change my life and say goodbye to instant noodles forever... only to watch the dream evaporate faster than my hope in crypto riches.

But hey, stealer, if you're out there, how about we split the 'bad food fund' 50/50? You keep 50% of the loot, and we can both try to bounce back from my deep, puzzle-induced depression. 🤷‍♂️

As for my fellow puzzle chasers: Let’s not stage any bad drama here—I’ve already seen enough of that in my own life! It’s time to embrace the tragic comedy that is puzzle-solving. 😅 Also, note to self: if you’re poor, solving complex puzzles may not be the miracle escape plan you hoped for. But hey, who needs financial freedom when you’ve got sarcasm?

Let’s just say, if puzzles were your 'big plan' to escape bad food, you might want to try a new recipe! Go fishing and eat fish every day.

[Akito S. M. Hosana]

It’s time to embrace the tragic comedy that is puzzle-solving. 😅 Also, note to self: if you’re poor, solving complex puzzles may not be the miracle escape plan you hoped for.

This is the sad truth. You have to be a millionaire or have a rich dad to be able to solve the puzzle. Or work for companies where you can steal resources.

[COBRAS]

It’s time to embrace the tragic comedy that is puzzle-solving. 😅 Also, note to self: if you’re poor, solving complex puzzles may not be the miracle escape plan you hoped for.

This is the sad truth. You have to be a millionaire or have a rich dad to be able to solve the puzzle. Or work for companies where you can steal resources.

Unfortunately this is one of more normal idea in this  thread 

[Anonymous User]

It’s time to embrace the tragic comedy that is puzzle-solving. 😅 Also, note to self: if you’re poor, solving complex puzzles may not be the miracle escape plan you hoped for.

This is the sad truth. You have to be a millionaire or have a rich dad to be able to solve the puzzle. Or work for companies where you can steal resources.

Or start a fake puzzle solving pool like TTD's. Who stole thousands of peoples computing power but still couldn't able to solve.