path: root/d9/44c254714bf210a191d1d52aa52797043901b5

Return-Path: <scott@adligo.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DC97DAD5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 13 Jan 2016 23:47:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com
	[209.85.223.170])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2144B125
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 13 Jan 2016 23:47:51 +0000 (UTC)
Received: by mail-io0-f170.google.com with SMTP id 77so404555937ioc.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 13 Jan 2016 15:47:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=adligo-com.20150623.gappssmtp.com; s=20150623;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=wWNzQeSQdGaukfKU4pKODiJe8FGN2vBlgutiBcNbEkc=;
	b=vBis6SVvZZsxWqQDUT4vYKnyaRxdap2bcaVivgzMChJ6LZJMEa4HR3Dh8yKRH8IPVK
	cOtmnPp1oLBoNvQen5nAt3xPQUnOLjoU1fAhnyHivpDtXqhq6fvOFZ0vbHs46t4bRd+K
	XRTxV2B4y9ru7G8YJk37+ETBGLWDoZvvCTnGTZt8wwFuys4Q3XtuMIRwBUhUQvd7OohA
	sQIU93l4ojLtPepeoh97b851Op4TGEq/NJKo98YwA/FGI2wWMIBEdOH5OZtib13C4fIC
	+V4dv0KEHQNt7f5EO05BLjvSpPiR+f1HK35VrklkVWCs6a1VVQasrtcug3nAjNSEeR4j
	Jy7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type;
	bh=wWNzQeSQdGaukfKU4pKODiJe8FGN2vBlgutiBcNbEkc=;
	b=MIpRzW68ffRVmwwt1iCLFCrkRQrucYW0XUbyPLPpT583dnsfgVLfQ5sDYCjNltjjEr
	NJ5/h6q5FOXLl4tyS9nTfmB50yBUy2lYVNwTZvv+ITDdtbE1Wjq0A5jYI893lc8P6Rq/
	XItw/G7MtZw2tsJEHR1F3hG+pEc4lhz6USc+myt1w1w7VC7eIFPCkh7BTaiC2RsIW4Kz
	lhMsZmFA6jr4rjY2NVU5YFSdcTTSJjXjw+0kLwhG3ND8AhYewUpy1sjPb8iECqWMYn0j
	R/uNh4ZAg9EUK2uirgkFFcKDz68OuxQIiDgQRfrPkgp4vSdhLu9C8R/w2EueVA7uJAeF
	i23A==
X-Gm-Message-State: ALoCoQnFeq1QlcEV/155et8ozTWLTFLo6bb08FvQ7M/F+EcYn02g7T0Fpfp/WyWFqXljgmFDWV+xqSojn/oBuEUVRm1P5WtObg==
MIME-Version: 1.0
X-Received: by 10.107.132.221 with SMTP id o90mr1865216ioi.137.1452728870492; 
	Wed, 13 Jan 2016 15:47:50 -0800 (PST)
Received: by 10.64.35.19 with HTTP; Wed, 13 Jan 2016 15:47:50 -0800 (PST)
In-Reply-To: <CANEdHmjczpys1RMaZAahE-L==xMDzuVT=eyVApCxU_AHswtEYQ@mail.gmail.com>
References: <CANEdHmjczpys1RMaZAahE-L==xMDzuVT=eyVApCxU_AHswtEYQ@mail.gmail.com>
Date: Wed, 13 Jan 2016 17:47:50 -0600
Message-ID: <CANEdHmgBkwLxJNqEwoWCVL7Vrsiv8WZReJp2so+UvMG1A38Gmg@mail.gmail.com>
From: Scott Morgan <scott@adligo.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a113fe5b647f2a205293fcc63
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 13 Jan 2016 23:57:05 +0000
Subject: [bitcoin-dev] Fwd: Wallet Lock, Unlock BIP idea
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 23:47:52 -0000

--001a113fe5b647f2a205293fcc63
Content-Type: text/plain; charset=UTF-8

Hi All,

   Here is a suggestion which is similar to bip-0065, but slightly
different.
In a nutshell I under stand bip-0065 to do this;
Create a transaction adding a lock time, that the recipient user must wait
before they can spend the coins.

My proposal is to do this;
Create an entry in the blocks to lock entire wallet addresses indefinitely,
with a specified unlock period.
Later on create / modify an entry in the blocks to acknowledge the wallet
is being unlocked.
Remove the lock on the wallet after the unlock period has transpired.

  I think it is technically feasible since many wallet addresses are in
each block at the transaction level.  However, it would have huge
implications to the entire Bitcion ecosystem, so it would probably need a
start date at least a year in the future after it was developed.

bip-0065 would not allow the following;
  This would allow users holding coins for long periods to monitor the
blockchain to see if someone else is unlocking their wallets (which may
have been stolen/copied etc), giving them some time to react to a
intrusion.  Perhaps there should also be a re-lock (during unlock) feature.

My original message is attached.

Cheers,
Scott

