Bitcoin Forum
November 10, 2024, 09:22:09 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: offline / frozen addresses
Want
May be
what?
No thanks

Pages: « 1 2 [3]  All
  Print  
Author Topic: offline address - or a way to explicitly freeze an address  (Read 2613 times)
casascius
Mike Caldwell
VIP
Legendary
*
Offline Offline

Activity: 1386
Merit: 1140


The Casascius 1oz 10BTC Silver Round (w/ Gold B)


View Profile WWW
February 28, 2013, 05:02:17 PM
 #41

No matter how you cut it though, if you have a time-locked address, the bad guy has just as much chance of being the person to get the coins the minute the time runs out as the good guy, possibly even more so if the good guy is in a vulnerable position.

Companies claiming they got hacked and lost your coins sounds like fraud so perfect it could be called fashionable.  I never believe them.  If I ever experience the misfortune of a real intrusion, I declare I have been honest about the way I have managed the keys in Casascius Coins.  I maintain no ability to recover or reproduce the keys, not even under limitless duress or total intrusion.  Remember that trusting strangers with your coins without any recourse is, as a matter of principle, not a best practice.  Don't keep coins online. Use paper or hardware wallets instead.
btcusr (OP)
Sr. Member
****
Offline Offline

Activity: 405
Merit: 255


@_vjy


View Profile
February 28, 2013, 05:18:39 PM
 #42

I think, "time-based lock" is different from "frozen".

"time-based lock" is for predefined time, "freezing" is adhoc.

compromised "time-based lock" address, has no protection.
when in doubt, "frozen" addresses can be unlocked, and then locked with new "freeze" key.

DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
February 28, 2013, 05:27:49 PM
 #43

when in doubt, "frozen" addresses can be unlocked, and then locked with new "freeze" key.

You keep saying this.  I give up.
btcusr (OP)
Sr. Member
****
Offline Offline

Activity: 405
Merit: 255


@_vjy


View Profile
February 28, 2013, 05:32:09 PM
 #44

when in doubt, "frozen" addresses can be unlocked, and then locked with new "freeze" key.

You keep saying this.  I give up.

easy for you, I can't do that.  Smiley

I still have to go a long way to answer questions like,
whether this can be implemented?
can I do this?
will this ever be released?

Timo Y
Legendary
*
Offline Offline

Activity: 938
Merit: 1001


bitcoin - the aerogel of money


View Profile
March 01, 2013, 12:24:48 PM
 #45

No matter how you cut it though, if you have a time-locked address, the bad guy has just as much chance of being the person to get the coins the minute the time runs out as the good guy, possibly even more so if the good guy is in a vulnerable position.

True. But my idea is to use the time lock as an additional security feature on top of already existing security features, such as offline wallets and multisig.

Instead of using time locks that expire on a fixed date, I would suggest using 'ratchet' time locks where the expiry date can be postponed indefinitely by the owner of the address.

GPG ID: FA868D77   bitcoin-otc:forever-d
btcusr (OP)
Sr. Member
****
Offline Offline

Activity: 405
Merit: 255


@_vjy


View Profile
March 01, 2013, 11:47:17 PM
 #46

Instead of using time locks that expire on a fixed date, I would suggest using 'ratchet' time locks where the expiry date can be postponed indefinitely by the owner of the address.

so, someone gets they key can extend the lock and prevent you from spending.

how you could postpone a time lock? through a new transaction?

Dabs
Legendary
*
Offline Offline

Activity: 3416
Merit: 1912


The Concierge of Crypto


View Profile
March 09, 2013, 02:32:23 AM
 #47

I still have to go a long way to answer questions like,
whether this can be implemented?
can I do this?
will this ever be released?

1. Probably can not be implemented.
2. Probably no easy way to do it yourself without changing the protocol. It could be client dependent.
3. Probably not ever be released.

Pages: « 1 2 [3]  All
  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!