Generating a new receiving bitcoin address
In order to generate a new "receiving" bitcoin address within your CoinJar:
- Sign in to your CoinJar's Accounts.
- Select your 'Everyday Bitcoin'.
- Next to the 'Actions' dropdown menu, select 'View address'.
Your CoinJar's receiving bitcoin address will be provided as an alphanumeric string of characters, which can be copied and safely passed along to anyone looking to send bitcoin to your CoinJar. If their device can scan QR codes, they can also use the QR code provided.
Keeping payment activity private
Utilising a single receiving address to accept incoming payments is typically not advised for long term use. Although bitcoin payments are anonymous, they are available to view publicly on the blockchain.
Each time you select 'View address', CoinJar will generate a brand new receiving address for you to use. By actively generating and using new addresses for each incoming payment, you're able to keep your transfer activity as private as possible.
For these reasons, your CoinJar will not display any previously-generated addresses, however those addresses are permanently linked to your CoinJar in the background. This means you can safely distribute the addresses you generate within CoinJar for future use and the funds sent to them will always arrive safely.
Receiving Payouts with CoinJar
Due to the way CoinJar's wallet system operates, it does not support payouts.
CoinJar uses various different addresses to send digital currencies - not the receiving wallet address you've generated in your CoinJar. As some external services are automatically configured to return payouts to your sending address, this can lead to funds not being returned to your CoinJar.
Due to this, we do not recommend you use your CoinJar for cryptocurrency mining or gambling websites. You can instead use an offline wallet for these payouts, and then transfer your funds to your CoinJar. If you have any questions regarding this, please reach out to our Support Team.
Updated: 18 Jan 2018 (AS)
Reviewed: 18 Jan 2018 (AS)
Comments
0 comments
Article is closed for comments.