To all other code/ECC experts
I am not an ECC expert. Some people think I am, but this is not the case. Also, when it comes to writing code, I saw many better programmers. There are people who can generate any 256-bit curve just like that, while I am still struggling with 32-bit ones. That means, I am just a beginner, compared to them.
why on earth would any of you openly and publicly help to break ECC?
My goal is not to break things, but to learn from scratch, how they were created. It is entirely different thing. Knowing that the pair (p=67,n=79) and (p=79,n=67) is the only single-byte pair that meets secp256k1 conditions (and uses a=0,b=7) is not going to help you with breaking anything. It can only help you understand, how those curves are constructed.
The main reason is the curiosity: were you never curious, how n-value was calculated for secp256k1, why "p" and "n" are different, how it was checked that those huge numbers are primes, and so on?
In case you haven't noticed, some of you are one of a kind regarding the knowledge about ECC, so don't sell yourselves short.
Do you seriously think that all of those things are hidden from the public, and some people here are revealing some secret magic, that was never known? This is clearly not the case, you have
the whole pages, where you can find integer sequences. You have even
similar pages, dedicated specifically for elliptic curves. Even more: you have
tools for generating curves on GitHub. And after seeing all of that, do you really think some random people on bitcointalk have some secret knowledge, that cannot be reached on any of those linked pages?
It is good to teach others things they don't know, but teaching has limits
Basic mathematics including combination which we learned in high school is not going to help you break ECC or solve ECDLP.
I'm not talking about this topic, I just used it as an excuse to post this.
Are you talking about this topic?
https://bitcointalksearch.org/topic/smaller-elliptic-curves-y2-x37-based-on-secp256k1-5459153Know the limits and consider the consequences.
I know the limits. And the only consequences so far, was OP trying to use brute-force to handle all of those combinations, instead of using even basic optimizations mentioned in this topic. So, calm down, we are safe.