ill be sure to run dban from now on when i reformat...
Great tool I didn't know it File "pywallet.py", line 95
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^
SyntaxError: invalid syntax
You seem to have Python 3 which is not supported yet |
|
|
|
|
No need for Bitbills, choose 64 random characters in [1234567890abcdef], change it into a Bitcoin address -> instant free bitbill
|
|
|
|
Is there any technical/cryptographical reason why this has to be so complex? In other words, would the following method for generating addresses have some serious flaw that the above method does not:
address = base58(version byte + first160bitsof(sha256(pubkey)) + crcCheck)
crcCheck = crc32(version byte + first160bitsof(sha256(pubkey)))
Can't see any reason why that would be much weaker, really. Me neither, but it's just an opinion Or for that matter, is there any point to sha256'ing the public key to begin with? i.e., would replacing first160bitsof(sha256(pub key)) with just first160bitsof(pubkey) do just as well?
Thanks!
Not too sure about that, I doubt revealing part of the pubkey long in advance is a problem. But then I'm not a cryptographer familiar with ECC, so I wouldn't bet the future of a currency on it. In that case there will be 2^96 known pubkeys with the same address, it may be a problem |
|
|
|
You're right, I just put it on the top of the todo list |
|
|
|
If COPYING is considered "developing" then shitting in a toilet should the equivalent of depositing cash at the bank.
Nice, I approve this message |
|
|
|
|
666. I'm going to release a new Bitcoin fork
|
|
|
|
yep, it smells like scam, but it's the only way to save ixcoin... Nuts don't fall far from the tree |
|
|
|
Wow..you sure are an advocate arent you? So when's the big dump Psy?
The big dump? I just took it... RIGHT ON YOUR FACE!
Intelligence isnt your forte is it?  Quoting isnt your forte is it? |
|
|
|
Do you want the web interface? nope Do you want to sign messages? nope Yeah, I forgot the download part, is it that hard? Getting Python+deps is beyond the average user.
Perhaps make a bundle Windows installer for it? I know Inkscape requires Python and it contains its own copy of Python with all the needed deps in it's installer.
Perhaps even make an option not to unpack and just to use the local Python for power-users.
When dealing with Bitcoin I think binaries are not a good idea I don't see how http://sprucecodes.com/one-time.htm is simple and installing 1 exe + downloading a file is horribly impossible |
|
|
|
You can convert your private keys from a format to another with pywallet
Maybe you can, but I can't. I'm a stupid Windows plug-and-play type user. My hand-coded SpruceCode stuff is aimed at people who aren't computer geeks and don't trust themselves with anything particularly complex on their computer. To get Bitcoin into the mainstream requires it to be usable by mainstream people. Who aren't all computer geeks! Windows-R Enter cmd Enter one line copypasted + your private key Enter Done My grandma did that once, that didn't even kill her |
|
|
|
TRY TO CALL OUT SOMEONE FOR A TYPO ITS ACTUALLY SPELLED CORRECTLY Do you have problems? You should smoke something bro I was just meaning that it's not really bizarre |
|
|
|
We're working on exactly this, and it should be available sometime next week on the Bitbills website.
I hope it will accept private key input in both base58 and hex format. My one-time hand-encoding (see sig link) of private keys works on the hex key and not the base58 one. You can convert your private keys from a format to another with pywallet |
|
|
|
|
sha256 of a file, nothing to remember, impossible to find
|
|
|
|
The checksum matches?
Yes, otherwise it couldn't have received coins We'll never know wether or not it's valid  It almost certainly is valid. In theory, there are approx. 2^96 private keys that would fit. So far RaTTuS seems to have set the bar for complexity with his public address. Even though the prefix is only "1" + 6-characters, it's a 33-character address, and is much less common than a 34-character "1" + 7-character prefix. To beat it, one would need to show: - An address containing a 7-character or longer interior sequence, case-sensitive
- A 34-character address with a "1" + 8-character prefix, case-sensitive
- A 33-character address with a "1" + 7-character prefix, case-sensitive
Jackjack7eYNdGkbgUUrtKBraSWBUV5DJP (a "J" + 7-character prefix) Draw  Is that a valid bitcoin address? Here's mine: 1Chocobogtn77Fw56kQvZmTVbkziCK4L24 (I go by Chocobo in other forums) Another draw. For modified Bitcoin clients which accept higher address version (ie not for 99.9999% of the clients) Valid for Namecoin and testnets though |
|
|
|
The checksum matches?
Yes, otherwise it couldn't have received coins We'll never know wether or not it's valid It almost certainly is valid. In theory, there are approx. 2^96 private keys that would fit. So far RaTTuS seems to have set the bar for complexity with his public address. Even though the prefix is only "1" + 6-characters, it's a 33-character address, and is much less common than a 34-character "1" + 7-character prefix. To beat it, one would need to show: - An address containing a 7-character or longer interior sequence, case-sensitive
- A 34-character address with a "1" + 8-character prefix, case-sensitive
- A 33-character address with a "1" + 7-character prefix, case-sensitive
Jackjack7eYNdGkbgUUrtKBraSWBUV5DJP (a "J" + 7-character prefix) Draw |
|
|
|
thanks for your help kjj and forp, I think i can come up with a pretty accurate guess using both those methods.
Another thing i'm confused about. How to I determine the address the block reward was sent to? e.g. is their some way to extract the address out of "scriptSig"?
Take the 65 bytes starting with 04, it's the public key Then, do that: http://dl.dropbox.com/u/1139081/BitcoinImg/PubKeyToAddr.png |
|
|
|
|
It is valid
We'll just never find the private key
|
|
|
|
|
3 posts, 2 referral links
|
|
|
|
|
Show Posts
