Bitcoin Forum
May 24, 2024, 04:04:01 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 »
1  Economy / Scam Accusations / Re: CRYPTSY stopping withdraw locking accounts without notifying users! Class Action on: May 22, 2024, 11:19:55 PM
yeah stolen funds return my biggest funds i had there, same nick as here..
2  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: May 10, 2024, 10:22:40 PM
ok hi there, k3ntINA, we need so many kind of skills with this, still this could be the only skill needed,
to solve it right, and some, some kind of skills you are showing,
but merely few get the picture, get it, what is your youtube channel, or the link
if you have posted it,
3  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: April 24, 2024, 12:14:46 PM
I have another idea,

The puzzle creator said the only thing all the private keys have in common, is that all of them were created from a HD wallet, and then masked from the left with zeros.

Is it any weakness on the HD method of creating wallets? I mean, with the number of private keys already revealed, we could just try to target the searches for the the master private key that was used in the HD wallet.

What do you think?

Regards.

nice catch, go go go from me,
when update ready.
4  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: March 21, 2024, 10:19:35 PM
jean luc kangaroo just added to his github's readme.


#130, 129bits private key [2<sup>119</sup>,2<sup>120</sup>-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
5  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: March 21, 2024, 03:45:44 PM
UNSPENTS
height: 339085 tx_hash: 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 tx_pos: 65 value: 6600000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 496585
height: 475240 tx_hash: 5d45587cfd1d5b0fb826805541da7d94c61fe432259e68ee26f4a04544384164 tx_pos: 14 value: 59400000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 360430
height: 581637 tx_hash: c725a765997cf82ca4a40cb2166f9ed2c2677e9ad9446112dd94920db7034a07 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254033
height: 581641 tx_hash: 9623ca8da4f10db5ca90a0673674571a3150e568cb82c2e2ad6ca55af77a67f9 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 254029
height: 601832 tx_hash: ab571acb61ec96a4759da551ae37a1fe5accbd353dfca3e1a57cb254e5e0e790 tx_pos: 1 value: 666 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 233838
height: 666538 tx_hash: 33ea377a3c0aa2e10f498a41f746d7489e06bf9b6e45b406b817ee96e4cec96b tx_pos: 1 value: 1950 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 169132
height: 755590 tx_hash: 4461b388764735edf0b8b35456846c251dc7e281a8837df42f684b4bfce91f72 tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 80080
height: 759213 tx_hash: c1a490e56f7faea9c064fd30023647780d5b3fa330cd7ec10c60c513c3f36813 tx_pos: 0 value: 1533 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 76457
height: 761116 tx_hash: 1602e46f048a7466db2f630f74e6f83a6e72fb2726067ac719c7de3ab784689c tx_pos: 0 value: 600 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 74554
height: 763866 tx_hash: 3615aa6fc46e190a9d542844172a105191c902402ff753c96f6bd591ea2aecad tx_pos: 0 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 71804
height: 777889 tx_hash: acdf413e69ab69a2628e50225096f14fab57483b1d908387e00d593d56abe425 tx_pos: 0 value: 908 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 57781
height: 778883 tx_hash: 7cce2dde07daaa77a0c2159ae079cf56a1b9ca8196c0b122666d3d40d5314e22 tx_pos: 1 value: 1000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 56787
height: 785620 tx_hash: 12f34b58b04dfb0233ce889f674781c0e0c7ba95482cca469125af41a78d13b3 tx_pos: 1 value: 594000000 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 50050
height: 831116 tx_hash: 6a76cd295c5fe4037511c2e5c2945b99aa52e2fd41d014943c0a975e08a5ce17 tx_pos: 0 value: 6700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 4554
height: 834413 tx_hash: 8da7b3599f9fec422ace5d290443c17f685d6e45ce89ca1ee0a334b711f10745 tx_pos: 0 value: 660 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1257
height: 834609 tx_hash: 8cc982de6db7539fa665840ff774d69807a9d85c01e17620205da67de995ea29 tx_pos: 0 value: 1277 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 1061
height: 835645 tx_hash: cff6de5c21176e8cb9d60fcf1e2a2d9a44b9267860126cfddee5d7fa39ab27e1 tx_pos: 0 value: 6018 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 25
height: 0 tx_hash: d7d518a01522f0ac26dddf0595265c9acbfc52361e1e5c7da2c17fd930a5d0c3 tx_pos: 0 value: 616 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0
height: 0 tx_hash: d76dccf84fde447a3fd11d50d70ae7e187ede0e8829f99b39a420962795b7ad2 tx_pos: 0 value: 4700 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0
height: 0 tx_hash: 55571ca5e1f86c11a5ec5837aa1edf4262042b4b18379373585047ce8f8938cf tx_pos: 61 value: 546 address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so confirmations: 0


