diff --git a/bitaddress.org.html b/bitaddress.org.html index f6bb0d3..af178f5 100644 --- a/bitaddress.org.html +++ b/bitaddress.org.html @@ -3754,6 +3754,11 @@ return this.pubKeyHex = Crypto.util.bytesToHex(this.getPub()).toString().toUpperCase(); }; + ECKey.prototype.getPubKeyHexCompressed = function () { + if (this.pubKeyHexCompressed) return this.pubKeyHexCompressed; + return this.pubKeyHexCompressed = Crypto.util.bytesToHex(this.getPubCompressed()).toString().toUpperCase(); + }; + ECKey.prototype.getPubCompressed = function () { if (this.pubCompressed) return this.pubCompressed; return this.pubCompressed = ecparams.getG().multiply(this.priv).getEncoded(1); @@ -3940,11 +3945,14 @@ .pubkeyhex { word-wrap: break-word; } .faqs ol { padding: 0 0 0 25px; } .faqs li { padding: 3px 0; } - #main { font-family: Arial; position: relative; text-align: center; margin: 0px auto; width: 795px; } + #main { font-family: Arial; position: relative; text-align: center; margin: 0px auto; width: 945px;/*795px;*/ } #logo { width: 578px; height: 80px; } #generate { font-family: Courier New; height: 158px; text-align: left; position: relative; padding: 5px; border: 2px solid green; } #generate span { padding: 5px 5px 0 5px; } #menu { visibility: hidden; } + #culturemenu { text-align: right; padding: 0 20px; } + #culturemenu span { padding: 3px; } + #culturemenu .selected { text-decoration: none; color: #000000; } #paperarea { min-height: 120px; display: none; } #paperarea .keyarea { border: 2px solid green; border-top: 0; } @@ -3998,7 +4006,7 @@ #vanitystep1label { padding-left: 5px; } #vanitystep2area { border-top: 2px solid green; display: block; padding: 15px; } #vanitystep2inputs { padding: 0 15px 10px 15px; } - #vanityadd { margin-top: 5px; } + #vanitycalc { margin-top: 5px; } .bulkquestion { padding: 10px 15px; text-align: left; cursor: pointer; } .bulkquestion:hover, .expandable:hover { color: #77777A; } @@ -4043,12 +4051,12 @@ #bulklimit { width: 45px; } .footer { font-family: Arial; font-size: 90%; clear: both; width: 700px; padding: 10px 0 10px 0; margin: 50px auto auto auto; } - .footer div span { padding: 10px; } + .footer div span.item { padding: 10px; } .footer .authorbtc { float: left; width: 470px; } - .footer .authorbtc span { text-align: left; display: block; padding: 0 20px; } + .footer .authorbtc span.item { text-align: left; display: block; padding: 0 20px; } .footer .authorbtc div { position: relative; z-index: 100; } .footer .authorpgp { position: relative; } - .footer .authorpgp span { text-align: right; display: block; padding: 0 20px; } + .footer .authorpgp span.item { text-align: right; display: block; padding: 0 20px; } .footer .copyright { font-size: 80%; clear: both; padding: 5px 0; } .footer .copyright span { padding: 10px 2px; } } @@ -4069,6 +4077,10 @@
+
+ English | + Español +
Open Source JavaScript Client-Side Bitcoin Wallet Generator
@@ -4080,10 +4092,10 @@
Vanity Wallet
Wallet Details
- +
- Generating Bitcoin Address...
 - MOVE your mouse around to add some extra randomness...
 + Generating Bitcoin Address...
+ MOVE your mouse around to add some extra randomness...
@@ -4091,21 +4103,21 @@
- +
- Bitcoin Address: + Bitcoin Address:
- Private Key (Wallet Import Format): + Private Key (Wallet Import Format):
@@ -4114,30 +4126,30 @@
- Hide Art? - Addresses per page: - Addresses to generate: + + + - +
- Start index: - Rows to generate: + + - +
- Comma Separated Values: Index,Address,Private Key (WIF) + Comma Separated Values: Index,Address,Private Key (WIF)
- Why should I use a Bulk Wallet to accept Bitcoins on my website? + Why should I use a Bulk Wallet to accept Bitcoins on my website?
@@ -4152,19 +4164,19 @@
- How do I use a Bulk Wallet to accept Bitcoins on my website? + How do I use a Bulk Wallet to accept Bitcoins on my website?
    -
  1. Use the Bulk Wallet tab to pre-generate a large number of bitcoin addresses (10,000+). Copy and paste the generated +
  2. Use the Bulk Wallet tab to pre-generate a large number of bitcoin addresses (10,000+). Copy and paste the generated comma separated values (CSV) list to a secure text file on your computer. Backup the file you just created to a secure location.
    3. -
  3. Import the bitcoin addresses into a database table on your web server. +
  4. Import the bitcoin addresses into a database table on your web server. (Don't put the wallet/private keys on your web server, otherwise you risk hackers stealing your coins. Just the bitcoin addresses as they will be shown to customers.)
    5. -
  5. Provide an option on your website's shopping cart for your customer to pay in Bitcoin. When the customer chooses to pay in Bitcoin you will +
  6. Provide an option on your website's shopping cart for your customer to pay in Bitcoin. When the customer chooses to pay in Bitcoin you will then display one of the addresses from your database to the customer as his "payment address" and save it with his shopping cart order.
    7. -
  7. You now need to be notified when the payment arrives. Google "bitcoin payment notification" and subscribe to at least +
  8. You now need to be notified when the payment arrives. Google "bitcoin payment notification" and subscribe to at least one bitcoin payment notification service. There are various services that will notify you via Web Services, API, SMS, Email, etc. Once you receive this notification, which could be programmatically automated, you can process the customer's order. To manually check if a payment has arrived you can use Block Explorer. Replace THEADDRESSGOESHERE with the bitcoin address @@ -4175,7 +4187,7 @@ Unconfirmed transactions can be viewed at: http://blockchain.info/
    You should see the transaction there within 30 seconds.
    9. -
  9. Bitcoins will safely pile up on the block chain. Use the original wallet file you generated in step 1 to spend them.
    10. +
  10. Bitcoins will safely pile up on the block chain. Use the original wallet file you generated in step 1 to spend them.
@@ -4185,30 +4197,30 @@
- Enter Passphrase: + Enter Passphrase: - Show? - + +
Confirm Passphrase: - Algorithm: SHA256(passphrase) + Algorithm: SHA256(passphrase)
- Bitcoin Address: + Bitcoin Address:
- Private Key (Wallet Import Format): + Private Key (Wallet Import Format):
@@ -4217,120 +4229,122 @@
- Step 1 Public Key: + Step 1 Public Key:
-

Copy and paste the above into the Your-Part-Public-Key field in the Vanity Pool Website.
+
Copy and paste the above into the Your-Part-Public-Key field in the Vanity Pool Website.
- Step 1 Private Key: - -

Copy and paste the above Private Key field into a text file. Ideally save to an encrypted drive. + Step 1 Private Key: + +
Copy and paste the above Private Key field into a text file. Ideally save to an encrypted drive. You will need this to retrieve the Bitcoin Private Key once the Pool has found your prefix.
-
Enter Your Part Private Key (generated in Step 1 above and previously saved): -
[NOTE: this input box can accept a public key or private key] +
+ Enter Your Part Private Key (generated in Step 1 above and previously saved): +
[NOTE: this input box can accept a public key or private key]
-
Enter Pool Part Private Key (from Vanity Pool): -
[NOTE: this input box can accept a public key or private key] +
+ Enter Pool Part Private Key (from Vanity Pool): +
[NOTE: this input box can accept a public key or private key]
- - + +
-
+
- Vanity Bitcoin Address: + Vanity Bitcoin Address: -

The above is your new address that should include your required prefix.
+
The above is your new address that should include your required prefix.
- Vanity Public Key (HEX): + Vanity Public Key (HEX): -

The above is the Public Key in hexadecimal format.
+
The above is the Public Key in hexadecimal format.
- Vanity Private Key (WIF): + Vanity Private Key (WIF): -

The above is the Private Key to load into your wallet.
+
The above is the Private Key to load into your wallet.
- Enter Private Key (any format) + - +
- Your Bitcoin Private Key is a unique secret number that only you know. It can be encoded in a number of different formats. - Below we show the Bitcoin Address and Public Key that corresponds to your Private Key as well as your Private Key in the most popular encoding formats (WIF, HEX, B64, MINI). -

- Bitcoin v0.6+ stores public keys in compressed format. The client now also supports import and export of private keys with importprivkey/dumpprivkey. The format of the exported - private key is determined by whether the address was generated in an old or new wallet. + Your Bitcoin Private Key is a unique secret number that only you know. It can be encoded in a number of different formats. + Below we show the Bitcoin Address and Public Key that corresponds to your Private Key as well as your Private Key in the most popular encoding formats (WIF, HEX, B64, MINI). +

+ Bitcoin v0.6+ stores public keys in compressed format. The client now also supports import and export of private keys with importprivkey/dumpprivkey. The format of the exported + private key is determined by whether the address was generated in an old or new wallet.
- Bitcoin Address: + Bitcoin Address:

- Bitcoin Address (compressed): + Bitcoin Address (compressed):

- Public Key (130 characters [0-9A-F]): + Public Key (130 characters [0-9A-F]):
- Public Key (compressed, 66 characters [0-9A-F]): + Public Key (compressed, 66 characters [0-9A-F]):
- Private Key WIF (51 characters base58, starts with a '5'): + Private Key WIF (51 characters base58, starts with a '5'):


- Private Key WIF (compressed, 52 characters base58, starts with a 'K' or 'L'): + Private Key WIF (compressed, 52 characters base58, starts with a 'K' or 'L'):


- Private Key Hexadecimal Format (64 characters [0-9A-F]): + Private Key Hexadecimal Format (64 characters [0-9A-F]):
- Private Key Base64 (44 characters): + Private Key Base64 (44 characters):
@@ -4340,19 +4354,20 @@
@@ -4625,6 +4640,176 @@ }; + +