<p>The pull request that you refer to is just for simple import/export of private keys and wallets and does not include the feature that you want.</p>

<p>There have been some discussions on multi-signature transactions which sounds similar to what you are looking for. That would allow for cases where two different private keys are required to make a transaction. See <a href="https://bitcointalk.org/index.php?topic=38928.0" rel="nofollow">this forum thread</a> and the <a href="https://gist.github.com/39158239e36f6af69d6f" rel="nofollow">draft proposal here</a>.</p>

CC BY-SA 3.0
2011-09-25T21:17:28.420Z
Tell me: With pull 220, what will happen if I import the same key to two different wallets?
Leo
CC BY-SA 3.0
2011-09-26T11:43:40.297Z
As both wallets will have the key with the ability to spend the coins, both can spend it. The first to spend it most likely decides where the coins go. The other will see the debit transaction appear. If you try to do two spendings almost simultaneous, you're effectively doing an attempted double spend. The netwerk will cope, but the wallet will not.
Pieter Wuille
CC BY-SA 3.0
2011-10-04T14:35:03.673Z
Sipa: Will be possible to have a feature where I know that a exported key it's not in any wallet? If someone export a key and send me, I would like to be the only one able to spend the btc from this key.
Leo
CC BY-SA 3.0
2011-11-13T17:18:01.180Z
If you want to be the only one controlling a key, there is one simple solution: use a key you generated yourself. If you want to accept funds available to a key as incoming payment, do a transaction yourself to send the funds to a new key. There are plans for a "sweepprivkey" command that would do this; it hasn't been implemented, though.
Pieter Wuille
CC BY-SA 3.0
2011-09-25T20:22:00.213Z
2011-09-25T20:22:00.213Z
D.H.
<p>On pull request <a href="https://github.com/bitcoin/bitcoin/pull/220">https://github.com/bitcoin/bitcoin/pull/220</a> say will be possible to import/export keys.
I would like to know if will be possible to have the same key on different wallets and only be able to spend the bitcoins from this key with permission of the other users that has this same key on the wallet. Example:</p>

<ol>
<li>I have a key on my client with 10 BTC. </li>
<li>I export this key and send to a friend</li>
<li>The key will be on my wallet and on my friend wallet</li>
<li>When I or my friend try to spend the bitcoins from this specific key, will be requested a password asking if we accept the transaction.</li>
</ol>

<p>Will this be possible on next Bitcoin versions?</p>

CC BY-SA 3.0
2011-09-25T20:41:18.390Z
I think that the title of this question should be changed. It seems to be more about requiring permission from two different people to send funds and less about having the same key in two wallets.
D.H.
<development>
Will be possible to have the same key on more than one wallet?
Leo
# Will be possible to have the same key on more than one wallet?

(Asked by: username_0 on 2011-09-25)

On pull request <https://github.com/bitcoin/bitcoin/pull/220> say will be possible to import/export keys.
I would like to know if will be possible to have the same key on different wallets and only be able to spend the bitcoins from this key with permission of the other users that has this same key on the wallet. Example:

1. I have a key on my client with 10 BTC.
2. I export this key and send to a friend
3. The key will be on my wallet and on my friend wallet
4. When I or my friend try to spend the bitcoins from this specific key, will be requested a password asking if we accept the transaction.

Will this be possible on next Bitcoin versions?

**Tags:** development

> **Comments:**
> **username_1**: I think that the title of this question should be changed. It seems to be more about requiring permission from two different people to send funds and less about having the same key in two wallets.  

---

## 1 answers

### Answer by username_1 on 2011-09-25. Score: 4

The pull request that you refer to is just for simple import/export of private keys and wallets and does not include the feature that you want.

There have been some discussions on multi-signature transactions which sounds similar to what you are looking for. That would allow for cases where two different private keys are required to make a transaction. See [this forum thread](https://bitcointalk.org/index.php?topic=38928.0) and the [draft proposal here](https://gist.github.com/39158239e36f6af69d6f).

> **Comments:**
> **username_0**: Tell me: With pull 220, what will happen if I import the same key to two different wallets?  
> **username_2**: As both wallets will have the key with the ability to spend the coins, both can spend it. The first to spend it most likely decides where the coins go. The other will see the debit transaction appear. If you try to do two spendings almost simultaneous, you're effectively doing an attempted double spend. The netwerk will cope, but the wallet will not.  
> **username_0**: Sipa: Will be possible to have a feature where I know that a exported key it's not in any wallet? If someone export a key and send me, I would like to be the only one able to spend the btc from this key.  
> **username_2**: If you want to be the only one controlling a key, there is one simple solution: use a key you generated yourself. If you want to accept funds available to a key as incoming payment, do a transaction yourself to send the funds to a new key. There are plans for a "sweepprivkey" command that would do this; it hasn't been implemented, though.  

---

