user121477: There has never been a remittance history to this address.
https://www.blockchain.com/btc/address/1JqPFnGPhHhy54zJKmC1MPiczzgFjCmzE9
public key : 02f51f8d0c4dc4a5338bef745098e6f6364f8936fee6aa5a9d4ab0c214e7cdd727
It has a balance of 340 bitcoins.
I am not the owner of this bitcoin.
However, you can create a transaction with only the public key.
I can make this kind of transaction infinite.
You can check the rsz value with this program.
https://github.com/Sean-Bradley/ECDSA_secp256k1_JordonMatrix_nodejs/blob/master/getPubKeyFromRSZ.py

R = 0xf8eb13edf4663f68fe635bdd7222c79d964099b4bb7595a53e1c22f988c1cfa2
S = 0xd83fd6c056a6eae6f76c492f7791fdb83336a5b796aa95656159e161cf1d03bc
Z = 0x72ee6ef84536396d0b655396281876a81cd998bb27dde49171785a6c4c45e6e7
R = 0xb4684517444a86cbc7a11eeda7aea984755dbb624d57907f09dcc4e47bd648cd
S = 0xcdffc4fb64e5acd079b2c3de7c8c122a7a4cdfb9f70cc02eef54452bbf5e7b82
Z = 0x873b1235044c5b38a24cfa941cb6347ba6038771d54b672e03d812fc291dffa2
R = 0x4e3a352bd5f7598ddf580f5e2181ea3faf33e8186dff84aa462d90b3b37e7371
S = 0xaad1fce91c3326b6ad8dc1c0a0d41625ec23b97f4f50092d94b36f22b3c1122d
Z = 0x8625e67ceca36f11d315be232fe86bef50c4d8a6bcf9fc4adb7120fb671bc827
R = 0xd875063a0b9e9aa30d58f8ac3e39d1f6695a5d04deea0a8f1d6dcbc96a3a3d22
S = 0xbe27760132ba69321cb938ab931fd78ce9c944644505b48ae170e8171ccfe761
Z = 0xdeead39249eb7d02856de81723d193727a599db0a156dbf5bff60427d17f5a95
R = 0x29e690606edf3d7dc5b2e4f83c2c7ea8924cb0911792514c1912789cc3dde563
S = 0xc7722f325ce71add08eb51e9edfae276d9c164d298d8355c6cf75359e5cf7eb3
Z = 0x5c7abfcb68f3e4d0320c760a8430a52c90d8c2ee3795878b0b308bfaa310082f

user5406: Yes, finding bugs in Bitcoin would be valuable. However this doesn't seem to be one.
What's shown here is a series of supposed "signatures". However, a cryptographic signature is only meaningful in the context of the message it signs. To verify a signature, you need three inputs: 1) the message, 2) the signature, 3) the public key. Generating a "signature" that seems to correspond to a public key is trivial if it doesn't need to match a message, but they cannot be validated without a corresponding message.
To create a Bitcoin transaction, you need to sign a specific message, namely the transaction's signature hash. If you could do that, that would be a problem, however, that's not what you've shown here.

121477: <p>There has never been a remittance history to this address.
<a href="https://www.blockchain.com/btc/address/1JqPFnGPhHhy54zJKmC1MPiczzgFjCmzE9" rel="nofollow noreferrer">https://www.blockchain.com/btc/address/1JqPFnGPhHhy54zJKmC1MPiczzgFjCmzE9</a>
public key : 02f51f8d0c4dc4a5338bef745098e6f6364f8936fee6aa5a9d4ab0c214e7cdd727</p>
<p>It has a balance of 340 bitcoins.
I am not the owner of this bitcoin.
However, you can create a transaction with only the public key.
I can make this kind of transaction infinite.</p>
<p>You can check the rsz value with this program.</p>
<p><a href="https://github.com/Sean-Bradley/ECDSA_secp256k1_JordonMatrix_nodejs/blob/master/getPubKeyFromRSZ.py" rel="nofollow noreferrer">https://github.com/Sean-Bradley/ECDSA_secp256k1_JordonMatrix_nodejs/blob/master/getPubKeyFromRSZ.py</a>
<a href="https://i.stack.imgur.com/h9yQp.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/h9yQp.jpg" alt="enter image description here" /></a></p>
<p>R = 0xf8eb13edf4663f68fe635bdd7222c79d964099b4bb7595a53e1c22f988c1cfa2
S = 0xd83fd6c056a6eae6f76c492f7791fdb83336a5b796aa95656159e161cf1d03bc
Z = 0x72ee6ef84536396d0b655396281876a81cd998bb27dde49171785a6c4c45e6e7</p>
<p>R = 0xb4684517444a86cbc7a11eeda7aea984755dbb624d57907f09dcc4e47bd648cd
S = 0xcdffc4fb64e5acd079b2c3de7c8c122a7a4cdfb9f70cc02eef54452bbf5e7b82
Z = 0x873b1235044c5b38a24cfa941cb6347ba6038771d54b672e03d812fc291dffa2</p>
<p>R = 0x4e3a352bd5f7598ddf580f5e2181ea3faf33e8186dff84aa462d90b3b37e7371
S = 0xaad1fce91c3326b6ad8dc1c0a0d41625ec23b97f4f50092d94b36f22b3c1122d
Z = 0x8625e67ceca36f11d315be232fe86bef50c4d8a6bcf9fc4adb7120fb671bc827</p>
<p>R = 0xd875063a0b9e9aa30d58f8ac3e39d1f6695a5d04deea0a8f1d6dcbc96a3a3d22
S = 0xbe27760132ba69321cb938ab931fd78ce9c944644505b48ae170e8171ccfe761
Z = 0xdeead39249eb7d02856de81723d193727a599db0a156dbf5bff60427d17f5a95</p>
<p>R = 0x29e690606edf3d7dc5b2e4f83c2c7ea8924cb0911792514c1912789cc3dde563
S = 0xc7722f325ce71add08eb51e9edfae276d9c164d298d8355c6cf75359e5cf7eb3
Z = 0x5c7abfcb68f3e4d0320c760a8430a52c90d8c2ee3795878b0b308bfaa310082f</p>
 5406: <p>Yes, finding bugs in Bitcoin would be valuable. However this doesn't seem to be one.</p>
<p>What's shown here is a series of supposed &quot;signatures&quot;. However, a cryptographic signature is only meaningful in the context of the message it signs. To <a href="https://cryptobook.nakov.com/digital-signatures/ecdsa-sign-verify-messages#ecdsa-verify-signature" rel="nofollow noreferrer">verify a signature</a>, you need three inputs: 1) the message, 2) the signature, 3) the public key. Generating a &quot;signature&quot; that seems to correspond to a public key is trivial if it doesn't need to match a message, but they cannot be validated without a corresponding message.</p>
<p>To create a Bitcoin transaction, you need to sign a specific message, namely the transaction's signature hash. If you could do that, that would be a problem, however, that's not what you've shown here.</p>
