I'm on it, but maybe some hint?

Okey I'll try to figure out?

Sadly this is the last minigame QAQ

I'm new to cryptography, just started playing ctf challenges and such about a year ago, so excuse me if this comes out a bit stupid   

But from what I understood, the Signature is the message above signed with the wallet's private key. But isn't that just a way to prove that the private key corresponds to the publicly known private key? if so how is that different from bruteforcing the private key itself from the known keyspace?

Again, thanks for the challenge dude, and sry if this question came out a bit dumb xd

Hello, man. Well, I'll try my luck with this puzzle.

The main vulnerability of signatures is the use of the same value of K, which gives the same value of r.
for the first message the values ​​of r and s were:
r 0xde97092bfb7c02148a827b4f8b62db1e189a739c77815799df5e6fb35ae88a1f
s 0x3f4fa38bcbb17615446fabc6fbebceefbb7d052eca9ce136b3a4a67b7f0d4f42
for the second message the values ​​of r and s were:
r 0x838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc
s 0x288da41a03e78a23e2ac277921e2d19d17717a27a10f1c6cca7fd5ba351a5fca
I don't see the same r values ​​here, maybe I'm being stupid.

The public is is already exposed, and if you're sure you've found the private key (which would be obvious because is has 126 0 at the end) you would've probably cached out by now 

yep just saw it

Now yes, I liked it, a difficult puzzle lol, don't give any more tips to this bunch of parasitic worms, no @
RetiredCoder

2 most common vulnerabilities are repetitions of K for the same private key and weak K
We have only 2 signed messages and their signature r does not match, only the weak K remains.
I checked 02/03838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc in the 80-bit range it is not there.
sha256 from the message also does not reveal r, as well as double hashing.
The rabbit hole is too deep. I'm tired))