---------- Forwarded message ----------
From: Scott Morgan <scott@adligo.com>
Date: Tue, Jan 12, 2016 at 3:35 PM
Subject: Wallet Lock, Unlock BIP idea
To: bitcoin-dev@lists.linuxfoundation.org


Hi All,

   It seems to me that one of the large issues with bitcoin is that they
can be stolen like cash.   This issue also culminates with the fact that
most miners probably need to hold their coins for some time to be
profitable due to the large interest in mining.
   I think it may be possible to reduce some of this theft by adding a BIP
to lock and unlock wallets.  Here is the basic idea (probably with some
holes);

   1) Users could 'lock' their wallet specifying a unlock period (i.e. 15
days)
       The information that a particular wallet is locked would get added
to the blocks and confirmed like other transactions.
    2) During transaction creation and mining (to be sure a locked wallet
isn't drained) the top blocks would be checked to see if the wallet is
locked.  Locked wallet transactions would not be confirmed.
    3)  Users would eventually 'unlock' their wallet.
        This would put a unlocking as of date time in the blocks to specify
a wallet is unlocking.  Eventually the wallet would not have any lock or
unlocking entries in the blocks.
    4) The users would wait the unlock period (i.e. 15 days)
    5) The Users could then spend their coins.


   This would also have some other consequences on the bitcoin system,
since anyone could check the transactions to locked wallets to see how many
BTC are being held, or are being unlocked soon.   This could effect the
price of BTC in fiat as supply would change similar to the way mining
changes it.  Also it will slow transaction creation a little and mining a
fair amount.
   Also locking a wallet might incur a fee.

  What are your thoughts, does this idea qualify for a BIP?
  If so, I would appreciate it if someone takes it and runs with it.

Cheers,
Scott

PS A bit about me, I am a Privacy and Java evangelist, so I will not be
doing any work on the main bitcoin core.  I have been doing a little mining
to attempt to help fund my companies (Adligo Inc) open source Java projects
Tests4j and Fabricate and hopefully in the future Taxi, Sanctum and
Intelligence4j.

Donations are always welcome;

http://www.plumfund.com/crowdfunding/adligoorg

--001a113fe5b647f2a205293fcc63
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi All,<div><br></div><div><font face=3D"monospace, monosp=
ace">=C2=A0 =C2=A0Here is a suggestion which is similar to bip-0065, but sl=
ightly different.</font></div><div><font face=3D"monospace, monospace">In a=
 nutshell I under stand bip-0065 to do this;</font></div><div><font face=3D=
"monospace, monospace">Create a transaction adding a lock time, that the re=
cipient user must wait before they can spend the coins.</font></div><div><f=
ont face=3D"monospace, monospace"><br></font></div><div><font face=3D"monos=
pace, monospace">My proposal is to do this;</font></div><div><font face=3D"=
monospace, monospace">Create an entry in the blocks to lock entire wallet a=
ddresses=C2=A0<span style=3D"line-height:100%">indefinitely</span>, with a =
specified unlock period.</font></div><div><font face=3D"monospace, monospac=
e">Later on create / modify an entry in the blocks to acknowledge the walle=
t is being unlocked.</font></div><div><font face=3D"monospace, monospace">R=
emove the lock on the wallet after the unlock period has transpired.</font>=
</div><div><font face=3D"monospace, monospace"><br></font></div><div><font =
face=3D"monospace, monospace">=C2=A0 I think it is t<span style=3D"line-hei=
ght:100%">echnically
feasible</span>=C2=A0since many wallet addresses are in each block at the t=
ransaction level.=C2=A0 However, it would have huge implications to the ent=
ire Bitcion ecosystem, so it would probably need a start date at least a ye=
ar in the future after it was developed.=C2=A0</font></div><div><font face=
=3D"monospace, monospace"><br></font></div><div><font face=3D"monospace, mo=
nospace">bip-0065 would not allow the following;</font></div><div><font fac=
e=3D"monospace, monospace">=C2=A0 This would allow users holding coins for =
long periods to monitor the blockchain to see if someone else is unlocking =
their wallets (which may have been stolen/copied etc), giving them some tim=
e to react to a intrusion.=C2=A0 Perhaps there should also be a re-lock (du=
ring unlock) feature.</font></div><div><font face=3D"monospace, monospace">=
<br></font></div><div><font face=3D"monospace, monospace">My original messa=
ge is attached.</font></div><div><font face=3D"monospace, monospace"><br></=
font></div><div><font face=3D"monospace, monospace">Cheers,</font></div><di=
v><font face=3D"monospace, monospace">Scott</font></div><div><span style=3D=
"font-size:12.8px"><br></span><div class=3D"gmail_quote">---------- Forward=
ed message ----------<br>From: <b class=3D"gmail_sendername">Scott Morgan</=
b> <span dir=3D"ltr">&lt;<a href=3D"mailto:scott@adligo.com">scott@adligo.c=
om</a>&gt;</span><br>Date: Tue, Jan 12, 2016 at 3:35 PM<br>Subject: Wallet =
Lock, Unlock BIP idea<br>To: <a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org">bitcoin-dev@lists.linuxfoundation.org</a><br><br><br><div dir=3D=
"ltr"><font face=3D"monospace, monospace">Hi All,</font><div><font face=3D"=
monospace, monospace"><br></font></div><div><font face=3D"monospace, monosp=
ace">=C2=A0 =C2=A0It seems to me that one of the large issues with bitcoin =
is that they can be stolen like cash. =C2=A0 This issue also culminates wit=
h the fact that most miners probably need to hold their coins for some time=
 to be profitable due to the large interest in mining.</font></div><div><fo=
