Bitcoin puzzle transaction ~32 BTC prize to who solves it

[kTimesG]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

[username666187]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

[Grzegorz2022]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

You think everyone here doesn't have the same information you're talking about while you insult others?! You're wrong, and badly wrong. Some of us here have more information than you and your ChatGPT combined. I mentioned it earlier and I'll repeat it learn to code without asking others to do it for you, then conduct your own research, and when you discover something and want to share it, then write. You keep posting the same things over and over, or things we already know. The problem is you probably haven't tested them individually or tried combining them. You talk about double speed, what speed? Do you have it? Then demonstrate your algorithm by showing all of us how you use what you're talking about and what results you get, instead of writing ChatGPT scripts or things we already know while insulting people here. You grow up, and stop spamming. If you have something to show, show it. If you want to ask something, ask. But don't try to convince anyone of things you don't understand yourself

[collardelay]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

You think everyone here doesn't have the same information you're talking about while you insult others?! You're wrong, and badly wrong. Some of us here have more information than you and your ChatGPT combined. I mentioned it earlier and I'll repeat it learn to code without asking others to do it for you, then conduct your own research, and when you discover something and want to share it, then write. You keep posting the same things over and over, or things we already know. The problem is you probably haven't tested them individually or tried combining them. You talk about double speed, what speed? Do you have it? Then demonstrate your algorithm by showing all of us how you use what you're talking about and what results you get, instead of writing ChatGPT scripts or things we already know while insulting people here. You grow up, and stop spamming. If you have something to show, show it. If you want to ask something, ask. But don't try to convince anyone of things you don't understand yourself

Couldn't have said it better myself. No need for the disrespectful language. Post your facts and attach relevant evidence or theoretical proof.

[username666187]

Lol your calling ME disrespectful and insulting ? Lmfao  🤣🤣🤣

Lol yea thats what happens when you intentionally insult and disrespect someone they get offended and starg insulting you back what makes it even more humiliating is when the return insults still have value that can logically be directly related to the subject by using correct information providing intelligible replies that if interpreted maturely is still useful even though that information was delivered in an insulting way with a disrespectful tone and a superior demeanor

You say you already know what im talking about then you tell me to show you how to do it then you tell me i dont know anything then use the words like i probly dont or i cant or i dont know anything  then you again ask me to show you how it works after trying to tell me that you know more information than me and that you know how it works better than me

Make yourself make sense

What is "it" big dawg if you already know it then why are you arguing about it and if you dont why are you saying that you do and telling me i dont you set yourself up to look stupid and unintelligible i litterally dont know how i could answer your question when you havent even referenced what subject

If you are saying that i am WRONG that is perfectly ok as long as you can actually point out exactly what im wrong about and give a logical reasoning of where or why im wrong instead of just the average preteen psychobabble

But hey maybe some people just learn by making themselves look so stupid and use insults to draw more information from people while making sure theyre ego stays went and wanting like a princess at a pucker party

[SecretAdmirere]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

No need for such a offensive language... It's out of line, complitely, regardless if someone is right or not, in this case you are simply wrong.

It is true that GLV spliting let's you speed up computation of k*G, but it's not true and usefull for this specific case (challenge addresses, bruteforcing for a private key).. kTimesG explained to you very well, "Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar."

Simply, most basic interpertation: you compute once private key -> public key and that is it, no more k*G needed, after you do point addition, adding points whitin elliptic curve space, once you added enough points and you get a match, private key recovery is simple, you know how many times you added points on the starting point aka starting private key, private key space and public key space corelate 1:1 with each other. Private key 1 -> 1*G, you add on it 20*G, that is 21*G that = private key 21.

That is it, that is the most efficient way, no way around it. And only speed up you can get is purely how effective your gpu computes, less gpu instructions = faster execution. Better and faster multiplication, squaring, subtraction. Inversion that is armortised over 512 points becomes basicly free. If you want speed, write a better multiplication on a gpu, that calculates "256*256 -> reduction" in least amount of instructions. Simple, but complicated. Kangaroo, BSGS, what ever else there is, is simply a mathematical shortcut that reduce required amount of operations needed to get to the solution, none applicable to addresses that don't have exposed public key. Both have their pros and cons, and they simply solve the problem "this is exposed public key that is located within A and B, pick a private key(compute k*G to get public key) within that search space and find where stepping from private key(compute k*G to get public key) crosses steping from exposed public key".. Or if you wish to break Secp256k1 curve, find a "better shortcut", of the said problem, that requires less operations.

[Grzegorz2022]

Lol your calling ME disrespectful and insulting ? Lmfao  🤣🤣🤣

Lol yea thats what happens when you intentionally insult and disrespect someone they get offended and starg insulting you back what makes it even more humiliating is when the return insults still have value that can logically be directly related to the subject by using correct information providing intelligible replies that if interpreted maturely is still useful even though that information was delivered in an insulting way with a disrespectful tone and a superior demeanor

