k represents the decss c code in binary format in this video

i dont think the largest-prime-number-part of video is so relevant for our case its only k that represents code that can break or decrypt the (dvd) encryption

i think the large-prime-number part is more to do with k being 'illegal' and so is a distraction

distraction in sense that for us what is relevant is whether k exists or not whereas most of this video is about whether k was illegal or not and the ways the guy made sure the large prime could not be deemed illegal

so in relation to k my quick search on this issue is that a key was found in plain text on dvd player and so they were able to reverse engineer the encryption because it was relatively weak is 40 bits vs bitcoin 128 bits (?)

with bitcoin the cryptography is already public doesn't need to be reverse engineered it is well reviewed piece of code BUT just like in the dvd player where the implementation was shabby we have to be wary of any implementation in soft- or hardware wallet leaking our private key material or storing it in way where can be extracted

the alternative is brute forcing our private keys but my searching says that using current computation today 40 bit would take seconds while 128 bit there is not enough computational resources on earth to make that happen

so doesnt it come down to trusting an implementation of the library

say i was going to dabble in btc id generate private keys offline with sufficient entropy and make sure as best as i can they never are exposed to a network in any format

and imwoukd use open source well reviewed methods to sign transactions and all the while pay attention to other bits of advice like don't use old address types don't use single address more than once etc etc

what more can dumb pleb like me do