Confirmed Balance: 660050868
Unconfirmed Balance: 5862

This address was found in 26 transactions and has 26 unspents.
 guessing no one yet or 26 people
6  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: March 20, 2024, 07:39:30 AM
Lets assume i have a btc wallet with no public key inside my core wallet, now i import this
one inside blockchain.com wallet, there i have the funds now, i will instantly sell these btc
coins for usd, and send my coins out there, said it, this is the way i assume all, keyfinders succes rate.

there now you have you have your coins on one of your own wallets, but now, not the forks??
i guess, or you have to do this inside the blockchain instantly with multiple windows open, but blockchain.com
prehibits this, one browser window allowed open logged in at the same time, the same you can do with the
bit of forks, but guessing the valuable btc should be enough to have there if imported,

is this not tested before, haha there this public key will not leave from your possession, untill you sell the coins
inside blockchain wallet, should be fine. i guess
7  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: February 09, 2024, 08:20:58 PM
Zahid888, is the expert at prefix searches...probably has the world's largest prefix database, he can attest to what I am saying to you.
Yes, perhaps I have the world's highest number of prefixes for puzzle66.
And maybe I have conducted the most experiments on prefixes worldwide, whether it be in the form of base58 or hash160.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.
Sometimes, a few bytes of a private key match, and at other times, they do not match at all.
So, there is no difference between a 'private keys with matched prefixes' and a 'totally random private keys'.
I save addresses with prefixes only as a 'proof of work'; beyond that, these addresses serve no further purpose.

If your objective is solely to locate addresses with matching prefixes, it would be advisable to opt for the vanity search implemented by WanderingPhilosopher, which is based on multi-GPU counting, rather than attempting to enhance speed in Python, which never ever compete with GPU-counting.

Edit :

Anyway, I have scanned about 6.5% of puzzle 66 keys individually, I need your best wishes, and a lot of good wishes from my side to all of you.

hi there,

could we get a copy? hmm if not ok, but want to try your nicely made software piece,
you have a github.. or so. anyway thanks a lot.
8  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: January 18, 2024, 08:45:32 AM
again but probably another digaran version?
really clear presentation, of it's own toughts on how to calculate this puzzle,
get it..
9  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: January 12, 2024, 01:59:50 AM
Added mod 013

https://github.com/alek76-2/VanitySearch/tree/main/mod/013

Added Path - m/0'/0'/66' For 32 BTC Puzzle

Use SSE2 instructions - default VanitySearch code / Disable SSE cmd: -nosse
Initial SEED extension to 64 bits
GPU Added rotation - #define NB_SPIN 16
Modification file GPUHash.h
The speed on the Tesla T4 GPU is 670.98 Mkeys/s
If Use GPU Rekey multiple by 1000

RUN CMD:
Code:
VanitySearch.exe -stop -nosse -verbose 1 -level 0 -t 1 -bits 66 -r 10 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

VanitySearch.exe -stop -t 0 -nosse -o Result.txt -verbose 1 -level 0 -gpu -r 500000000 -bits 66 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

Added play sound buzzer.wav in Windows version Wink

p.s. The binaries assemble everything themselves.

