Bitcoin Forum
October 18, 2018, 02:08:45 AM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bitcoin core multi wallet  (Read 503 times)
columbo
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
October 25, 2017, 08:44:26 AM
 #1

On the newest version of bitcoin core there is a declared support for multi wallets.
Can someone explain how does this work on a linux command line interface? I couldn't find anything explained on documentation.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1539828525
Hero Member
*
Offline Offline

Posts: 1539828525

View Profile Personal Message (Offline)

Ignore
1539828525
Reply with quote  #2

1539828525
Report to moderator
1539828525
Hero Member
*
Offline Offline

Posts: 1539828525

View Profile Personal Message (Offline)

Ignore
1539828525
Reply with quote  #2

1539828525
Report to moderator
HCP
Hero Member
*****
Offline Offline

Activity: 756
Merit: 932

<insert witty quote here>


View Profile
October 25, 2017, 12:08:19 PM
 #2

The release notes for 0.15 seem to explain it: https://bitcoin.org/en/release/v0.15.0.1#multi-wallet-support
2nd paragraph explains how to use multiple wallets:
Quote
Multi-wallet is enabled by using more than one -wallet argument when starting Bitcoin, either on the command line or in the Bitcoin config file.

Then to access a specific wallet, check the 3rd bullet point down regarding changes to RPC interface:
Quote
When running Bitcoin Core with multi-wallet, wallet-level RPC methods must specify the wallet for which they’re intended in every request. HTTP RPC requests should be send to the <RPC IP address>:<RPC port>/wallet/<wallet name>/ endpoint, for example: 127.0.0.1:8332/wallet/wallet1.dat/. bitcoin-cli commands should be run with a -rpcwallet option, for example: bitcoin-cli -rpcwallet=wallet1.dat getbalance.

columbo
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
October 25, 2017, 12:55:14 PM
 #3

The release notes for 0.15 seem to explain it: https://bitcoin.org/en/release/v0.15.0.1#multi-wallet-support
2nd paragraph explains how to use multiple wallets:
Quote
Multi-wallet is enabled by using more than one -wallet argument when starting Bitcoin, either on the command line or in the Bitcoin config file.

Then to access a specific wallet, check the 3rd bullet point down regarding changes to RPC interface:
Quote
When running Bitcoin Core with multi-wallet, wallet-level RPC methods must specify the wallet for which they’re intended in every request. HTTP RPC requests should be send to the <RPC IP address>:<RPC port>/wallet/<wallet name>/ endpoint, for example: 127.0.0.1:8332/wallet/wallet1.dat/. bitcoin-cli commands should be run with a -rpcwallet option, for example: bitcoin-cli -rpcwallet=wallet1.dat getbalance.

Thank you. So, when starting bitcoind I simply use:
bitcoind -daemon -wallet=wallet1.dat -wallet=wallet2.dat
Right?

Then on bitcoin-cli I pass the -rpcwallet=wallet1.dat argument, right?
HCP
Hero Member
*****
Offline Offline

Activity: 756
Merit: 932

<insert witty quote here>


View Profile
October 25, 2017, 01:04:13 PM
 #4

Yep, that looks to be right.

Spiffer
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
December 28, 2017, 01:30:33 PM
 #5

The release notes for 0.15 seem to explain it: https://bitcoin.org/en/release/v0.15.0.1#multi-wallet-support
2nd paragraph explains how to use multiple wallets:
Quote
Multi-wallet is enabled by using more than one -wallet argument when starting Bitcoin, either on the command line or in the Bitcoin config file.

Then to access a specific wallet, check the 3rd bullet point down regarding changes to RPC interface:
Quote
When running Bitcoin Core with multi-wallet, wallet-level RPC methods must specify the wallet for which they’re intended in every request. HTTP RPC requests should be send to the <RPC IP address>:<RPC port>/wallet/<wallet name>/ endpoint, for example: 127.0.0.1:8332/wallet/wallet1.dat/. bitcoin-cli commands should be run with a -rpcwallet option, for example: bitcoin-cli -rpcwallet=wallet1.dat getbalance.