You say you already know what im talking about then you tell me to show you how to do it then you tell me i dont know anything then use the words like i probly dont or i cant or i dont know anything  then you again ask me to show you how it works after trying to tell me that you know more information than me and that you know how it works better than me

Make yourself make sense

What is "it" big dawg if you already know it then why are you arguing about it and if you dont why are you saying that you do and telling me i dont you set yourself up to look stupid and unintelligible i litterally dont know how i could answer your question when you havent even referenced what subject

If you are saying that i am WRONG that is perfectly ok as long as you can actually point out exactly what im wrong about and give a logical reasoning of where or why im wrong instead of just the average preteen psychobabble

But hey maybe some people just learn by making themselves look so stupid and use insults to draw more information from people while making sure theyre ego stays went and wanting like a princess at a pucker party

I'm not going to correct you or bring you down to earth every time. Since you're so eloquent, be that intelligent and start doing your own research instead of listening to ChatGPT. Convince yourself the way we convinced ourselves. If you think I or anyone else here is going to tell you about our own work, research, and how things connect you're wrong. I told you earlier you have your method, ask your magical ChatGPT to write you the code.
As for your claim about GLV it's true only in one scenario: single multiplication! If you had run more tests instead of sitting with ChatGPT, you'd know what this is about.
You say GLV gives 2× speed in brute-force. And I'm telling you now point addition is ~192× faster than GLV scalar multiplication. Show us your code and results instead of theory. Until you show that, it's just talk like your ChatGPT. I said earlier, you contribute nothing but spam and insulting people here. I'm surprised the moderator doesn't react to this. Nobody wants anything from you you're the one making up stories for yourself.
If you show up here being so confident in what you're saying, prove it to the community. Simple. If you think you can throw out various methods from ChatGPT and find someone to write code for you, then something's really wrong with you. What you're showing we already know. Many of us have been through it without posting nonsense on forums, just testing. And anyone who knows the subject, seeing the posts you make, knows you're way behind.

[username666187]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

No need for such a offensive language... It's out of line, complitely, regardless if someone is right or not, in this case you are simply wrong.

It is true that GLV spliting let's you speed up computation of k*G, but it's not true and usefull for this specific case (challenge addresses, bruteforcing for a private key).. kTimesG explained to you very well, "Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar."

Simply, most basic interpertation: you compute once private key -> public key and that is it, no more k*G needed, after you do point addition, adding points whitin elliptic curve space, once you added enough points and you get a match, private key recovery is simple, you know how many times you added points on the starting point aka starting private key, private key space and public key space corelate 1:1 with each other. Private key 1 -> 1*G, you add on it 20*G, that is 21*G that = private key 21.

That is it, that is the most efficient way, no way around it. And only speed up you can get is purely how effective your gpu computes, less gpu instructions = faster execution. Better and faster multiplication, squaring, subtraction. Inversion that is armortised over 512 points becomes basicly free. If you want speed, write a better multiplication on a gpu, that calculates "256*256 -> reduction" in least amount of instructions. Simple, but complicated. Kangaroo, BSGS, what ever else there is, is simply a mathematical shortcut that reduce required amount of operations needed to get to the solution, none applicable to addresses that don't have exposed public key. Both have their pros and cons, and they simply solve the problem "this is exposed public key that is located within A and B, pick a private key(compute k*G to get public key) within that search space and find where stepping from private key(compute k*G to get public key) crosses steping from exposed public key".. Or if you wish to break Secp256k1 curve, find a "better shortcut", of the said problem, that requires less operations.

Thank you and i agree the language was uncalled for i failed to realize that just because i was offended is not an excuse to be vitrol or voulger i accept that and will take that constructively

That being said the glv method allows you to use the both the public key and the inverse or negative public key which allows you two public keys to search for meaning now you can check two private keys at a time because using it correctly if you find one of them you can calculate the other which when you pair that with kangaroo gives you a much higher than just double collision chance greatly increasing your chances and when you use parallel computing with cuda your gains grow exponentially

[Grzegorz2022]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

No need for such a offensive language... It's out of line, complitely, regardless if someone is right or not, in this case you are simply wrong.

It is true that GLV spliting let's you speed up computation of k*G, but it's not true and usefull for this specific case (challenge addresses, bruteforcing for a private key).. kTimesG explained to you very well, "Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar."

Simply, most basic interpertation: you compute once private key -> public key and that is it, no more k*G needed, after you do point addition, adding points whitin elliptic curve space, once you added enough points and you get a match, private key recovery is simple, you know how many times you added points on the starting point aka starting private key, private key space and public key space corelate 1:1 with each other. Private key 1 -> 1*G, you add on it 20*G, that is 21*G that = private key 21.