Bro thanks again, will test, but is it still present somewhere the bip39_english.h and Winm.lib
10  Bitcoin / Development & Technical Discussion / Re: Binary Baby Step Giant Step with lightweight database - Brute force (BSGS) on: December 12, 2023, 01:18:17 PM
sorry for jumping in and having to ask what i have to change
binary_bsgs_v1.py using this one starting at another point instead of 1 using this
"lm_upub= ice.scalar_multiplication(Add+(lm*i))"
will go for 120 bit db how to setup after 125 any help on this , mean where are you're specific scripts,
you all have your own scripts share it is care for it..
11  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 12, 2023, 12:18:22 AM
The easiest way currently known to brute force is using bit with my method applied to the different algorithms for solving the discrete logarithm.
I only ask that you mention me in your repositories, credit to whom it is deserved! Surely, those who understand the subject are secretly cooking this up, so I recommend not waiting for them (there is no need to judge them either, we are all after the same thing) . learn C, it is most likely that those repositories will come to light once it is unlikely to find a key using bits.
There are even more efficient methods, but honestly I don't want to throw all the cards at once, because I am also after some puzzle of this, I'm sorry, you can't be so generous in a world where nobody gives you anything, it's obvious, But since strength alone is of no use to me because my resources are limited, I share it so that whoever can take advantage of it.

Hi there mcdouglasx,,

how are you? could you maybe explain what parameters or lines to change for letting it search and create db with different range then this
30 bits example could you explain that would be great, gonna test after i get your explanation again, thanks man.
12  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: November 23, 2023, 02:28:33 PM
wow shit, 1632701.66 MKey/s a second, is this version available somewhere. thanks for the sharing.
btw looking like you are getting there, keep it going,

13  Bitcoin / Development & Technical Discussion / Re: My problem with btcseedrecover, I give a finder’s reward! on: November 18, 2023, 01:27:15 PM
Hi my friends,

I have a problem with the seedrecover.py file.
I have created a token list, but like mine is always displayed:  no such file or direcoty

what am I doing wrong?
I have already tested the program with other token lists. But I need my own 12 words that are all twisted.
I know all 12 words but they are all twisted.

Can someone give me an example command of how the program then rolls the dice?
address is: bc1qzgujzqeg4sht0dme6za87usp6pn2e5exhemenp

The tokenlist file is called token.txt and is located in the btcseedrecover folder.
i use a mac

i tried:  python3.9 seedrecover.py --no dupchecks --mnemonic-length 12 --language EN --dsw --wallet-type BIP39 --addr-limit 1 --addrs bc1qkccun6f65de3wq4fwnl2qfptfzd5q34gy4m2kc --tokenlist token.txt --typos 0 --transform-wordswaps 12


I give a finder’s reward!
Thanks everyone

this is what my readme says. Seedrecover_Quick_Start_Guide.md
# seedrecover.py #

*seedrecover.py* is a seed recovery tool which can take a seed with one or more mistakes in it, and recover the correct seed if not too many mistakes have been made.

## Installation ##

[Follow the installation guide here... ](INSTALL.md)

## Running *seedrecover.py* ##

In order to run *seedrecover.py*, you'll need these two things:

 * A good estimate of what your seed is, *and*

 * *One* of these four, in order of preference:
     1. for Electrum (1.x or 2.x), a copy of your wallet file (a wallet file using Electrum 2.8's new full-file encryption won't work here), *or*
     2. your master public key (sometimes called an *xpub*), *or*
     3. a receiving address that was generated by your wallet from your seed, along with a good estimate of how many addresses you created before the receiving address you'd like to use, *or*
     4. an "address database". If you don't have i., ii., or iii. from above, please see [Recovery with an Address Database](Creating_and_Using_AddressDB.md)

