One of the component of making of SECP256K1 signatures, is a random number that is later multiplied by the generator point in order to be used in further computations.
If we imagine that k - is the random nonce number and G - is the generator point, then:
What's the length of k (random number), in bytes, bits?
However, I am trying to find the answer in the Bitcoin core source code, but it's kind of hard to read and could find an answer to it there.
/* Generate an ECDSA signature `noncefp` and `ndata` allows you to pass a * custom nonce function, passing `NULL` will use the RFC-6979 safe default. * Signing with a valid context, verified secret key * and the default nonce function should never fail. */ return_val = secp256k1_ecdsa_sign(ctx, &sig, msg_hash, seckey, NULL, NULL); assert(return_val);
I am not sure where is k located in the code.
Also curious about other things:
Has anyone successfully replicated, mimicked the k for signatures, where k is not known?
Has anyone successfully "mined", or brute forced a k for signatures?
Is it possible to brute force the k by randomly generating random number with the function/algorithm being implemented in bitcoin core? (I suppose it is RFC-6979 or something)