>>1447

If we could get the EC VQC generation code now, it would be helpful for when we figure this out.

Proof of progess: Square root of RSA100's N2's X: 2797181014427

Critical formula update following this post.

Method for generating any cell by inputing E, N, and X, and testing if actually valid to the grid as follows.

ArbitraryCell(e, n, x){

e = e;

n = n;

x = x;

a = (x * x + e) / (2 * n);

d = x + a;

b = a + 2 * (x + n);

c = a * b;

}

boolean isValid(){

return (c - d * d) == e;

}

Remember to follow the order of operations when implementing!

>>1465

I've literally done no work in (E,0). My method so far has been to take an input C, move to the home cell (E,1), then approximately jump down N. Today I'm gonna work on searching for valid cells, deriving their pattern, and unlocking the entire N column for a given E. Multithreaded, this is an insanely fast solution.

>>1466

>>1465

It's essentially turning this beautiful thing into a hammer, but it's a logarithmic hammer instead of an exponential one.

>>1467

We need a munchicus digitus pepe.

>>1476

Which stocks are most likely be impacted if RSA is broken? I'm trying to not be poor (or dead) after this.

>>1481

I don't even have enough money for food next week after rent. Would appreciate a list of ticker symbols.

>>1484

There's playing the market, and then there's being able to mathematically prove where the roulette ball is going to land…

I'm sick of working my fucking ass off to break even. This is going to happen, and we should all start to get ready.

www.pssurvival.com

>>1486

I agree with the gold and silver up sentiment. Security companies specializing in ECC as well. In terms of down, every chip credit card uses RSA. As VQC mentioned, SSL certificates use RSA. The entire online transaction market is about to be blown the fuck out. Amazon down?

>>1490

I'm in it because the implication is a new age of knowledge. At the same time, if the financial system collapses and looting starts, it's gonna be tough to pull through to the other side. This will be the lightning bolt that marks the beginning of the great storm.

Of course as soon as I start thinking about that, I run into a massive problem. For this cell in format {E:N:D:X:A:B:C},

61218444075812733697456051513875809617598014768503

4

7652305509476591712182006439234476202199751846067

3

7652305509476591712182006439234476202199751846064

7652305509476591712182006439234476202199751846078

58557779610365799850575360231375488434617810249426155485106497416876136614796334204692772478136992

This should absolutely not pass isValid, but it does… Hmmmm….

Well, either the isValid method is incomplete, or my method of generating an arbitrary cell is flawed. Back to square N+1.

>>1499

That's what I was using, but I think I've found a solution. The generate arbitrary cell function can be tweaked to further distort invalid data.