That is it, that is the most efficient way, no way around it. And only speed up you can get is purely how effective your gpu computes, less gpu instructions = faster execution. Better and faster multiplication, squaring, subtraction. Inversion that is armortised over 512 points becomes basicly free. If you want speed, write a better multiplication on a gpu, that calculates "256*256 -> reduction" in least amount of instructions. Simple, but complicated. Kangaroo, BSGS, what ever else there is, is simply a mathematical shortcut that reduce required amount of operations needed to get to the solution, none applicable to addresses that don't have exposed public key. Both have their pros and cons, and they simply solve the problem "this is exposed public key that is located within A and B, pick a private key(compute k*G to get public key) within that search space and find where stepping from private key(compute k*G to get public key) crosses steping from exposed public key".. Or if you wish to break Secp256k1 curve, find a "better shortcut", of the said problem, that requires less operations.

Thank you and i agree the language was uncalled for i failed to realize that just because i was offended is not an excuse to be vitrol or voulger i accept that and will take that constructively

That being said the glv method allows you to use the both the public key and the inverse or negative public key which allows you two public keys to search for meaning now you can check two private keys at a time because using it correctly if you find one of them you can calculate the other which when you pair that with kangaroo gives you a much higher than just double collision chance greatly increasing your chances and when you use parallel computing with cuda your gains grow exponentially

Seriously?, stop using that AI. What you're saying is again a half-truth true in theory, but in practice and application it's not how you wrote it and read it from the chat. Start working and you'll understand. I'm already losing the desire to reply to your posts, and soon the rest will lose it too, and you'll be left alone with your little magician.

[username666187]

Again what are you talking about ? You still dont say what doesnt work or why and why do you keep assuming what i know and dont know or how or where i learned it dude just because somebody else knows something that you dont know yet does not make them wrong and just because you cant understand something enough to elaborate on it  does not make it non sense it just shows that you yourself are nonsensical maybe you should do some research on what im talking about find out if its viable or not for yourself then reply with an educated argument or better understanding

Just because you think your right does not mean i am wrong

[username666187]

🤣 Dude its for when you know the public key you get twice the vectors and double the chance of a collision

Wait please tell me people here are not wasting theyre time using kangaroo or pollards or jean luc pons on keys with only the address because god damn if so that is a special kind of stupid and just proves my point that this is the fucking kiddy pool and your right i need to go back to the grown ups to have a decent conversation

Yes, you should do that, instead of posting non-sense. No, having the public key does not double anything up. GLV is simply an efficient computational optimization of a k*G operation, and has nothing to do with either brute-force, Kangaroo, or BSGS, as it does not simplify anything on any of those front-ends.

Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar.

Yes, you have much to learn. Maybe not via LLM though, unless you want to become the dumb idiot you think the rest of us (not using AI) are.

You stupid dumb fuck do you even know what brute force searching is? Its computing candidate PRIVATE KEYS  trying to find a match the GLV method lets you COMPUTE PRIVATE KEY 2 TIMES FASTER! Double the speed fucking know what your talking about before speaking you fucking moron k*g is exactly what an efficient search optimizes van oorschot weiner makes it even better because now were doing that same thing in parallel you fucking ignorant uneducated simpleton if you are just fucking with me it still doesnt change the fact that even with the best optimizations you have at your disposal you dont have the key or know how to get it you just keep telling me im correct and verify what im saying in the most stupidest sounding way possible your just embarrassing yourself at this point grow the fuck up and actually pay attention to what your saying

No need for such a offensive language... It's out of line, complitely, regardless if someone is right or not, in this case you are simply wrong.

It is true that GLV spliting let's you speed up computation of k*G, but it's not true and usefull for this specific case (challenge addresses, bruteforcing for a private key).. kTimesG explained to you very well, "Optimizing k*G is irelevant to either Puzzle 71 or 135, since neither of those kind of puzzles actually require computing more than one, initial, starting public key from a known scalar."

Simply, most basic interpertation: you compute once private key -> public key and that is it, no more k*G needed, after you do point addition, adding points whitin elliptic curve space, once you added enough points and you get a match, private key recovery is simple, you know how many times you added points on the starting point aka starting private key, private key space and public key space corelate 1:1 with each other. Private key 1 -> 1*G, you add on it 20*G, that is 21*G that = private key 21.

That is it, that is the most efficient way, no way around it. And only speed up you can get is purely how effective your gpu computes, less gpu instructions = faster execution. Better and faster multiplication, squaring, subtraction. Inversion that is armortised over 512 points becomes basicly free. If you want speed, write a better multiplication on a gpu, that calculates "256*256 -> reduction" in least amount of instructions. Simple, but complicated. Kangaroo, BSGS, what ever else there is, is simply a mathematical shortcut that reduce required amount of operations needed to get to the solution, none applicable to addresses that don't have exposed public key. Both have their pros and cons, and they simply solve the problem "this is exposed public key that is located within A and B, pick a private key(compute k*G to get public key) within that search space and find where stepping from private key(compute k*G to get public key) crosses steping from exposed public key".. Or if you wish to break Secp256k1 curve, find a "better shortcut", of the said problem, that requires less operations.

