Bitcoin addresses starting with 1 are P2PKH addresses. This is a recipe for building a P2PKH lock script.

That is, an address is a prefix followed by a hash of the public key, followed by a checksum. All you need here is a valid prefix, a random bunch of visible bytes, and a correct checksum. So it’s perfectly feasible simply by selecting a bundle of bytes that is the ASCII encoding of the statement, pretending to be a public key hash, and calculating the required checksum.

It doesn’t matter that bytes that should be hashs are not public key hashs, as they will not construct an unlock script using the corresponding private key.

There’s no way to tell if that’s the case Any Unused P2PKH addresses are fake or actually fake or real until you post an unlock script that can be checked against the lock script.

“Fake” means nothing more than arriving in the usual way other than building a private and public key pair.

I’ve been following topics that interest me and have tried them for a few days, but I can’t!

I know it’s easy to retrieve from a P2PKH transaction. There are various tools that can do that and their behavior.

But I’m trying to get the r, s, z values ​​from a Segwit Transactionsbut I can’t do that.

Some Python scripts failed to achieve my goal, so I wanted to ask if anyone here has a solution to get R, S, Z values ​​from a Segwit transaction.

Edit: 2025/02/18 I have something wrong with the transaction and I don’t have any random numbers (k=nounce) created, but I think some transactions use the same R value, so I need to add the following There is. This means you can calculate the private key using r, s, z!

Now I want to check my transactions, but those are my transactions I have done in the last 3 years!

I just want to make sure my assumption that R is used twice is wrong!

In a segwit transaction, the value of r, s is only “only” required to calculate the private key.

I already know how to get R,S!