MonetaryUnit Address
SHARE
Private Key (Wallet Import Format)
SECRET

A MonetaryUnit wallet is as simple as a single pairing of a MonetaryUnit address with it's corresponding MonetaryUnit private key. Such a wallet has been generated for you in your web browser and is displayed above.

To safeguard this wallet you must print or otherwise record the MonetaryUnit address and private key. It is important to make a backup copy of the private key and store it in a safe location. This site does not have knowledge of your private key. If you are familiar with PGP you can download this all-in-one HTML page and check that you have an authentic version from the author of this site by matching the SHA1 hash of this HTML with the SHA1 hash available in the signed version history document linked on the footer of this site. If you leave/refresh the site or press the "Generate New Address" button then a new private key will be generated and the previously displayed private key will not be retrievable. Your MonetaryUnit private key should be kept a secret. Whomever you share the private key with has access to spend all the MonetaryUnits associated with that address. If you print your wallet then store it in a zip lock bag to keep it safe from water. Treat a paper wallet like cash.

Add funds to this wallet by instructing others to send MonetaryUnits to your MonetaryUnit address.

Check your balance by going to a block explorer and entering your MonetaryUnit address.

Spend your MonetaryUnits by downloading the MonetaryUnit wallet and importing your private key. Keep in mind when you import your single key to a MonetaryUnit p2p client and spend funds your key will be bundled with other private keys in the p2p client wallet. When you perform a transaction your change will be sent to another MonetaryUnit address within the p2p client wallet. You must then backup the p2p client wallet and keep it safe as your remaining MonetaryUnits will be stored there. Satoshi advised that one should never delete a wallet.

Comma Separated Values: Index,Address,Private Key (WIF)
Why should I use a Bulk Wallet to accept MonetaryUnits on my website?
The traditional approach to accepting MonetaryUnits on your website requires that you install the official MonetaryUnit client daemon ("MonetaryUnitd"). Many website hosting packages don't support installing the MonetaryUnit daemon. Also, running the MonetaryUnit daemon on your web server means your private keys are hosted on the server and could get stolen if your web server is hacked. When using a Bulk Wallet you can upload only the MonetaryUnit addresses and not the private keys to your web server. Then you don't have to worry about your MonetaryUnit wallet being stolen if your web server is hacked.
How do I use a Bulk Wallet to accept MonetaryUnits on my website?
  1. Use the Bulk Wallet tab to pre-generate a large number of MonetaryUnit 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.
  2. Import the MonetaryUnit 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 MonetaryUnit addresses as they will be shown to customers.)
  3. Provide an option on your website's shopping cart for your customer to pay in MonetaryUnit. When the customer chooses to pay in MonetaryUnit 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.
  4. You now need to be notified when the payment arrives. Google "MonetaryUnit payment notification" and subscribe to at least one MonetaryUnit 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 MonetaryUnit address you are checking. It could take between 10 minutes to one hour for the transaction to be confirmed.
    http://www.blockexplorer.com/address/THEADDRESSGOESHERE

    Unconfirmed transactions can be viewed at: http://blockchain.info/
    You should see the transaction there within 30 seconds.
  5. MonetaryUnits will safely pile up on the block chain. Use the original wallet file you generated in step 1 to spend them.
Enter Passphrase:
Confirm Passphrase: Algorithm: SHA256(passphrase)
MonetaryUnit Address:
Private Key (Wallet Import Format):
Step 1 Public Key:

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. You will need this to retrieve the MonetaryUnit Private Key once the Pool has found your prefix.

YOU MUST SET THIS VALUE BEFORE CONTINUING!

Select the Decimal Version. Refer to the chart.





For Example:

LiteCoin addresses start with L. So, the decimal version is 48.
NameCoin addresses start with n or m. So, the decimal version is 111.


A text version of this chart is available here

Your MonetaryUnit 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 MonetaryUnit 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, BIP38).

MonetaryUnit 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.
MonetaryUnit Address
MonetaryUnit Address Compressed


Public Key (130 characters [0-9A-F]):
Public Key (compressed, 66 characters [0-9A-F]):

Private Key WIF
51 characters base58, starts with a
'6'
Private Key WIF Compressed
52 characters base58, starts with a
'T'


Private Key Hexadecimal Format (64 characters [0-9A-F]):
Private Key Base64 (44 characters):