Thank you and i agree the language was uncalled for i failed to realize that just because i was offended is not an excuse to be vitrol or voulger i accept that and will take that constructively

That being said the glv method allows you to use the both the public key and the inverse or negative public key which allows you two public keys to search for meaning now you can check two private keys at a time because using it correctly if you find one of them you can calculate the other which when you pair that with kangaroo gives you a much higher than just double collision chance greatly increasing your chances and when you use parallel computing with cuda your gains grow exponentially

Seriously?, stop using that AI. What you're saying is again a half-truth true in theory, but in practice and application it's not how you wrote it and read it from the chat. Start working and you'll understand. I'm already losing the desire to reply to your posts, and soon the rest will lose it too, and you'll be left alone with your little magician.

A half truth in theory is a full improvement in application and of course you still use point addition but with glv you now have two points to work with

Also                                are you saying you know more than ai?¿        Because........

[kTimesG]

Just because you think your right does not mean i am wrong

Jesus Christ. You are not wrong, you are dead wrong. You might also need help, you will not find therapists here though. Maybe just moderators.

There is no need to compute k*G to get to the next desired pubKey or address, no matter if you need to compute k+1 * G or k+512 * G or whatever other step/delta some algorithm requires. Neither in brute-force, Kangaroo, or BSGS.

This has been explained to you in great detail by me and others.

Why can't you grasp this, but still "you can do math all day", while what has been explained to you is a basic math principle in elliptic curve theory, not a coding thing?

All your ramblings about optimizations are pure crap, they do not exist. GLV is only useful for fast ECDSA signature verifications, and general point scalar-multiplication. Neither of these things are relevant to any puzzles.

GLV is also irrelevant to k*G multiplication itself because G is constant and there are much better optimizations then GLV to compute k*G.

GLV is only useful/efficient when you have a random point P and you want it multiplied. Capisci? That is, ECDSA verification, where you need to do multiplication of signature's public key, which is not the G point.

Your other rambling about point inverses is:

1. Totally irrelevant and inapplicable to GLV since GLV only works with scalars, not points.
2. Well known for decades and already implemented in most serious software.

Now, go to sleep, drink some tea, and go to a doctor for a prescription.

[Grzegorz2022]

Again what are you talking about ? You still dont say what doesnt work or why and why do you keep assuming what i know and dont know or how or where i learned it dude just because somebody else knows something that you dont know yet does not make them wrong and just because you cant understand something enough to elaborate on it  does not make it non sense it just shows that you yourself are nonsensical maybe you should do some research on what im talking about find out if its viable or not for yourself then reply with an educated argument or better understanding

Just because you think your right does not mean i am wrong

And that's exactly the point you know nothing! Anyone who knows the subject and goes through your posts will say the same thing. First you started with your magical method that you kept so secret, then you begged for someone to write you code, then your next posts were information already known for a decade, and now you're at the stage of convincing everyone here that these methods work in every way.

You know what I'll tell you at the end, because this is my last reply to you, and I hope the rest stop replying to you too then you'll get bored. That second point you can shove it... You're a rookie who grabs information and interprets it beyond the norm. I wish you good luck, and stop trashing the forum. If you can, write something concrete here, because the information you're posting is publicly available and you contribute nothing with it. If you were showing and talking about your own work or results, I wouldn't have said a bad word, but you're just spamming. Good luck

[And24r]

Grzegorz2022. Help me solve one problem. And I’ll share with you how to solve this puzzle. I asked you in message 13367

[Grzegorz2022]

Grzegorz2022. Help me solve one problem. And I’ll share with you how to solve this puzzle. I asked you in message 13367

We've already translated this. It won't work the way you think. secp256k1 is secp256k1 if you modify this curve, you get a different one. What you're working on won't work. I'm not stopping you, but I'm definitely not going to sit through this again. I've already been through it in my own work. I also have certain problems with my current work, but I'm trying to solve them on my own.

[And24r]

Grzegorz2022. Help me solve one problem. And I’ll share with you how to solve this puzzle. I asked you in message 13367

We've already translated this. It won't work the way you think. secp256k1 is secp256k1 if you modify this curve, you get a different one. What you're working on won't work. I'm not stopping you, but I'm definitely not going to sit through this again. I've already been through it in my own work. I also have certain problems with my current work, but I'm trying to solve them on my own.

You don’t know all my plans. I’m not going to derive a private key from the curve y^2=x^3. I need this curve for another task. If you help me, you won’t regret it.