does every transacation type like ( p2pk , p2pkh ) exposes pub - key of sender
also puzzle solver has to find private key or pub - key
which required to be find
also based on my knowledge thereare many transaction types which doesn't direclty expose pub - key of sender in mempool
Why solver is not ready to use other safe types ?
I am amused that you are just assuming the transaction was hijacked just because u feel so. Is there any pending transaction u can see on p66 address?? How then did u conclude that the winner lost the price?? U really think someone who beat 8 billion others to solve a puzzle is so dumb??? Lol
I have been able to get proof that it was most certainly stolen. I just don't know why the invalidated transaction by the original winner isn't logged to the address 13zb1... But is legitimately registered on the Blockchain still. Sad, I hope people will donate to him or the creator withdraws from like 165 which might not be done at all to give him. There is also a chance that he did RBF himself, I mean the winner.
does every transacation type like ( p2pk , p2pkh ) exposes pub - key of sender
also puzzle solver has to find private key or pub - key
which required to be find
also based on my knowledge thereare many transaction types which doesn't direclty expose pub - key of sender in mempool
Why solver is not ready to use other safe types ?
I will be consice not to confuse u because it isn't so complex and I am a great explainer.
Yes all spending txs expose the senders pubK once they hit the mempool whether public or local mempools.
Obviously to solve the puzzle which is to gain access to move the funds, u need the private key and that is what we are solving for. All that was available for 66 was the public address or simply address not to confuse u. we never had the pub key because we don't know the private key and the address also has no spending transaction.
Privatekey pased through the elliptic curve is your public key and your public key Sha-256 and ripemd 160 is the address u share to collect btc.
From Math it is like
Private key-> k
Public key -> pubK
secp256k1(k) = pubK
RipeMD(SHA-256(pubK)) = Btc address
If ur public key is known. That makes ur wallet vulnerable, how vulnerable will be based on your private key's entropy. So far 256 bit entropies which is like throwing heads or tails 256 times and combining the results has been unguessable right. But if u reduce it to 66 guesses of heads or tails that makes it extremely vulnerable. Still very unguessable by humans but super computers are strong enough today with some algorithms to crack it. That is the case of 66.
To your last question, there is no spending tx that doesn't expose the pubKey of the sender. But you can reduce exposure by not creating a direct transaction to the mempool.
The winner made no effort to safeguard the tx which is very f*olish.
U can submit a rawTX directly to a mining pool which wouldn't expose ur tx on the mempool before at least one confirmation. But remember, the mining pool and it's miners can still see your pubkey here so they could also steal it but it removes the exposure to the global mempool and bots on it. If u get a noble pool with integrity. They will carry it out without exposing your tx or forerunning you. So fara Mara Slipstream is the recommendation I heard.
This is all the valuable info worth years of experience.
can you explain in more detail , for my question : Everyone know Pub key of all transactions right ( I may be wrong in this or Evryone know just bitcoin address of sender)
Why bots just spoffed now itself
Wrong, everyone knows the address of their wallet and can share it. The publicKey is different and my indepth analysis into the basic technical cryptographic details above should help you really.
I had a very great Cryptographer for my Doctorate and he was so understandable. Bless him, this was how he broke it down.