This would not be up to specification, although non compliant bitcoin clients are functionally transparent (unless they reuse `k`, in which case your funds will

This would not be up to specification, although non compliant bitcoin clients are functionally transparent (unless they reuse `k`, in which case your funds will be quickly drained): https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch06.asciidoc#the-importance-of-randomness-in-signatures https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch06... To avoid this vulnerability, the industry best practice is to not generate k with a random-number generator seeded with entropy, but instead to use a deterministic-random process seeded with the transaction data itself. This ensures that each transaction produces a different k. The industry-standard algorithm for deterministic initialization of k is defined in RFC 6979, published by the Internet Engineering Task Force. > If you are implementing an algorithm to sign transactions in bitcoin, you must use RFC 6979 or a similarly deterministic-random algorithm to ensure you generate a different k for each transaction. (https://datatracker.ietf.org/doc/html/rfc6979 https://datatracker.ietf.org/doc/html/rfc6979)