From joseph at lightning.network  Fri Jul 24 22:38:28 2015
From: joseph at lightning.network (Joseph Poon)
Date: Fri, 24 Jul 2015 15:38:28 -0700
Subject: [Lightning-dev] commitment update steps
In-Reply-To: <CAJS_LCW7uJmR6-0CERrW4wJBfa_p=k_YfCg0i=Gbu212uibVYw@mail.gmail.com>
References: <CAJS_LCX8vaZtdC0XmECGyit19ZJv-pXBWeaHbPrt-6Jo9-t2kg@mail.gmail.com>
	<87egjyqt02.fsf@rustcorp.com.au>
	<CAJS_LCW7uJmR6-0CERrW4wJBfa_p=k_YfCg0i=Gbu212uibVYw@mail.gmail.com>
Message-ID: <20150724223828.GA18345@lightning.network>

Hi Anthony,

If we're presuming everyone uses OP_CSV in the long-term, you can
overload nLockTime with values below current unixtime as a
filter/counter. It should be enough bits of entropy no matter the size
(even in the billions of transactions in a single channel) Since both
parties are signing the nLockTime value, it's safe to use that as an
identifier in the Commitment Transaction.

-- 
Joseph Poon