To start *seedrecover.py* on OS X, first rename the `seedrecover.py` script file to `seedrecover.command`. Aside from this, starting it is the same for every system: just double-click the `seedrecover.py` (or `seedrecover.command`) file.
 If you're asked about running it in a terminal, choose *Run in Terminal*. Next, you'll be asked a short series of questions:

 1. First you'll be asked to open your wallet file. If you have an Electrum wallet file, find it now - the rest of the steps will then be skipped. Otherwise, click `Cancel` to continue.

 2. Next, select your wallet type. If you're unsure of what to choose, feel free to open an [issue on GitHub](https://github.com/3rdIteration/btcrecover/issues/new) to see if your wallet software is supported.

 3. Next you'll be asked for your master public key. If you don't have yours stored anywhere, click `Cancel` to continue.

 4. If you don't have your master public key, next you'll be asked for your addresses. Find as many of your addresses associated with this wallet as you can, and enter them here (separated by spaces).
 Addresses you created early in your wallet's lifetime are prefereable. If your wallet supports multiple "accounts" each with their own address list, only addresses from your first account should be entered here.

 5. If you entered addresses above, next you'll be asked to enter the "address generation limit". *seedrecover.py* works by generating one or more addresses based on each seed it tries.
 The generation limit is the number of addresses it generates for each seed. Generating fewer addresses will improve *seedrecover.py*'s speed, however if it generates too few, it will miss the correct seed entirely.
 (If you have done something non-standard and your wallet doesn't increment from the first address, you can also specify the index that this starts counting from with the --addr-start-limit)
 
    For example, let's say you found and entered three addresses in step 4. If you're reasonably sure that all three were within the first 10 addresses ever created in your wallet, you should use `10` for the address generation limit.

Finally, you'll be asked for your best guess of what your seed is.
14  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: November 05, 2023, 11:05:27 PM
Am I understanding this correctly that you have found seed collisions? Because I see different seeds with the same key as output, or is this something else?
This is not a collision. The one that was used is saved. With the -r 1 option you can select the fastest one.
If we get lucky.  Grin

hi there,

could you make the github hold your different exe files, so we dont have to compile to test all these mods,
i could compile but am a tad late for sleeping i guess. and is this what demining mentiones just wondering

/* Magic Mersenne Twister constants */
#define N 624
#define M 397
#define MATRIX_A 0x9908b0dfUL
#define UPPER_MASK 0x80000000UL
#define LOWER_MASK 0x7fffffffUL
Technical Description CVE-2023-39910
The cryptocurrency wallet entropy filling mechanism used in Libbitcoin Explorer 3.0.0–3.6.0 is weak, also known as the Milk Sad problem.  Using the Mersenne Twister mt19937 PRNG limits the internal entropy to 32 bits regardless of settings. This allows remote attackers to recover any wallet private keys generated from the entropy results of “bxseed” and steal funds. (Affected users need to transfer funds to a new secure cryptocurrency wallet)
is this issue present still in your vanitygen, thanks for the exes.
15  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: November 04, 2023, 11:40:15 PM
this shit is sick, fast, i mean, go go nomachine we will overcome all,

52e763a7ddc1aa4fa811578c491c1bc7fd570137
generate_h160 Average Time: 0.00000000 seconds

now alek, can you send a exe to pm or github. thanks man.
16  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 12, 2023, 09:45:49 AM
hi,
you = got to use wsl, that is the dev/urandom for.,

17  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 11, 2023, 10:14:23 AM
PUZZLE SOLVED: Wed Oct 11 12:13:21 2023, total time: 13.47 sec
  • WIF:  -0000000000000000000000000000000000000000000000000022bd43c2e9354

nice catching again nomachine, is this programmable for 120th and up
18  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 06, 2023, 11:45:38 AM
Yo Nomachine,

nice catch, where's our current puzzle 66 in there,

thanks works like a charm.
19  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: September 25, 2023, 11:15:28 AM
Hello everyone, and especially those who still remember me)
Has anyone used OpenSSL to generate keys?
Probably not..

main.cpp (*Int class require some code changes within the SECP256k1 library to support BIGNUM* directly.)
Code:
#include "SECP256k1.h"
#include "Int.h"
#include <iostream>
#include <fstream>
#include <string>
#include <ctime>
#include <iomanip>
#include <sstream>
#include <thread>
#include <vector>
#include <mutex>
#include <memory>
#include <openssl/bn.h>

const int numThreads = 4; // You can adjust this number based on your CPU cores

// Function to generate a random private key using BIGNUM
BIGNUM* generateRandomPrivateKey(const BIGNUM* minKey, const BIGNUM* maxKey) {
    BIGNUM* randomPrivateKey = BN_new();
    BN_rand_range(randomPrivateKey, maxKey);

    // Ensure the generated key is within the desired range
    while (BN_cmp(randomPrivateKey, minKey) < 0) {
        BN_rand_range(randomPrivateKey, maxKey);
    }

    return randomPrivateKey;
}

// Function to convert a BIGNUM to Int
Int bignumToBigInt(const BIGNUM* bignum) {
    char* bignumStr = BN_bn2dec(bignum);
    Int bigInt;
    bigInt.SetBase10(bignumStr);
    OPENSSL_free(bignumStr);
    return bigInt;
}

