Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: COBRAS on August 17, 2020, 11:56:18 AM



Title: Private key hack new method
Post by: COBRAS on August 17, 2020, 11:56:18 AM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]

[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???


Title: Re: Private key hack new method
Post by: AB de Royse777 on August 17, 2020, 12:05:09 PM
So the plan is, today or tomorrow you are going to get everyone's private keys and will steal the coins?
I am moving my coins to fiat :-P


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 12:09:29 PM
So the plan is, today or tomorrow you are going to get everyone's private keys and will steal the coins?
I am moving my coins to fiat :-P

Maybe you need move all yors coin to fiat many days ago.

Look at this site - https://privatekeys.pw/bitcoin/keys/2573157538607026564968244111304175730063056983979442319613448069811514699875

All private keys was hacked, or many many of them !!! Seea a site, max posible privkey is a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141 and on last page of privatekeys.pw you can see this private key  :o

Plan is a education  only !!!

p.s. if your coin not hacked now, I think privatekeys.pw not find your privkey.


Title: Re: Private key hack new method
Post by: TheArchaeologist on August 17, 2020, 12:18:14 PM
Look at this site - https://privatekeys.pw/bitcoin/keys/2573157538607026564968244111304175730063056983979442319613448069811514699875

All private keys was hacked, or many many of them!
I know you are still in the "I want to believe phase" but once again I am the bearer of bad news. None of the private keys on that site are hacked in a way they only had a public key and somehow calculated the private key out of it. All the endless dumps on that site are non-random inputs used for private keys.

The process from there on out is:
Private Key -> Public Key -> encoded as an address.



Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 12:19:10 PM
Someone who know mathematics please help  :'(


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 12:21:33 PM
Look at this site - https://privatekeys.pw/bitcoin/keys/2573157538607026564968244111304175730063056983979442319613448069811514699875

All private keys was hacked, or many many of them!
I know you are still in the "I want to believe phase" but once again I am the bearer of bad news. None of the private keys on that site are hacked in a way the only had a public key and somehow calculated the private key out of it. All the endless dumps on that site are non-random inputs used for the private keys.

The process from there on out is:
Private Key -> Public Key -> encoded as an address.



In my start post I was show a private key -base point-public key and address with 1000 BTC. :o If someine know math, he can make all around from him very very happy.


Title: Re: Private key hack new method
Post by: TheArchaeologist on August 17, 2020, 12:21:50 PM
Someone who know mathematics please help  :'(
I'm sure you can hire one know that you know how to hack every private key in existence!

/s


Title: Re: Private key hack new method
Post by: TheArchaeologist on August 17, 2020, 12:22:37 PM
In my start post I was show a private key -base point-public key and address with 1000 BTC. :o
Well you have the private key, go sweep the 1000 BTC then.


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 12:25:17 PM
In my start post I was show a private key -base point-public key and address with 1000 BTC. :o
Well you have the private key, go sweep the 1000 BTC then.

This private key for different base point !!! Need someone who can make a code for find privkey for legit base point this info about this modified base point, and legit private key for this modified base point.

With 500 BTC any of us can be a king of some African country. Yes, if someone disappointed, and not thant get any btc from block chain this is mistake for future all life for him. So, lets make a code and go, Brothers !!!!   I can provide more examples of privkey+basepoint+pubkey's !!!


Title: Re: Private key hack new method
Post by: TheArchaeologist on August 17, 2020, 12:35:12 PM
Ok, I have a super-secret 1337 calculation because I'm a math guru. So you see, someone provided me with this uncompressed public key:

Code:
041a87e4688d8b9445b5b038cb3b34c186331f1ab4fc0822dcca44192043eab3b7accf8e941f95ae80b8f373229b7a3f83144160d8982e648f60c8e5cb968ec72e

Now when running my base-point calculator (tm) for 10 minutes it came back with the calculated private key:
Code:
Private key calculated: 20536951ACC1F347F922E64A62AEC1CE3B73F038A99CB9D56F3D313F2F8CAAC5
Address found: 1BoatSLRHtKNngkdXEeobR76b53LETtpyT
So this is what you are looking for?


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 12:48:31 PM
Ok, I have a super-secret 1337 calculation because I'm a math guru. So you see, someone provided me with this uncompressed public key:

Code:
041a87e4688d8b9445b5b038cb3b34c186331f1ab4fc0822dcca44192043eab3b7accf8e941f95ae80b8f373229b7a3f83144160d8982e648f60c8e5cb968ec72e

Now when running my base-point calculator (tm) for 10 minutes it came back with the calculated private key:
Code:
Private key calculated: 20536951ACC1F347F922E64A62AEC1CE3B73F038A99CB9D56F3D313F2F8CAAC5
Address found: 1BoatSLRHtKNngkdXEeobR76b53LETtpyT
So this is what you are looking for?


But with my base point this is anower address

Bro, my pubkey is 045ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae138a03820dcda0 c431bf15f4fe897d36c5053981610b20e1699853a00b3248154

base point for key is

FakBase point (6733679609719187550322383620907876677281311728966538016392101299397377628245 : 96032098930535991804214637849063191397704397558234818224314499645527827937572)

Private key 40118423916604329992738910029529338069567151528432752036165544618942716987539


I thant modyfy base point and private key for get privkey * real base point = true pubkey = true, becouse now I have only my fake privkey * fake base point = true pubkey. This understand ? Help please, Bro ???



Title: Re: Private key hack new method
Post by: AB de Royse777 on August 17, 2020, 01:07:46 PM
You panic too much, just create P2SH or P2WPKH-P2SH address with your own spending condition (e.g. private key + random string as password) :P
Did I look panicking? :-P

My wallet has passphrase + another 12 word passphrase and the wallet never been in an online device. Now good luck on hacking it :-D

This topic again? Why don't you prove your theory by sign address used to mine genesis block or hold big amount of Bitcoin?
We all know the answer, don't we? :-D


Title: Re: Private key hack new method
Post by: alani123 on August 17, 2020, 01:08:28 PM
It's been posted again but an illustrative example is always good for newcomers I guess. The chances of cracking a private key are so small, you shouldn't even consider the task. The resources that would be required to break bitcoin's cryptography are beyond our mortal comprehension.  
https://i.ibb.co/D4ymj5M/fYFBsqp.jpg


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 01:13:02 PM
TheArchaeologist Bro, help please, as you have a good math knowledge ??? Share please yours "base point calculator" ???


Title: Re: Private key hack new method
Post by: TheArchaeologist on August 17, 2020, 01:18:03 PM
But with my base point this is anower address

I thant modyfy base point and private key for get privkey * real base point = true pubkey = true, becouse now I have only my fake privkey * fake base point = true pubkey. This understand ?

No, because what you are trying to do doesn't make any sense. I only used my example to show that it's really simple (because that's the way is is supposed to work) to calculate the public key from a private key. However the other way around is impossible (when the private key was generated truly random.  But when I know both I can easily claim that I did it the other way around.

But just like on every other thread you asked the same thing over and over again : No it can't be done! End of story.


Title: Re: Private key hack new method
Post by: mocacinno on August 17, 2020, 01:28:00 PM
TheArchaeologist Bro, help please, as you have a good math knowledge ??? Share please yours "base point calculator" ???

Looks like TheArchaeologist forgot to use the sarcasm-tag?

The correct use is:
[sarcasm]
Text
[/sarcasm]

 ;D


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 01:34:27 PM
TheArchaeologist Bro, help please, as you have a good math knowledge ??? Share please yours "base point calculator" ???

Looks like TheArchaeologist forgot to use the sarcasm-tag?

The correct use is:
[sarcasm]
Text
[/sarcasm]

 ;D

demonstrator of his yellow eggs size of ubiverse and TheArchaeologist, believe that their bitcoins are securely protected and therefore so freaked out.


Title: Re: Private key hack new method
Post by: Coding Enthusiast on August 17, 2020, 01:47:04 PM
You also can't just come up with any domain parameters you like, your G coordinates are not in the interval [0, p−1] (read page 17 of SEC 1: Elliptic Curve Cryptography). In other words your point is not even on curve and multiplication is not even defined, consequently the numbers you posted as pub/private key are random numbers. It is like claiming you have found an integer for x for x2=-1.


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 01:59:59 PM
You also can't just come up with any domain parameters you like, your G coordinates are not in the interval [0, p−1] (read page 17 of SEC 1: Elliptic Curve Cryptography). In other words your point is not even on curve and multiplication is not even defined, consequently the numbers you posted as pub/private key are random numbers. It is like claiming you have found an integer for x for x2=-1.

My points on the curve. Random only private keys and private key in order of curve.


p.s. Base point on curve, for example is a public key too.

This is another variant of privkey and base point for used pubkey:

BP (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)
FakeBP (27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)

Q (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

privkey 36540658479409362678121339879672694014739785286643571088000951145429744113500


Title: Re: Private key hack new method
Post by: gmaxwell on August 17, 2020, 02:17:34 PM
You also can't just come up with any domain parameters you like,
Unless you're microsoft. :P


This thread is silly. If you can change the basepoint the problem is trivial.   Set the basepoint to any number times the pubkey.  The private key is the modular inverse of that number.



Title: Re: Private key hack new method
Post by: BitcoinFX on August 17, 2020, 03:39:18 PM
lolz ... close, but no cigar ... now go here OP ...  :D

How hard would it be to brute force an address. (Numerically)
- https://bitcointalk.org/index.php?topic=5267859.0


Title: Re: Private key hack new method
Post by: mamuu on August 17, 2020, 07:44:56 PM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]




[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???


hi
where is the method ?  did you read new model POW attack ?


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 09:26:00 PM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]




[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???


hi
where is the method ?  did you read new model POW attack ?

Need modify fake base point and get valid privkey. This is not to hard task, bat needed math knowledge.

I hope there is someone who will make the code.


Title: Re: Private key hack new method
Post by: dextronomous on August 17, 2020, 09:48:57 PM
hi there,
you could checkout https://pypi.org/project/eciespy/
i guess some of the things you need.


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 10:13:44 PM
hi there,
you could checkout https://pypi.org/project/eciespy/
i guess some of the things you need.


need someone who know how to subtract from basepoint fakeBP and after add and then what's left to add to the private key


Title: Re: Private key hack new method
Post by: mamuu on August 17, 2020, 11:20:08 PM
Code:
sage: P
115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: EE
Elliptic Curve defined by y^2 = x^3 + 7 over Finite Field of size 115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: Q
(41092972045662183626692698115026263699106807529773860274318687111639116151521 : 25612602434799576731996141476317124058234433726241370033130536741579356668244 : 1)
sage: 87954421572711191797409873682088439575132560617980964771068188888320747613432 *Q
(52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q
(27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)
sage:
sage: G
(55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q +G
(60514677919760207795808847379414464935859540298217373706884704950585656052831 : 92467424300256128213756399718584656167407456241133297890405049170425502221771 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113501*Q
(9870940521884748245828036059372982985243987669974027519407180018299448314799 : 84417392858735638984503471023078768847021781340877352409438879295369906944372 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G
(26526818200564724704301259892364899649062843225393016254446718809459073971066 : 58177991911204874107434935003117119688646076024935570317854531999248293096805 : 1)
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G)
Adres:  1BLBtz4sZgDkCYaLAx1g17jfiLHPpiojEF  Balance:  0  Tx:  0
Adres:  1B9kyL7qFSZaNRnkR3745zhg4vk3ZjSVPj  Balance:  0  Tx:  0
Adres:  1JBLMwzGGRAga5oXSoh9aBCxFVT7t4wNRi  Balance:  0  Tx:  0
Adres:  1BqzGKfAMj6AX9pdZG8C6AiDyaRqXPMpGc  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -2*G)
Adres:  14WtPAwTx3Wtp2pYrreztZy3FqVXWx7eQ3  Balance:  0  Tx:  0
Adres:  18HrA6fh3TjzxZ9CgkeL1ebDqZAP94xoNc  Balance:  0  Tx:  0
Adres:  1BUXyr7653i4p5Zy85SXiHbrp6fnPjqCRS  Balance:  0  Tx:  0
Adres:  1K3gF1uBixEgXbQjY9VUPHFH1nzVgbqkS4  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q)
Adres:  19qRsrAmc8ZfeAE8fLH7bguvWfTZ3MrLLS  Balance:  0  Tx:  0
Adres:  16KrAKZ6SPESWL1RBkhSbjRwUzbSwBfRso  Balance:  0  Tx:  0
Adres:  14B6z3QgLL6ygX27EjzjjgFMvQkumE41AA  Balance:  0  Tx:  0
Adres:  14LnUUW8dX5Zh3YpddjVDFh24TZMdaf8S7  Balance:  0  Tx:  0
sage: CC(Q)
Adres:  17XekGktaj9DMi61ndokjN6Sx7LNWsVYjQ  Balance:  0  Tx:  0
Adres:  1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK  Balance:  10000.00188824  Tx:  46
Adres:  187cn4uGjP1rvjrPzSyWzQhX5rhz62ArNm  Balance:  0  Tx:  0
Adres:  1CVZtk2czeMQeRfSeKNHYTDSMJEBXTS21Z  Balance:  0  Tx:  0
sage: SmartAttack(G,Q,P)%P
49507345783879453664137177101856360142284501228139827997787302912743629416333
sage: SmartAttack(G,2*G,P)%P
92776810360347062140128362771302456139448233644672974681811545519691306070200
sage:


there is no fakeBP, all of them Q, Q is k.G

36540658479409362678121339879672694014739785286643571088000951145429744113500*Q == 36540658479409362678121339879672694014739785286643571088000951145429744113500*k*G

if you want solve fakeBP, you can use ECDLP solver(like kangaroo)

SmartAttack work on anomalous curve because trace of one

but if work on sec curves, then  always one result.


Title: Re: Private key hack new method
Post by: COBRAS on August 17, 2020, 11:32:10 PM
Code:
sage: P
115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: EE
Elliptic Curve defined by y^2 = x^3 + 7 over Finite Field of size 115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: Q
(41092972045662183626692698115026263699106807529773860274318687111639116151521 : 25612602434799576731996141476317124058234433726241370033130536741579356668244 : 1)
sage: 87954421572711191797409873682088439575132560617980964771068188888320747613432 *Q
(52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q
(27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)
sage:
sage: G
(55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q +G
(60514677919760207795808847379414464935859540298217373706884704950585656052831 : 92467424300256128213756399718584656167407456241133297890405049170425502221771 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113501*Q
(9870940521884748245828036059372982985243987669974027519407180018299448314799 : 84417392858735638984503471023078768847021781340877352409438879295369906944372 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G
(26526818200564724704301259892364899649062843225393016254446718809459073971066 : 58177991911204874107434935003117119688646076024935570317854531999248293096805 : 1)
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G)
Adres:  1BLBtz4sZgDkCYaLAx1g17jfiLHPpiojEF  Balance:  0  Tx:  0
Adres:  1B9kyL7qFSZaNRnkR3745zhg4vk3ZjSVPj  Balance:  0  Tx:  0
Adres:  1JBLMwzGGRAga5oXSoh9aBCxFVT7t4wNRi  Balance:  0  Tx:  0
Adres:  1BqzGKfAMj6AX9pdZG8C6AiDyaRqXPMpGc  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -2*G)
Adres:  14WtPAwTx3Wtp2pYrreztZy3FqVXWx7eQ3  Balance:  0  Tx:  0
Adres:  18HrA6fh3TjzxZ9CgkeL1ebDqZAP94xoNc  Balance:  0  Tx:  0
Adres:  1BUXyr7653i4p5Zy85SXiHbrp6fnPjqCRS  Balance:  0  Tx:  0
Adres:  1K3gF1uBixEgXbQjY9VUPHFH1nzVgbqkS4  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q)
Adres:  19qRsrAmc8ZfeAE8fLH7bguvWfTZ3MrLLS  Balance:  0  Tx:  0
Adres:  16KrAKZ6SPESWL1RBkhSbjRwUzbSwBfRso  Balance:  0  Tx:  0
Adres:  14B6z3QgLL6ygX27EjzjjgFMvQkumE41AA  Balance:  0  Tx:  0
Adres:  14LnUUW8dX5Zh3YpddjVDFh24TZMdaf8S7  Balance:  0  Tx:  0
sage: CC(Q)
Adres:  17XekGktaj9DMi61ndokjN6Sx7LNWsVYjQ  Balance:  0  Tx:  0
Adres:  1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK  Balance:  10000.00188824  Tx:  46
Adres:  187cn4uGjP1rvjrPzSyWzQhX5rhz62ArNm  Balance:  0  Tx:  0
Adres:  1CVZtk2czeMQeRfSeKNHYTDSMJEBXTS21Z  Balance:  0  Tx:  0
sage: SmartAttack(G,Q,P)%P
49507345783879453664137177101856360142284501228139827997787302912743629416333
sage: SmartAttack(G,2*G,P)%P
92776810360347062140128362771302456139448233644672974681811545519691306070200
sage:


there is no fakeBP, all of them Q, Q is k.G

36540658479409362678121339879672694014739785286643571088000951145429744113500*Q == 36540658479409362678121339879672694014739785286643571088000951145429744113500*k*G

if you want solve fakeBP, you can use ECDLP solver(like kangaroo)

SmartAttack work on anomalous curve because trace of one

but if work on sec curves, then  always one result.

if conwert curve equation, the trase will be not one. A forget form what without this bag(I mean secure and trace one, not secure - no bug)


CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q)


what is it ? so you find private key for 10k btc ? Or this is a privkey * to Q ?

and what is this - "sage: CC(Q)"?


Title: Re: Private key hack new method
Post by: mamuu on August 17, 2020, 11:53:21 PM
Code:
sage: P
115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: EE
Elliptic Curve defined by y^2 = x^3 + 7 over Finite Field of size 115792089237316195423570985008687907853269984665640564039457584007908834671663
sage: Q
(41092972045662183626692698115026263699106807529773860274318687111639116151521 : 25612602434799576731996141476317124058234433726241370033130536741579356668244 : 1)
sage: 87954421572711191797409873682088439575132560617980964771068188888320747613432 *Q
(52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q
(27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)
sage:
sage: G
(55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q +G
(60514677919760207795808847379414464935859540298217373706884704950585656052831 : 92467424300256128213756399718584656167407456241133297890405049170425502221771 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113501*Q
(9870940521884748245828036059372982985243987669974027519407180018299448314799 : 84417392858735638984503471023078768847021781340877352409438879295369906944372 : 1)
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G
(26526818200564724704301259892364899649062843225393016254446718809459073971066 : 58177991911204874107434935003117119688646076024935570317854531999248293096805 : 1)
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -G)
Adres:  1BLBtz4sZgDkCYaLAx1g17jfiLHPpiojEF  Balance:  0  Tx:  0
Adres:  1B9kyL7qFSZaNRnkR3745zhg4vk3ZjSVPj  Balance:  0  Tx:  0
Adres:  1JBLMwzGGRAga5oXSoh9aBCxFVT7t4wNRi  Balance:  0  Tx:  0
Adres:  1BqzGKfAMj6AX9pdZG8C6AiDyaRqXPMpGc  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q -2*G)
Adres:  14WtPAwTx3Wtp2pYrreztZy3FqVXWx7eQ3  Balance:  0  Tx:  0
Adres:  18HrA6fh3TjzxZ9CgkeL1ebDqZAP94xoNc  Balance:  0  Tx:  0
Adres:  1BUXyr7653i4p5Zy85SXiHbrp6fnPjqCRS  Balance:  0  Tx:  0
Adres:  1K3gF1uBixEgXbQjY9VUPHFH1nzVgbqkS4  Balance:  0  Tx:  0
sage: CC(36540658479409362678121339879672694014739785286643571088000951145429744113500*Q)
Adres:  19qRsrAmc8ZfeAE8fLH7bguvWfTZ3MrLLS  Balance:  0  Tx:  0
Adres:  16KrAKZ6SPESWL1RBkhSbjRwUzbSwBfRso  Balance:  0  Tx:  0
Adres:  14B6z3QgLL6ygX27EjzjjgFMvQkumE41AA  Balance:  0  Tx:  0
Adres:  14LnUUW8dX5Zh3YpddjVDFh24TZMdaf8S7  Balance:  0  Tx:  0
sage: CC(Q)
Adres:  17XekGktaj9DMi61ndokjN6Sx7LNWsVYjQ  Balance:  0  Tx:  0
Adres:  1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK  Balance:  10000.00188824  Tx:  46
Adres:  187cn4uGjP1rvjrPzSyWzQhX5rhz62ArNm  Balance:  0  Tx:  0
Adres:  1CVZtk2czeMQeRfSeKNHYTDSMJEBXTS21Z  Balance:  0  Tx:  0
sage: SmartAttack(G,Q,P)%P
49507345783879453664137177101856360142284501228139827997787302912743629416333
sage: SmartAttack(G,2*G,P)%P
92776810360347062140128362771302456139448233644672974681811545519691306070200
sage:


there is no fakeBP, all of them Q, Q is k.G

36540658479409362678121339879672694014739785286643571088000951145429744113500*Q == 36540658479409362678121339879672694014739785286643571088000951145429744113500*k*G

if you want solve fakeBP, you can use ECDLP solver(like kangaroo)

SmartAttack work on anomalous curve because trace of one

but if work on sec curves, then  always one result.

Code:
sage: Q
(41092972045662183626692698115026263699106807529773860274318687111639116151521 : 25612602434799576731996141476317124058234433726241370033130536741579356668244 : 1)

sage: str('02')+hex(41092972045662183626692698115026263699106807529773860274318687111639116151521).lstrip("0x")
'025ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1'

sage : ku 025ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1

input                        : 025ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1
network                      : Bitcoin mainnet
symbol                       : BTC
public pair x                : 41092972045662183626692698115026263699106807529773860274318687111639116151521
public pair y                : 25612602434799576731996141476317124058234433726241370033130536741579356668244
 x as hex                    : 5ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1
 y as hex                    : 38a03820dcda0c431bf15f4fe897d36c5053981610b20e1699853a00b3248154
y parity                     : even
key pair as sec              : 025ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1
 uncompressed                : 045ad9cc469e32ea3d294a152b78bfded6ad47cfb9d5d9e52e201cd93d0c05fae1\
                                 38a03820dcda0c431bf15f4fe897d36c5053981610b20e1699853a00b3248154
hash160                      : d7b1951a0da15bce93d296b386b4e473e8c00c65
 uncompressed                : 479cbe0cd292709e8595c541146cd6231add3eda
Bitcoin address              : 1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK
Bitcoin address uncompressed : 17XekGktaj9DMi61ndokjN6Sx7LNWsVYjQ
Bitcoin segwit address       : bc1q67ce2xsd59duay7jj6ecdd8yw05vqrr9yd638m
p2sh segwit                  : 38Hhqsz98m8bjAJ9JhrN6RMx25Kz32UdS4
 corresponding p2sh script   : 0014d7b1951a0da15bce93d296b386b4e473e8c00c65

sage: CC(Q)
Adres:  17XekGktaj9DMi61ndokjN6Sx7LNWsVYjQ  Balance:  0  Tx:  0
Adres:  1LfV1tSt3KNyHpFJnAzrqsLFdeD2EvU1MK  Balance:  10000.00188824  Tx:  46
Adres:  187cn4uGjP1rvjrPzSyWzQhX5rhz62ArNm  Balance:  0  Tx:  0
Adres:  1CVZtk2czeMQeRfSeKNHYTDSMJEBXTS21Z  Balance:  0  Tx:  0
sage:


CC() is check balance function on ellipticcurve points for bitcoin

Code:
sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q
(27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)

sage: FakeBP
(27766988394528305332024168539037695039502084538361626787903749004653433687854 : 13581498523946301885502763354170297668198202071266362739407311067363122460026 : 1)

sage: 36540658479409362678121339879672694014739785286643571088000951145429744113500*Q == FakeBP
True
sage:



Title: Re: Private key hack new method
Post by: COBRAS on August 18, 2020, 12:06:52 AM
@mamuu, Im go to sleep now. I will answer you in the morning.

But I not understand why you always multiply some number to stable Q. If you mean what Q is a basepoint, so, you need Q<> QPublickkey.

And were is your private key ?

You know SAGE this is a good news.


Title: Re: Private key hack new method
Post by: MrFreeDragon on August 18, 2020, 09:24:24 AM
The set of elliptic curve points is a wheel (repeating from the beginning as soon as reach the order). Actually you try to straighten the wheel, starting from different points (base point) considering the start of length as the base point.

There is no advantage in it. So do not waste your time.


Title: Re: Private key hack new method
Post by: ewaspiro on August 27, 2020, 02:48:02 PM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]

[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???

Well, why dont you use Pollard on any public key exposed before 2015 with a balance. Much easier than what you are trying to do. Or even throw ina few custom spartan 6 to spin off that private key recovery.


Title: Re: Private key hack new method
Post by: bigvito19 on August 27, 2020, 03:43:10 PM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]

[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???

Well, why dont you use Pollard on any public key exposed before 2015 with a balance. Much easier than what you are trying to do. Or even throw ina few custom spartan 6 to spin off that private key recovery.



What's special about public keys exposed before 2015?



Title: Re: Private key hack new method
Post by: Karartma1 on August 27, 2020, 05:18:25 PM
In my start post I was show a private key -base point-public key and address with 1000 BTC. :o
Well you have the private key, go sweep the 1000 BTC then.

This private key for different base point !!! Need someone who can make a code for find privkey for legit base point this info about this modified base point, and legit private key for this modified base point.

With 500 BTC any of us can be a king of some African country. Yes, if someone disappointed, and not thant get any btc from block chain this is mistake for future all life for him. So, lets make a code and go, Brothers !!!!  I can provide more examples of privkey+basepoint+pubkey's !!!

I gave you a bit of credit, but I lost you at the king of some African country part. /s
Have fun cracking private keys with your script, if you are super lucky you might unleash satoshi's wealth. And then you would be the new king of bitcoin.
In the meantime read this https://www.quora.com/Is-it-possible-for-someone-to-guess-a-private-key-to-a-Bitcoin-wallet-and-steal-the-coins


Title: Re: Private key hack new method
Post by: COBRAS on August 27, 2020, 05:23:37 PM
I know a method how to find a private key for any publick key, but with modified base point(false BP).

If someone making a code for calculating a private key for real base point, I will share code for find a private key for false base point and REAL publick key.

This is a examles:

Code:
Real BTC Basepoint (55066263022277343669578718895168534326250603453777594175500187360389116729240 : 32670510020758816978083085130507043184471273380659243275938904335757337482424 : 1)


False BTC Base Point [u](52426333756564302526085053269432084545410002202648992412042160756077650870390 : 79709923240617764371931483354308897031409999608033097982950682278401348639896 : 1)[/u]

[b]REAL Public key[/b] Q(41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Public key generated[/b] Q1 (41092972045662183626692698115026263699106807529773860274318687111639116151521, 25612602434799576731996141476317124058234433726241370033130536741579356668244)

[b]Q1==Q True[/b]

[b]Private key [/b]87954421572711191797409873682088439575132560617980964771068188888320747613432 !!!




Any help are welcome !!!

???

Well, why dont you use Pollard on any public key exposed before 2015 with a balance. Much easier than what you are trying to do. Or even throw ina few custom spartan 6 to spin off that private key recovery.

Did you fined something before 2015 ? Before 2015 is 256 bytes too and Kangaroo just time waster in task to crack 256 bytes.


Title: Re: Private key hack new method
Post by: BTCW on August 27, 2020, 11:24:27 PM
If you or anyone else could calculate private keys from public keys, you would accomplish one thing: bringing down the value of Bitcoin to zero.