MIME-Version: 1.0
In-Reply-To: <7cIbglgQM_K07YQ3dgHTMIQwC_7OXa9DeqFquUZyfuM7HnliTUiIQZuJzo753ICjzUhqh5qLKPbGBVtGGrUT5DvkB7p3YQZePDEtiWd5Xs4=@achow101.com>
References: <CAPg+sBhGMxXatsyCAqeboQKH8ASSFAfiXzxyXR9UrNFnah5PPw@mail.gmail.com>
	<TGyS7Azu3inMQFv9QFn8USr9v2m5QbhDRmiOI-4FWwscUeuIB9rA7mCmZA4-kwCJOMAx92fO7XICHtE7ES_QmIYLDy6RHof1WLALskGUYAc=@achow101.com>
	<c32dc90d-9919-354b-932c-f93fe329760b@satoshilabs.com>
	<CAPg+sBhhYuMi6E1in7wZovX7R7M=450cm6vxaGC1Sxr=cJAZsw@mail.gmail.com>
	<881def14-696c-3207-cf6c-49f337ccf0d1@satoshilabs.com>
	<CAPg+sBg4MCOoMDBVQ2eZ=p3iS3dq506Jh4vUNBmmM20a6uCwYw@mail.gmail.com>
	<95137ba3-1662-b75d-e55f-893d64c76059@satoshilabs.com>
	<RdSjdFhvANrG9ve8bXVnqs68ih5_iVK11jdOAL6WoMI2358TdylR3H2SyGHQfByKwMYYOfIJIOq0l6clYf-az8_D_D-D7cByzqbyYt1nV4c=@achow101.com>
	<c7a4476b-8643-3ddd-723b-1ff8b8910e36@satoshilabs.com>
	<7cIbglgQM_K07YQ3dgHTMIQwC_7OXa9DeqFquUZyfuM7HnliTUiIQZuJzo753ICjzUhqh5qLKPbGBVtGGrUT5DvkB7p3YQZePDEtiWd5Xs4=@achow101.com>
From: Jason Les <jasonles@gmail.com>
Date: Thu, 5 Jul 2018 10:23:51 -0700
Message-ID: <CAHNu4kWLS7Q4rzudLPJu9hUcRVfScgnGRQibnY_+BMqVpq2fjg@mail.gmail.com>
To: Achow101 <achow101-lists@achow101.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000a75eec057043cf67"
Subject: Re: [bitcoin-dev] BIP 174 thoughts
Precedence: list

--000000000000a75eec057043cf67
Content-Type: text/plain; charset="UTF-8"

Has there been any thought to standardizing file names used when creating
.psbt files? Maybe something that gives some reliability of being collision
resistant and descriptive. For example:

[8 char trim of hash of unsigned tx]+[Role that created file (Ex:
Signer)]+[4 char trim of hash of data unique to that role (Ex: partial sig)]

It may be useful to especially the combiner to have some idea of what files
they have.

-Jason Les

--000000000000a75eec057043cf67
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Has there been any thought to standardizing file names use=
d when creating .psbt files? Maybe something that gives some reliability of=
 being collision resistant and descriptive. For example:<div><br></div><div=
>[8 char trim of hash of unsigned tx]+[Role that created file (Ex: Signer)]=
+[4 char trim of hash of data unique to that role (Ex: partial sig)]</div><=
div><br></div><div>It may be useful to especially the combiner to have some=
 idea of what files they have.</div><div><br></div><div>-Jason Les</div></d=
iv>

--000000000000a75eec057043cf67--