// Function to generate keys and check for a specific address
void generateKeysAndCheckForAddress(BIGNUM* minKey, BIGNUM* maxKey, std::shared_ptr<Secp256K1> secp256k1, const std::string& targetAddress) {
    BIGNUM* randomPrivateKey = generateRandomPrivateKey(minKey, maxKey);

    while (true) {
        // Convert the BIGNUM private key to an Int
        Int privateKey = bignumToBigInt(randomPrivateKey);

        // Continue with the rest of the address generation and checking logic
        Point publicKey;
        std::string caddr;
        std::string wifc;

        publicKey = secp256k1->ComputePublicKey(&privateKey);
        caddr = secp256k1->GetAddress(0, true, publicKey);
        wifc = secp256k1->GetPrivAddress(true, privateKey);

        // Display the generated address
        std::string message = "\r\033[01;33m[+] " + caddr;
        std::cout << message << "\e[?25l";
        std::cout.flush();

        // Check if the generated address matches the target address
        if (caddr.find(targetAddress) != std::string::npos) {
            time_t currentTime = std::time(nullptr);

            // Format the current time into a human-readable string
            std::tm tmStruct = *std::localtime(&currentTime);
            std::stringstream timeStringStream;
            timeStringStream << std::put_time(&tmStruct, "%Y-%m-%d %H:%M:%S");
            std::string formattedTime = timeStringStream.str();

            std::cout << "\n\033[32m[+] PUZZLE SOLVED: " << formattedTime << "\033[0m" << std::endl;
            std::cout << "\033[32m[+] WIF: " << wifc << "\033[0m" << std::endl;

            // Append the private key information to a file if it matches
            std::ofstream file("KEYFOUNDKEYFOUND.txt", std::ios::app);
            if (file.is_open()) {
                file << "\nPUZZLE SOLVED " << formattedTime;
                file << "\nPublic Address Compressed: " << caddr;
                file << "\nPrivatekey (dec): " << privateKey.GetBase10();
                file << "\nPrivatekey Compressed (wif): " << wifc;
                file << "\n----------------------------------------------------------------------------------------------------------------------------------";
                file.close();
            }
        }

        // Cleanup the BIGNUM
        BN_free(randomPrivateKey);

        // Convert the max key to an Int
        Int maxInt;
        maxInt.SetBase10(BN_bn2dec(maxKey));

        if (privateKey.IsGreater(maxInt)) {
            break;
        }
    }
}

int main() {
    // Clear the console
    std::system("clear");

    time_t currentTime = std::time(nullptr);
    std::cout << "\033[01;33m[+] " << std::ctime(&currentTime) << "\r";
    std::cout.flush();

    BIGNUM* minKeyBN = BN_new(); // Initialize minKeyBN
    BIGNUM* maxKeyBN = BN_new(); // Initialize maxKeyBN

    // Configuration for the Puzzle
    // Set minKeyBN and maxKeyBN using the provided base 10 values
    BN_dec2bn(&minKeyBN, "62079069358943824031");
    BN_dec2bn(&maxKeyBN, "67079069358943924031");
    std::string targetAddress = "13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so";

    // Initialize SECP256k1
    std::shared_ptr<Secp256K1> secp256k1 = std::make_shared<Secp256K1>();
    secp256k1->Init();

    // Create threads for key generation and checking
    std::vector<std::thread> threads;

    for (int i = 0; i < numThreads; ++i) {
        threads.emplace_back(generateKeysAndCheckForAddress, minKeyBN, maxKeyBN, secp256k1, targetAddress);
    }

    // Wait for all threads to finish
    for (std::thread& thread : threads) {
        thread.join();
    }

    // Cleanup BIGNUM variables
    BN_free(minKeyBN);
    BN_free(maxKeyBN);

    return 0;
}


Yes... Grin

But it is still slow. Even 5M keys/s per core muscles is not enough for such a large range. Undecided

hi there nomachine, is there a compiled exe there.. or not. thanks man
20  Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver on: August 02, 2023, 09:02:29 PM
i guess did not even clicked it or looked at it, cause i already have used that one,
wasn't what i was looking for actually i guess, the gpu already also working so,
the code of 57fe/Pollard-Rho-Kangaroo should be ai 'ed quickly..
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!