<oembed><type>rich</type><version>1.0</version><title>Tomas Susanka [ARCHIVE] wrote</title><author_name>Tomas Susanka [ARCHIVE] (npub1pz…xnfhv)</author_name><author_url>https://yabu.me/npub1pzhqhlvhvdg3ygr8keypprax6gg0qmsrtypmez67few4uzsvhqaqkxnfhv</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2018-06-25&#xA;📝 Original message:Hi,&#xA;&#xA;this is great.&#xA;&#xA;On 23.6.2018 00:28, Achow101 via bitcoin-dev wrote:&#xA;&#xA;&gt; Hi all,&#xA;&gt;&#xA;&gt; After reading the comments here about BIP 174, I would like to propose the following changes:&#xA;&#xA;From my perspective those are exactly the points I have felt strongly&#xA;about. I still think &#34;typed records&#34; would be a better choice, but it&#39;s&#xA;something I&#39;m willing to compromise on. As I&#39;m looking at the draft, we&#xA;currently have 13 records and only 3 of them have keys... Matejcik was a&#xA;bit keener on this, so we&#39;ll try to discuss this more during the week&#xA;and we also look at the draft more carefully to see if we can come up&#xA;with some nit-picks.&#xA;&#xA;&gt; - Encoding&#xA;&gt;&#xA;&gt; I have decided that PSBTs should either be in binary or encoded as a Base64 string. For the latter, several&#xA;&gt; Bitcoin clients already support Base64 encoding of data (for signed messages) so this will not add any extra&#xA;&gt; dependencies like Z85 would.&#xA;&#xA;I agree. If we&#39;re arguing for not using protobuf, because it is a&#xA;dependency, we shouldn&#39;t add dependency for some lesser-known encoding&#xA;format.&#xA;&#xA;As was partially brought up by William, shouldn&#39;t we consider using&#xA;bech32? It doesn&#39;t break on double-click and it is a dependency for&#xA;native Segwit addresses anyway, so wallets might already support it or&#xA;they will at some point. But we should probably run some numbers on this&#xA;first, since bech32 will obviously be larger than base64.&#xA;&#xA;&#xA;On 24.6.2018 10:28, Andrew Chow via bitcoin-dev wrote:&#xA;&#xA;&gt; I disagree with the idea that global types can be removed. Firstly, it&#xA;&gt; is less of a breaking change to leave it there than to remove it&#xA;&gt; entirely. Secondly, there may be a point in the future where global&#xA;&gt; types would be useful/necessary. By having it still be there, we allow&#xA;&gt; for future extensibility.&#xA;&#xA;I agree. It doesn&#39;t hurt if the global section stays and it is more&#xA;forward-looking.&#xA;&#xA;&#xA;Best,&#xA;Tomas&#xA;&#xA;PS: This email didn&#39;t get through at first, so I hope this isn&#39;t a repost.&#xA;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180625/b930777e/attachment.html&gt;</html></oembed>