5.3.05.3.05.3.05.3.05.3.0

cacke -> cache

rebase

improve error message some more

improve error message some more

better error message if the lib is not available at all

rebase after squashing D16706 with previous diffs

rebase

dedup

move secp256k1_schnorr_* declarations to secp256k1 where it belongs, raise a meaningful error if the lib is missing the schnorr module, remove some extra try: except: wrapping in secp256k1.py so that the inner errors are raised with more precise error messages

@bot electrum-functional-tests

resbase

rebase

rebase

rebase

rebase

rebase

rebase

replace a few 32's with PRIVATE_KEY_BYTECOUNT, clarify legacy use for arbitrary size secret

In D16681#378434, @bytesofman wrote:

still not able to arc patch this one, which could mean we see issues when it is landed. may want to wait until this is next off the rank.

did points at infinity or not on curve not being properly handled impact app performance? why was this not handled before this diff?

In D16676#378433, @bytesofman wrote:

I can't get the test plan to pass but I'm also not sure it's really an issue.

rebase

rebase

rebase

I'm not sure exactly what is going on. I will try to rebase all these diffs onto D16687 when I get it sorted out. Hopefully it will fix the situation. I could just rebase everything onto master after I land any diff in the stack, but that would be tedious and noisy in the phabricator logs for a stack of 10+ commits.