Receive bitcoin
An address, once created, remains yours to use in perpetuity. However, unless you understand the privacy implications of reusing addresses, KeepKey recommends using a new address every time you receive a transaction. By default, KeepKey generates a new address for each transaction. Make sure that the address provided matches the address displayed on your KeepKey. This step ensures that the address does in fact belong to KeepKey.
With that being said, your KeepKey does not need to be connected to receive bitcoin. Feel free to save one or more addresses to use at a later date without having to connect your KeepKey. Sorry, we didn't find any relevant articles for you. Please fill out the contact form below and we will reply as soon as possible. Support Home How-to Guides. After installing the KeepKey wallet on a Linux machine, There is no limit to the number of accounts KeepKey One of the difficulties involved with receiving bitcoin payments is the need to generate a unique address for each new user or invoice.
These addresses need to monitored and stored securely. The blockchain receive payments API takes care of the generation and monitoring of addresses. We will notify your server using a simple callback whenever a payment is received. The easiest way to start receiving payments is to open a Blockchain Wallet at https: You should create a new account inside your wallet exclusively for transactions facilitated by this API. This method creates a unique address which should be presented to the customer.
For any payments sent to this address, you will be sent an HTTP notification. This is done so you do not show the same address to two different customers. However, all funds will still show within the same account. As defined in BIP 44, wallet software will not scan past 20 unused addresses. Given enough requests from this API that don't have a matching payment, you could generate addresses past this horizon, which would make spending funds paid to those addresses quite difficult.
For this reason, this API will return an error and refuse to generate new addresses if it detects it would create a gap of over 20 unused addresses. If you encounter this error, you will either need to switch to a new xPub within the same wallet is fine , or receive a payment to one of the previous 20 created addresses.
Please note, this will not increase the number of addresses that will be monitored by our servers. Using this feature will require you understand the gap limitation and how to handle it for advanced users only:. You will be sent an HTTP notification immediately when a transaction is made, and subsequently when it reaches the number of confirmations specified in the request. You are required to specify the request's notification behaviour. Setting the behaviour to 'DELETE' will delete the request after the first relelvant notification is sent to your callback address.
Setting the behaviour to 'KEEP' will send additional notifications every time a transaction with the specified confirmations and operation type is sent to or from the address in the request. Operation type is an optional parameter indicating whether the address will be monitored for received or spent transactions, or both.
By default both operation types are monitored. You may also optionally specify the number of confirmations a transaction reaches before being sent a notification.