Hi

Can I store more than one type of crypto coin on a Bitcoin core wallet? And what types of coins can I store? Or did I misunderstand what you all are talking about?

Best Regards
Ottobrøker
AdolfinWolf
Hero Member
*****
Offline Offline

Activity: 826
Merit: 635



View Profile
December 28, 2017, 01:32:15 PM
 #6

The release notes for 0.15 seem to explain it: https://bitcoin.org/en/release/v0.15.0.1#multi-wallet-support
2nd paragraph explains how to use multiple wallets:
Quote
Multi-wallet is enabled by using more than one -wallet argument when starting Bitcoin, either on the command line or in the Bitcoin config file.

Then to access a specific wallet, check the 3rd bullet point down regarding changes to RPC interface:
Quote
When running Bitcoin Core with multi-wallet, wallet-level RPC methods must specify the wallet for which they’re intended in every request. HTTP RPC requests should be send to the <RPC IP address>:<RPC port>/wallet/<wallet name>/ endpoint, for example: 127.0.0.1:8332/wallet/wallet1.dat/. bitcoin-cli commands should be run with a -rpcwallet option, for example: bitcoin-cli -rpcwallet=wallet1.dat getbalance.

Hi

Can I store more than one type of crypto coin on a Bitcoin core wallet? And what types of coins can I store? Or did I misunderstand what you all are talking about?

Best Regards
Ottobrøker

No, the multiwallet is only made for bitcoin, it simply means you can access multiple wallet.dats at once, not multiple crypto currencies.

For something like that you would need to use something like exodus https://www.exodus.io/

jnano
Member
**
Offline Offline

Activity: 237
Merit: 13


View Profile
February 16, 2018, 01:47:59 AM
 #7

Can anyone suggest an effective way to interact with multiple wallets?

The GUI only allows interacting with the first wallet, and as far as I know there's no way to switch the primary wallet without restarting.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1554
Merit: 1701


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 16, 2018, 01:55:20 AM
 #8

Can anyone suggest an effective way to interact with multiple wallets?
Use the bitcoin-cli utility and use the JSON-RPC interface.

The GUI only allows interacting with the first wallet, and as far as I know there's no way to switch the primary wallet without restarting.
GUI support for multiwallet will hopefully be in 0.17.0.

jnano
Member
**
Offline Offline

Activity: 237
Merit: 13


View Profile
February 16, 2018, 02:18:57 AM
 #9

I meant in a GUI of some sort. Maybe a third party tool that interacts with Core through the RPC interface.

Good to know it's planned for 0.17. How come, even though it was useful to have also years ago, multi-wallet was never on the radar but started now getting more attention?




achow101
Moderator
Legendary
*
Offline Offline

Activity: 1554
Merit: 1701


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 16, 2018, 03:47:48 AM
 #10

Good to know it's planned for 0.17. How come, even though it was useful to have also years ago, multi-wallet was never on the radar but started now getting more attention?
The way that the wallet implementation was before made it very difficult to implement multi wallet. In order to properly implement multiwallet, a lot of stuff had to first be done to decouple the wallet stuff from the rest of the software, and that requires a lot of changes and a lot of review. Only then were we able to get proper multiwallet support.

jnano
Member
**
Offline Offline

Activity: 237
Merit: 13


View Profile
February 21, 2018, 05:58:16 AM
 #11

Was there a lack of developer interest before, or was it just a lower priority feature combined with complex implementation?

And in case anyone wants to follow the development, here are good starting points.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1554
Merit: 1701


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 21, 2018, 06:22:44 AM
 #12

Was there a lack of developer interest before, or was it just a lower priority feature combined with complex implementation?
It was mostly a low priority feature with lots of complex stuff to do before it could work.

jnano
Member
**
Offline Offline

Activity: 237
Merit: 13


View Profile
March 28, 2018, 10:24:02 PM
 #13

Now merged:
https://github.com/bitcoin/bitcoin/commit/25cf18f239f0d812fe458435d064e522a6cab5f8
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!