Simply,

 - an address can be frozen for spending
 - can keep one address without worrying about loss of its primary key
 - first primary key is protected by second primary which can be changed as and when required
 - second primary key is only used for lock / unlock (freeze / unfreeze) first address

It is not the same as m*n key because,

  - with m*n, address keep changing, so cannot use one address for all transactions

I am sure it wouldn't require lots of code changes. With some (lot) effort, I can implement all this myself. Real question is should we implement this, and what benefits it bring to the Bitcoin ecosystem.

And, no, surely it wouldn't require a hard fork, and this 'freeze' transaction is not meant to change already created blocks. It is only for new blocks (of course old addresses already in the block can also be used), it will also include transaction fees.

Transactions work in the way we make it work. We do have similar constructs in Bitcoin ecosystem; like, nlocktime.

Really, I didn't get any valid negative points from that thread. Most of the posts are either from me, or people saying it is not possible.

No one explained me how to keep single address for receiving funds, even some casual usage could leak private key, like unencrypted wallet.

So, there are two ways to do this. One, implementing it into Bitcoin client / protocol / transaction, or external (like a firstbits variant)

An idea doesn't have to look good and practical.

May be, I didn't explain it well.

What's the right way to get developer / reputed member's attention for my post without looking like spamming?

1. Personal messages
2. Tag ATTN, attn-sr, attn-hero, etc.
3. PM moderators

So this is my post,

https://bitcointalk.org/index.php?topic=146710.msg

Exploring 'script', and checking possibilities to define public address and firstbits-like shorthand notation (say 'secondbits') outside block chain. With this, I can keep one shorthand address notation and associate it with any public addresses.

And, I have to do this in a way that users don't have to trust 'secondbits' provider.

No, I have already imported it to my Blockchain.info wallet. Again, addresses generated offline is not the same as 'frozen' addresses. 'Frozen' addresses only receive, and will not spend funds.

With 2x2 scheme receiving addresses keep changing.

May be I should put less emphasis on addresses, and throw away old addresses, after all it is free. But, I prefer to keep it forever.

Is it?

Bored? Yes, but only as much as the guy who noticed Bitcoin is reaching parity with one ounce silver.

In other words, I am just interested.

I think, for most peoples, or average salary in BTC is going from 3 digits sum to 2 digits sum.. 

whats the exchange rate for different countries when salary in BTC move from 3 digits sum to 2 digits sum, or <100 BTC?

old (>2010) nokia phones, with Symbian S60. ($20 - $30)
opera mini + offline bitaddress.org
With no SIM, WiFi & Bluetooth (or, turned off)

Technically, other phones could also be useful.
 
whats your ideas..?!  

when I was reading through bitcoin.it, I found some concepts related to this 'offline / frozen address' do exist with bitcoin eco-syatem; like, nlocktime, exit address and contracts.

Now something similar to offline addresses mentioned above, can be done using multi-sign addresses, but in this case, new address keep changing, so it is not possible to use single address for receiving funds forever.

Now to answer an important question, when address creation is so cheep why you want to use one address forever? well, I got my firstbit addresses (1vijay and 1visu) and I don't want to loose it. Using one address as main address for all transactions, and protecting with second set of keys for freeze / unfreeze purposes, is preferable in many cases.

but with the ability to change second "unlock" key will be useful in many cases. so the first address remains safe always, and can receive money even when it was locked.

I still believe this kind of address freezing is the bestest safest way to store / exchange coins.

I will try to explain it further.

Why you think it is not useful, or can't be done?

Good question. I am not planning to freeze my second key, instead I will change them as I prefer. I mean I will freeze with third key, and then unfreeze with second key, so now I would need only third key to unfreeze my address. One unfreezed, now I can use my first private key to spend btc. Immediately after spending I will freeze my address again with third or another new key (4th).

If somehow we can implement this to blockchain, then it would really be useful for everyone.

I will try to explain further with detailed examples, implementation and pros/cons later.

Yes, I am aware of addresses generated offline, and tools used to generate addresses offline.  But, I tried to import private key to my block chain.info wallet and password protected wallet is backed up to many places. My password is quite strong, but I want to have more security for my wallet / address. Like, if I could externally freeze spending from my addresses, I think that would be great.

Whenever I want to spend btc I can unfreeze specific address for short period of time, and then freeze them again (by signing with different keys every time??).

This way I don't have to worry about my wallet getting stolen, because my addresses were frozen for spending.

All this is for I want to keep my firstbit addresses (1vijay, 1visu) forever. I still can create multi-sign (3xx*) addresses with one of these addresses part of it, but that's entirely different story.

Any comments?