Unverified Commit 2914834b authored by moneromooo-monero's avatar moneromooo-monero
Browse files

simplewallet.md: add a couple more commands, and rewording/typo fix

parent 7ec4a591
...@@ -27,7 +27,8 @@ Once you are running both simplewallet and bitmonerod, refresh the wallet's idea ...@@ -27,7 +27,8 @@ Once you are running both simplewallet and bitmonerod, refresh the wallet's idea
refresh refresh
This will pull blocks from the daemon the wallet did not yet see, and update your balance This will pull blocks from the daemon the wallet did not yet see, and update your balance
to match. To see the balance without refreshing: to match. This process will normally be done in the background every minute or so. To see the
balance without refreshing:
balance balance
...@@ -43,7 +44,7 @@ This is the command to use when you are sending to a standard address: ...@@ -43,7 +44,7 @@ This is the command to use when you are sending to a standard address:
transfer 3 ADDRESS AMOUNT PAYMENTID transfer 3 ADDRESS AMOUNT PAYMENTID
Replace ADDRESS with the address you wnt to sent to, AMOUNT with how many monero you want to send. Replace ADDRESS with the address you want to send to, AMOUNT with how many monero you want to send.
and PAYMENTID with the payment ID you were given. If the receiving party doesn't need one, just and PAYMENTID with the payment ID you were given. If the receiving party doesn't need one, just
omit it. omit it.
...@@ -61,18 +62,25 @@ higher fees needed. ...@@ -61,18 +62,25 @@ higher fees needed.
## Receiving monero ## Receiving monero
If you have your own Monero address, you just need to give your standard address to someone. If you have your own Monero address, you just need to give your standard address to someone.
Since Monero is anonymous, you won't see what address sent anything you receive. If you want to You can find out your address with:
know, you'll have to tell the sender to use a payment ID, which is an arbitrary optional tag which
gets attached to a transaction. To make life easier, you can generate an address that already address
includes a random payment ID:
Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
want to know, for instance to credit a particular customer, you'll have to tell the sender to use
a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
easier, you can generate an address that already includes a random payment ID:
integrated_address integrated_address
This will generate a random payment ID, and give you the address that includes your own account This will generate a random payment ID, and give you the address that includes your own account
and that payment ID. If you want to select your own payment ID, you can do that too: and that payment ID. If you want to select a particular payment ID, you can do that too:
integrated_address 12346780abcdef00 integrated_address 12346780abcdef00
Payments made to an integrated address generated from your account will go to your account,
with that payment id attached, so you can tell payments apart.
## Proving to a third party you paid someone ## Proving to a third party you paid someone
...@@ -81,12 +89,9 @@ to prove to a third party you did send the funds - or even to the merchant, if i ...@@ -81,12 +89,9 @@ to prove to a third party you did send the funds - or even to the merchant, if i
mistake. Monero is private, so you can't just point to your transaction in the blockchain, mistake. Monero is private, so you can't just point to your transaction in the blockchain,
as you can't tell who sent it, and who received it. However, by supplying the per-transaction as you can't tell who sent it, and who received it. However, by supplying the per-transaction
private key to a party, that party can tell whether that transaction sent monero to that private key to a party, that party can tell whether that transaction sent monero to that
particular address. Note that storing these per-transaction keys is disabled by default, and particular address.
you will have to enable it before sending, if you think you may need it:
set store-tx-keys 1
From now on, tx keys will be saved, and you can retrieve them later for a given transaction: You can retrieve the tx key from an earlier transaction:
get_tx_key 1234567890123456789012345678901212345678901234567890123456789012 get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
...@@ -121,3 +126,24 @@ If you received a payment using a particular payment ID, you can look it up: ...@@ -121,3 +126,24 @@ If you received a payment using a particular payment ID, you can look it up:
You can give more than one payment ID too. You can give more than one payment ID too.
More generally, you can review incoming and outgoing payments:
show_transfers
You can give an optional height to list only recent transactions, and request
only incoming or outgoing transactions. For example,
show_transfers in 650000
will only incoming transfers after block 650000. You can also give a height
range.
If you want to mine, you can do so from the wallet:
start_mining 2
This will start mining on the daemon usin two threads. Note that this is solo mining,
and may take a while before you find a block. To stop mining:
stop_mining
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment