Bitcoin Forum
April 27, 2024, 02:08:03 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Custom Bitcoin transaction with an override key?  (Read 1462 times)
Isosceles (OP)
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
December 27, 2011, 11:57:39 PM
 #1

Is it possible to construct a custom transaction in which either your key, or the key of an "overseer" can spend the coins? And add a feature such that all subsequent transactions you make also have to include the overseer's override feature?

Would be useful if you wanted to give a trusted organisation the ability to retrieve your bitcoins if they were lost/stolen.
1714183683
Hero Member
*
Offline Offline

Posts: 1714183683

View Profile Personal Message (Offline)

Ignore
1714183683
Reply with quote  #2

1714183683
Report to moderator
1714183683
Hero Member
*
Offline Offline

Posts: 1714183683

View Profile Personal Message (Offline)

Ignore
1714183683
Reply with quote  #2

1714183683
Report to moderator
1714183683
Hero Member
*
Offline Offline

Posts: 1714183683

View Profile Personal Message (Offline)

Ignore
1714183683
Reply with quote  #2

1714183683
Report to moderator
Bitcoin addresses contain a checksum, so it is very unlikely that mistyping an address will cause you to lose money.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2216


Chief Scientist


View Profile WWW
December 28, 2011, 12:09:45 AM
 #2

Is it possible to construct a custom transaction in which either your key, or the key of an "overseer" can spend the coins?
Yes.  That would be a "1 of 2 signatures required" multisignature transaction.
Quote
And add a feature such that all subsequent transactions you make also have to include the overseer's override feature?
That you can't do. If the coins were stolen, the thief can just sign them away.

I suppose you could do a "2 of 2 signatures required" and then have the overseer only approve transactions that were ALSO 2-of-2 required (where 1 was the overseer's signature).  A thief could take your coins away, but wouldn't be able to spend them without the overseer's OK.  The overseer wouldn't be able to take them back, though.

More complicated schemes are probably possible if you want to trust the overseer completely... but if you and the person you are paying trust the overseer completely then why bother using bitcoin transactions at all?  Just hold accounts at the overseer and they can transfer balances or reverse transactions as they like....

How often do you get the chance to work on a potentially world-changing project?
Isosceles (OP)
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
December 28, 2011, 01:31:09 AM
 #3

Can you do a "1-of-1 or 2-of-2" transaction, where either the overseer spends the coins, or both the overseer & the holder spends the coins?

I could open an account with the overseer & use a non-bitcoin currency, but you would lose the bitcoin's benefits of the inability to arbitrarily mint new currency, and the public transaction ledger. ie. if they stole it you would know immediately.
Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2216


Chief Scientist


View Profile WWW
December 28, 2011, 02:42:35 AM
 #4

Can you do a "1-of-1 or 2-of-2" transaction, where either the overseer spends the coins, or both the overseer & the holder spends the coins?

You can do 2-of-3 (overseer holds 2, so can always spend, you hold 1) instead to accomplish the same thing. I suppose having the overseer put transactions in the block-chain that everybody can see might make you and the people you're paying trust them more...

How often do you get the chance to work on a potentially world-changing project?
Isosceles (OP)
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
December 28, 2011, 04:02:54 AM
 #5

Interesting, thanks.

Thinking of uses, if everyone trusts the overseer, I could get my coins back if they're stolen. Alternatively, a government could regulate bitcoin by requiring merchants to use this type of transaction.

Also, how would this transaction appear in the Bitcoin client? Would both the owner & the overseer see the bitcoins in their account? Presumably the client can't spend them in the GUI.
Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2216


Chief Scientist


View Profile WWW
December 28, 2011, 05:50:37 PM
 #6

The client doesn't support multisignature transactions yet.

How often do you get the chance to work on a potentially world-changing project?
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742
Merit: 500



View Profile WWW
December 29, 2011, 08:31:48 AM
 #7

Can you do a "1-of-1 or 2-of-2" transaction, where either the overseer spends the coins, or both the overseer & the holder spends the coins?

You can do 2-of-3 (overseer holds 2, so can always spend, you hold 1) instead to accomplish the same thing. I suppose having the overseer put transactions in the block-chain that everybody can see might make you and the people you're paying trust them more...

Thats an interesting way to do it.  Might as well just give your coins to the overseer though as they don't need you.  Maybe have 2 separate overseers? Seems strange and I'm not sure I see a use-case.

Mike Hearn
Legendary
*
expert
Offline Offline

Activity: 1526
Merit: 1128


View Profile
December 30, 2011, 12:57:06 AM
 #8

You don't actually want the ability to "get back stolen coins". It sounds superficially attractive at first but has huge problems, which is one reason why credit cards work so poorly (from the merchants perspective).

To see why you don't actually want this, consider the example of a guy who runs an online store selling expensive widgets. He sells a widget and then gifts the profit to his brother as a birthday present. The brother uses the money to take a girl he just met on a date to a nice restaurant. After they eat the meal and it comes time to pay, the brother gets out his phone only to discover that his money has vanished. The restaurant owner gets angry and the date ends with both of them doing the washing up.

The problem is that the first transaction in this chain was done using stolen coins and the guy who suffered the theft has now unwound all the transactions. The original guys poor security habits (installing warez or whatever) have caused totally innocent people to lose out.

Also consider the case where somebody spends their own coins then lodges a false appeal saying the coins were stolen. They get the coins back and the merchant loses again.

Bitcoin provides a simpler and more straightforward model. Security of your coins is your own problem. If your coins are stolen, tough luck - perhaps you want to insure them next time, or use 2-factor coins, etc.
allten
Sr. Member
****
Offline Offline

Activity: 455
Merit: 250


You Don't Bitcoin 'till You Mint Coin


View Profile WWW
January 01, 2012, 12:59:52 AM
 #9

Gavin,
    This sounds like a nice feature. Thanks for your effort.
Will the fee structure change at all with a multi-sig transaction?
I'm hoping in the future the client will also support many different types of transactions that would appeal to other services than just money transactions. However, this would go beyond what Bitcoin's original intent was and will faten the block chain at a faster pace.
There are so many potential uses for a highly secure distributed database that's open to all -- it's amazing; however, these other services (transaction types) should have a steeper fee structure in my opionion (i.e. x10 the regular transaction fee cost for the last two weeks).

also, it would be nice if some of the fee was sent to a "black hole" (a dummy address); these bitcoins could give the programmers some breathing room if the time ever comes to restructure miner rewards after all the bitcoins are mined.

thanks for your consideration. 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!