Transaction-less transfer of value #84

issue gasteve opened this issue on February 28, 2011
  1. gasteve commented at 4:34 AM on February 28, 2011: none

    As a user, I would like to move bitcoins between wallets without having to use transactions (which could incur fees).

  2. gasteve commented at 4:39 AM on February 28, 2011: none

    It's important for this to be a "move" operation rather than a copy or export/import. For the user, it should feel like moving value between wallets (like a transaction, but without the need for it to enter the block chain and possibly incur fees). The wallets should be both presumed to be active, hence you would only want a given key to exist in one active wallet at a time. This feature should not be viewed as a backup mechanism.

  3. tcatm commented at 5:12 AM on February 28, 2011: none

    What you are describing is exactly what bitcoin transactions are for. It's impossible to break a coin into two smaller ones without making a transaction.

  4. gasteve commented at 6:37 AM on February 28, 2011: none

    Except that transactions will eventually cost money...I'm talking about moving private keys between wallets in order to consolidate bitcoins into a wallet without having to use a transaction and potentially incur a transaction fee.

  5. tril0byte commented at 4:53 PM on March 5, 2011: none

    I suggest generalizing this to a much more useful feature, the ability to create a bearer transaction that includes the private key (no need to mention amount), and obviously a text box to copy the transaction from instead of broadcasting it to the network. We'd need an input field to paste in the transaction (which is really just a key pair). It's really just export/import with the official client by default deleting the private key on export (possibly with a huge warning to make sure you copied the text somewhere safe). It makes sense to work on this feature after a mechanism for controlling which coins get included in a transaction, since the user will want to know how many coins are at a specific address before sending off the private key (to another wallet or another person).

    Appropriate new API calls should be created too.

  6. alexwaters commented at 5:31 AM on September 3, 2011: contributor

    Sipa's pull request would implement this, please contribute to #220 regarding this feature

  7. alexwaters closed this on Sep 3, 2011

  8. wtogami referenced this in commit d05e36e2ef on Nov 9, 2013
  9. glv2 referenced this in commit 60314cccff on Jul 22, 2014
  10. jtimon referenced this in commit 574817b129 on Mar 11, 2016
  11. ptschip referenced this in commit ca1cc2d231 on Sep 24, 2016
  12. ptschip referenced this in commit 7ecb12c127 on Sep 24, 2016
  13. classesjack referenced this in commit eb7c295c34 on Jan 2, 2018
  14. cryptapus referenced this in commit 26541868ac on Jan 21, 2018
  15. CryptAxe referenced this in commit 5b14c28826 on Mar 6, 2018
  16. attilaaf referenced this in commit 1d23bad793 on Jan 13, 2020
  17. Losangelosgenetics referenced this in commit e2181ada0c on Mar 12, 2020
  18. rajarshimaitra referenced this in commit 0f853c1332 on Aug 5, 2021
  19. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 21:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me