nt face=3D"monospace, monospace">=C2=A0 =C2=A0I think it may be possible to=
 reduce some of this theft by adding a BIP to lock and unlock wallets.=C2=
=A0 Here is the basic idea (probably with some holes);</font></div><div><fo=
nt face=3D"monospace, monospace">=C2=A0 =C2=A0</font></div><div><font face=
=3D"monospace, monospace">=C2=A0 =C2=A01) Users could &#39;lock&#39; their =
wallet specifying a unlock period (i.e. 15 days)</font></div><div><font fac=
e=3D"monospace, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0The information that =
a particular wallet is locked would get added to the=C2=A0</font><span styl=
e=3D"font-family:monospace,monospace">blocks and confirmed like other trans=
actions. =C2=A0</span></div><div><font face=3D"monospace, monospace">=C2=A0=
 =C2=A0 2) During transaction creation and mining (to be sure a locked wall=
et isn&#39;t drained) the top blocks would be checked to see if the wallet =
is locked.=C2=A0 Locked wallet transactions would not be confirmed.</font><=
/div><div><font face=3D"monospace, monospace">=C2=A0 =C2=A0 3) =C2=A0Users =
would eventually &#39;unlock&#39; their wallet.</font></div><div><font face=
=3D"monospace, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 This would put a unlo=
cking as of date time in the blocks to specify a wallet is unlocking.=C2=A0=
 Eventually the wallet would not have any lock or unlocking entries in the =
blocks.</font></div><div><font face=3D"monospace, monospace">=C2=A0 =C2=A0 =
4) The users would wait the unlock period (i.e. 15 days)</font></div><div><=
font face=3D"monospace, monospace">=C2=A0 =C2=A0 5) The Users could then sp=
end their coins.</font></div><div><font face=3D"monospace, monospace"><br><=
/font></div><div><font face=3D"monospace, monospace"><br></font></div><div>=
<font face=3D"monospace, monospace">=C2=A0 =C2=A0This would also have some =
other=C2=A0<span style=3D"line-height:100%">consequences</span>=C2=A0on the=
 bitcoin system, since anyone=C2=A0could check the transactions to locked w=
allets to see how many BTC are being held, or are being unlocked soon. =C2=
=A0 This could effect the price of BTC in fiat as supply would change simil=
ar to the way mining changes it.=C2=A0 Also it will slow transaction creati=
on a little and mining a fair amount.</font></div><div><font face=3D"monosp=
ace, monospace">=C2=A0 =C2=A0Also locking a wallet might incur a fee.</font=
></div><div><font face=3D"monospace, monospace"><br></font></div><div><font=
 face=3D"monospace, monospace">=C2=A0 What are your thoughts, does this ide=
a qualify for a BIP?</font></div><div><font face=3D"monospace, monospace">=
=C2=A0 If so, I would appreciate it if someone takes it and runs with it.</=
font></div><div><font face=3D"monospace, monospace"><br></font></div><div><=
font face=3D"monospace, monospace">Cheers,</font></div><div><font face=3D"m=
onospace, monospace">Scott</font></div><div><font face=3D"monospace, monosp=
ace"><br></font></div><div><font face=3D"monospace, monospace">PS A bit abo=
ut me, I am a Privacy and Java=C2=A0<span style=3D"line-height:100%">evange=
list, so I will not be doing any work on the main bitcoin core.=C2=A0 I hav=
e been doing a little mining to attempt to help fund my companies (Adligo I=
nc) open source Java projects Tests4j and Fabricate and hopefully in the fu=
ture Taxi, Sanctum and Intelligence4j.</span></font></div><div><span style=
=3D"line-height:100%"><font face=3D"monospace, monospace"><br></font></span=
></div><div>
=09
=09
=09


<p style=3D"margin-bottom:0in"><span style=3D"line-height:13px"><font face=
=3D"monospace, monospace">Donations are always welcome;</font></span></p><p=
 style=3D"margin-bottom:0in"><span style=3D"line-height:13px"><font face=3D=
"monospace, monospace"><a href=3D"http://www.plumfund.com/crowdfunding/adli=
goorg" target=3D"_blank">http://www.plumfund.com/crowdfunding/adligoorg</a>=
</font></span><br></p></div>
=09
=09
=09


<div><br></div></div>
</div><br></div></div>

--001a113fe5b647f2a205293fcc63--