Kasisto is a web app enabling you to receive person to person Monero payments in small cafes, bars or shops. It will accept unconfirmed payments which makes it pretty much instant, but also means you should only accept smaller amounts since there's always a chance of a transaction not getting mined.
I'm the developer, the source is on GitHub: amiuhle/...
Accounts were created as part of the subaddress scheme.
A wallet has a seed. From this seed, the primary address private spend and view keys are derived. From these private keys, subaddresses are derived. Subaddresses are grouped into accounts.
This primary address is the first address in the first account in the wallet.
Each account has its own balance, ...
In order to communicate via php with a Monero wallet you have to run Monero Wallet RPC.
monero-wallet-rpc --rpc-bind-port 18082 --disable-rpc-login --wallet-file /path/walletfile
If you are using a remote node, simply add to command the --daemon-host node.moneroworld.com:18089 flag.
That command will build a JSON API avaiable on the 18082 port. You can ...
Monero "looks ahead" 200 subaddress indices from the highest subaddress index that it observes it has received an incoming payment to.
Therefore if you ever issue more than 200 subaddresses in a row and none of those receive any funds to them, then you need to force your wallet to scan beyond the subaddress index that it would normally stop looking beyond.
If you previously ran simplewallet in CLI mode (or 0.10's monero-wallet-cli in RPC mode) then you would simply transition to using monero-wallet-rpc with the same flags. As always, running the binary with --help will give you a list of all possible flags.
monero-wallet-rpc is one of the command-line applications that ships with Monero. It enables developers to make HTTP based requests to interact with a Monero wallet. An example could be to implement the receiving of payments in XMR on an ecommerce site.
The other RPC is the daemon RPC which is part of the main monerod application. This enables developers to ...
Since Monero 0.15.0.0, you can use the public_nodes command in monero-wallet-cli. It will query your daemon, as the list is now shared over the P2P network. This can be used in tandem with the bootstrap daemon mode, so you can use RPC services before your node has finished syncing.
Similarly, the print_pl daemon command now accepts a publicrpc parameter to ...
You should use --generate-from-json for this.
The input fields in the JSON file are:
version: integer, should be 1
filename: string, path/filename for the newly created wallet
scan_from_height: 64 bit unsigned integer, optional
password: string, optional
viewkey: string, hex representation
spendkey: string, hex ...
Start the daemon: monerod --testnet and then once sync'ed...
Start the wallet in another window: monero-wallet-cli --testnet to create a testnet wallet, then...
Back in the running daemon type: start_mining <your-wallet-address-here>
Wait to mine a block. You'll then have testnet coins.
Using the --tx-notify parameter to monero-wallet-cli/monero-wallet-rpc, you can run an arbitrary program when the wallet receives a transaction. The option takes a command line as parameter. The binary in that command line should have a path if necessary. Before being called, any instance of the "%s" string will be replaced by the transaction hash.
The transfer_split RPC indeed has a priority field, which may be set to 0-4, as you suspected. 0 stands for default (which is 2 currently, but will use the default you set via simplewallet if any), and 1-4 for their respective priorities (unimportant, normal, medium, highest).
The documentation does indeed need updating, this is one of these neverending ...
There are no forbidden characters. However, you might have difficulty with characters such as \r and \n, since they're interpreted as "I'm done" when you type a string, and as terminator when reading from a file. $ works just fine (let me try right now just to double check... yes, it works).
Interesting characters that might cause trouble are non ASCII ...
There is no RPC to create an address.
If there would be one, it would be one that would also "forget" the current one, so it would have limited usefulness.
If you can't find a flag and you run linux, you can use the usual way of sending an application to the background.
Start the application in the background:
Additionally, don't show output on the terminal:
./monero-wallet-rpc > /dev/null 2>&1 &
If you connect via ssh to launch the application, it will exit when you ...
You can run multiple monero-wallet-rpc processes on the same machine (or different ones), and connect them to a single node (which can be either on the same machine again, or a different one). You don't have to do anything special for this, though it's best if the monero-wallet-rpc processes don't run off the same wallet file, or they'll overwrite each other'...
Did you send funds from your wallet back to that same wallet? This warning message might reflect an inability, when observing the blockchain, to distinguish between the amount sent and the change.
When you send a transaction back to yourself, you'll create two outputs destined for your own wallet. One will be the "amount sent", and the other will be "change"...
I was running the command with the wrong parameters. I should have used --wallet-file instead of --wallet-dir when running monero-wallet-rpc.
My corrected command:
./monero-wallet-rpc --rpc-bind-port 28083 --wallet-file monerowallet \
--password mycoolpassword --disable-rpc-login
Is this bad for privacy?
Yes. Performing a churn (or any transaction for that matter) at regular intervals is bad for privacy (for yourself and others to some degree).
You are essentially helping to create a linkage by exposing the likely true output in a ring (thus also exposing the likely decoys), based purely on the timing of the transactions.
Take a look at a response to issue #2351:
You can send 50 monero 20 times in one tx to yourself (make sure you have set merge-destinations to 0 first). This will break up the 1000 output.
Also set min-outputs-count and min-outputs-value to, say, 20 and 10, see the commit message for 0ad87db for an explantion of how they work. Last, you can pay several ...
transfer, the older of the two commands, creates a single transaction. This can fail if you try to create a transaction with too many destinations / the transaction becomes too large.
transfer_split may create more than one transaction. This is useful if you are wanting to create transactions with a higher number of destinations as it can efficiently split ...
Recent monero code has a close_wallet RPC, as seen in https://github.com/monero-project/monero/pull/4007.
This call will close the currently opened wallet, if any, if you've started monero-wallet-rpc with --wallet-dir.
As @kenshi mentioned, --digest needs to be added to the curl command. The default behavior for curl is to attempt basic authentication, then abort. I have personally attempted curl with monero-wallet-rpc, so it should work.
The password file is always written to the same directory where monero-wallet-rpc was started. The filename is always monero-wallet-rpc....
The current release only allows for one address per wallet. In other words, one has to create multiple wallets in order to get multiple unlinkable addresses (integrated addresses created in the same wallet share the same plain address). Fortunately, the notion of subaddresses materialized and was implemented. They will be included in the next release. ...
I had the exact same error message when running monero-wallet-rpc without the option --disable-rpc-login.
Then, as explained by vtnerd in this open issue:
The file is always created in the current working directory when
authentication is enabled.
To create the file, you need to be the owner of the working directory.
I set the current user within the ...
--rpc-bind-ip [IP ADDRESS] Binds the daemon to an IP address. You need to use your External IP if you plan to access this daemon from outside your local network, or an Internal IP if you only want it to work for devices in the same local network.
--rpc-bind-ip 0.0.0.0 In the context of a local network, 0.0.0.0 means 'all the IP addresses inside the local ...