FOR EXAMPLE: what method it is possible to calculate the private key in hexadecimal keyspace for addresses 1HBtApAFA9B2YZw3G2YKSMCtb3dVnjuNe2
I know, that he is on a position 00000000000000000000000000000000000000000000000000000022382facd0
I have learned(found out) it casually from an open source.
But me interests as it is possible to calculate this position and with what minimal error (i.e. with the maximal accuracy).
All these addresses are taken casually only for an example
I think you are asking "How do I calculate the private key from the public key?" It is easy to calculate the public key from the private key. The formula is PublicKey = PrivateKey * G where G is a specific point on the specified elliptic curve and * is the scalar multiplication defined over the finite group of the elliptic curve. For all practical purposes it is impossible to calculate or even estimate the private key from the public key because there is no "division operation" defined for the group. That is what makes Bitcoin work.If you could calculate or even estimate the private key from the public key then anyone could calculate anyone's private key from their public key and anyone could steal anyone's Bitcoins. Is that what you are thinking of doing? Stealing my Bitcoins? If anyone ever figures out how to calculate or estimate the private key from the public key then Bitcoin and a plethora of other system worldwide would all be catastrophically broken. |
|
|
|
Again, we know the exact method used to generated the all the private keys: the keys are all a random number masked down to the desired size.
So if the range of the next key is know (and it is) then the probability of finding it within any subrange within the known range is easily calculated.
If you know a random number is between 1 and 1000 then the probability that it is between 100 and 199 is exactly 10%, the probability it is in any subrange you calculate by any means, no matter how well intentioned and complicated, is just the size of that subrange over the size of the known range.
Hi BurtW! Can someone prompt as it is possible calculate location of the private key in hexadecimal (- keyspace FROM:TO)? Possible write in P.M. I have no idea what you are asking. What do you mean by "location"? |
|
|
|
My client is behaving very strangely. Going offline/online, staking like mad, showing 0 network weight, etc. Any ideas?
(passed your message along) I restarted the program and it fixed itself. |
|
|
|
LBC has sequentially searched and swept all private keys under 55 bits and is pressing on at about 20.82 trillion keys per day. So all short private keys are a bad idea.
|
|
|
|
|
My client is behaving very strangely. Going offline/online, staking like mad, showing 0 network weight, etc. Any ideas?
|
|
|
|
|
Again, we know the exact method used to generated the all the private keys: the keys are all a random number masked down to the desired size.
So if the range of the next key is know (and it is) then the probability of finding it within any subrange within the known range is easily calculated.
If you know a random number is between 1 and 1000 then the probability that it is between 100 and 199 is exactly 10%, the probability it is in any subrange you calculate by any means, no matter how well intentioned and complicated, is just the size of that subrange over the size of the known range.
|
|
|
|
And here is private key:
00000000000000000000000000000000000000000000000013C96A3742F64906
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYmLDHsih379uP9zbHSD
Hello Zielar the private key you give does not match it lacks characters Looks correct to me. Using bitaddress.org: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYmLDHsih379uP9zbHSD 00000000000000000000000000000000000000000000000013C96A3742F64906 0249A43860D115143C35C09454863D6F82A95E47C1162FB9B2EBE0186EB26F453F 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB |
|
|
|
|
I work in the storage industry designing solid state drives. In order for us to sell our drives into the government market for the storage of top secret information the NSA has told us that our next generation of drives will have to either move from our current 2048 bit RSA keys to 3072 bit RSA keys or switch from our current 2048 bit RSA keys to 384 bit EC keys. Also, all our hashes and HMACs have to be upgraded from 256 bits to 384 bits.
It is interesting to me that at one point the NSA was leaning toward forcing everyone to switch from RSA 2K to EC 384 across the board as EC 384 was thought to be slightly more quantum resistant and would give them some breathing room for the time being.
However, more recently they have told everyone that if we have not switched over to EC yet to not bother because they will be requiring everyone to move everything over to quantum resistant algorithms instead of switching to EC sooner than expected.
So my suggestion would be to follow the NSA lead and move Bitcoin off of EC on to a quantum resistant algorithm instead of trying to make our EC crypto less vulnerable by change to a larger key size etc.
I realize that may be seen as too big of a step but the "backup plan" would be to move Bitcoin to a 384 bit curve and upgrade all the hashes to 384 bits - breaking all ASIC mining hardware.
Since the miners will not allow that we are back to square one.
|
|
|
|
Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?  Why would you run it online? It is risky to do that because your data could be intercepted. You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me. I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem. Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through. I totally forget about split key. But google knowing user generate vanity address doesn't matter unless you could know bitcoin address just from partial private key, brute force to get private from an address with partial private key or have serious privacy concern. Here is an old thread from 2012 where we all discussed how outsourcing vanity address generation could be done. The math is discussed there if you want to read up on it. Later, most of us in the thread gave up on the idea since anyone who cares about fungibility wants to get rid of address reuse all together. Ideally all addresses would get used exactly two times: once to fund it and once to spend it. This flies in the face of the entire concept of vanity address generation. |
|
|
|
thank you for unmask a scammer which build directory.io!
I did not say it was a scam - because it is not a scam. I said it was a joke - because it is a joke. directory.io is down, BTW. this site just created Bitcoin addresses (and private keys?) on the fly if a user requested a new page of directory.io. let us not call it scam. instead let us call it spoofing. Yes, directory.io is down. The more appropriately named keys.lol does the same thing. |
|
|
|
Hi All
This is confusing me as i can't seem to grasp how i can keep and average of what i am paying for BTC??
I want to keep track of the amount of BTC i purchase (easy) and also the average price i paid per BTC..
My thinking for example was as below but it's not correct..lol
Purchase BTC
0.5 BTC for £3453
0.7 BTC for £3561
0.1 BTC for £7000
Therefore
1.3 BTC for £14,014
£14014/1.3= 1 BTC for £10,780 or £10,780/BTC
Is this correct?
If i sold ANYTHING upto 1.3BTC above £10,780/BTC i would be in profit??
Am i doing this correct? Or should i be using the exchange rate when purchasing??
I basically want to purchase small amounts and then do on large sell for profit...
Confused..
Cheers
0.5 BTC + 0.7 BTC + 0.1 BTC = 1.3 BTC £3453 + £3561 + £7000 = £14014 £14014/1.3 = £10780 so the math is correct. Did you really pay £7000 for 0.1 BTC? If so you got ripped off royally - that is £70000 PER BTC.I expect you actually bought 1.0 BTC for £7000, right? Then you have: 0.5 BTC + 0.7 BTC + 1.0 BTC = 2.2 BTC £3453 + £3561 + £7000 = £14014 £14014/2.2 = £6370 per BTC You will profit if you sell above £6370 per BTC EDIT: fixed typo |
|
|
|
thank you for unmask a scammer which build directory.io!
I did not say it was a scam - because it is not a scam. I said it was a joke - because it is a joke. |
|
|
|
What happened to puzzle transaction #55? No trophy, no collision, just on to the next one?
Also if we are checking against bloom filter of known addresses with positive balances how are we specifically targeting any particular address ie any puzzle transaction at all? Is it the complexity of the private key that is supposedly wildly basic/uncomplex and therefore most likely to be the next find?
How often is directory.io updated? I still have some pages I'd like to check but I'm about ready for some new material
Just airing out my stupid for a little bit, thanks for the smax
The puzzle transaction transactions are a known quantity. Each one uses one more bit in the private key. Since LBC is sequentially searching the private key space they will eventually find each puzzle transaction as they search. Finding each one is just a benchmark as LBC progresses through the private key space, that is all. LBC is not looking for the puzzle transactions specifically. It is just known that they will be found and approximately how long it will be till the next one is found. directory.io is a joke. It is not "updated" because it does not really exist in the sense of a database. All it does is calculate the information on the fly. When you enter a page number it just calculates all the information for that page at the time it presents the information to you. There is no database. But yes, you can enter a page number and it will calculate that page for you. |
|
|
|
I am very interested in this type of trades. The proceedure is simple: you deposit the coins or fiat. Crypto is protected by bitgo, we don't own any private key, any outgoing transactions need to be co-signed in order to be processed. So once you make the deposit you can transact it whatever you like at whatever price you like with your partner(s). You find the web address in my profile.
Your site is similar to the lousy analogue of crypto exchanges. If you calculate that someone will put their money on your site, then you are naive. This looks even more crap than my 3000btc purchase offer posted on this forum.I will give you merit for you honesty. |
|
|
|
|
Finally. It will be very interesting to see what it contains.
|
|
|
|
|
I know for a fact this is bullshit because anyone who deals with 10,000 BTC (approximately $39,629,400.00) does not do business here. They simply use real exchanges. If you started with a more reasonable amount then maybe you would be legit. You are asking to do a $40 million dollar transaction on a message board in the backwaters of the Internet, therefore, you are full of shit. You would not happen to also be a Nigerian prince by any chance would you?
|
|
|
|
Here is the bitcoin address that contains the Bitcoins:
1MDq7zyLw6oKichbFiDDZ3aaK59byc6CT8
I think there is a good chance you are the same as this person. 99.9%, this is a lame scam attempt. 0.1%, the coins are somehow stolen, or otherwise associated with very bad things so that anyone who has them will be wishing they were scammed. Stay away from this guy.... Pff ... I see that the very idea that someone can buy btc under a non-cash payment contract, and even coins will be transferred AFTER full payment, does not give you peace of mind. Apparently you sell BTC for cash and with escrow))? #1, he is asking for his trading partner to send coins first to him: Please do not ask me to send before. #2, Bitcoin is generally fungible, but it is not anonymous. If you want to cash out any decent amount of coin, you will need to disclose your identity to your counter party (exchange), and helping someone launder money is a crime, please see: because i hacked the bitcoins so i want to sell them.
#3, it is strange you were so quick to see my theory the OP was you  Your item #1 is a lie. I have never asked anyone to send me coins in advance. I need only PoC. After the PoC, we will start a further discussion about buying coins. So you're lying. None of this matters because you do not have control of or own these coins. If you do then prove it by signing a message with the private key you "hacked" in order to own/control these coins. Until you do that nothing else matters and this thread and all your other threads can be closed as scams. |
|
|
|
|
Show Posts
