<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: WARNING: Bitcoins stored in segwit addresses, i.e. addresses that start with a "3" or "bc1" are NOT safe. Please move your coins immediately before a miner "steals" them.</title>
	<atom:link href="http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/feed/" rel="self" type="application/rss+xml" />
	<link>http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/</link>
	<description>198.211.113.164 // 6326 273B 61A7 00AF 4CD9 5A7B 8C6C AB19 24A6 4DEC</description>
	<pubDate>Sat, 18 Jul 2026 19:34:17 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/#comment-610</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Mon, 26 Jul 2021 20:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=496#comment-610</guid>
		<description>Indeed, I was confused. The core of my confusion was mixing up terminology. I was describing what is found in the scriptPubkey as the 'address' which is not exactly correct. The discussion where I had this clarified can be &lt;a href="http://fixpoint.welshcomputing.com/2021/jwrd-logs-for-Jul-2021/#2731" rel="nofollow"&gt;found here.&lt;/a&gt; This confused terminology usage shows up in the prototype of my block explorer, which must be fixed.</description>
		<content:encoded><![CDATA[<p>Indeed, I was confused. The core of my confusion was mixing up terminology. I was describing what is found in the scriptPubkey as the 'address' which is not exactly correct. The discussion where I had this clarified can be <a href="http://fixpoint.welshcomputing.com/2021/jwrd-logs-for-Jul-2021/#2731" rel="nofollow">found here.</a> This confused terminology usage shows up in the prototype of my block explorer, which must be fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/#comment-606</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Fri, 23 Jul 2021 19:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=496#comment-606</guid>
		<description>That's what I thought you meant, so I'm sticking with "confused" not "confusing".

&lt;a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L256" rel="nofollow"&gt;Addresses have version 0&lt;/a&gt; (as &lt;a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L263" rel="nofollow"&gt;implemented&lt;/a&gt;), and &lt;a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L234" rel="nofollow"&gt;that version field becomes the first byte in the binary string to be encoded&lt;/a&gt;.

See also &lt;a href="http://fixpoint.welshcomputing.com/2021/jwrd-logs-for-Apr-2021/#1833" rel="nofollow"&gt;re 'anyonecanspend'.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>That's what I thought you meant, so I'm sticking with "confused" not "confusing".</p>
<p><a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L256" rel="nofollow">Addresses have version 0</a> (as <a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L263" rel="nofollow">implemented</a>), and <a href="http://fixpoint.welshcomputing.com/codeview/tree/bitcoin/bitcoin_dumpblock_no_losers/bitcoin/src/base58.h#L234" rel="nofollow">that version field becomes the first byte in the binary string to be encoded</a>.</p>
<p>See also <a href="http://fixpoint.welshcomputing.com/2021/jwrd-logs-for-Apr-2021/#1833" rel="nofollow">re 'anyonecanspend'.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/#comment-599</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Wed, 21 Jul 2021 19:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=496#comment-599</guid>
		<description>@Jacob Welsh

&gt; A technicality perhaps, but this sounds confused. Isn't it the proper p2pkh addresses that start with a zero byte, which translates to 1 in base58 encoding?

Argh yes that is a good point and makes what I'm say confusing. I mean to say that the bitcoin client allows addresses that start with a 0 byte &lt;b&gt;once decoded&lt;/b&gt; to be treated as anyone-can-spend. (The base58 p2pkh addresses, once decoded, start with 0x76a914)

And I was unaware that this anyonecanspend idea was not an explicit concept, thank you for that clarification.</description>
		<content:encoded><![CDATA[<p>@Jacob Welsh</p>
<p>> A technicality perhaps, but this sounds confused. Isn't it the proper p2pkh addresses that start with a zero byte, which translates to 1 in base58 encoding?</p>
<p>Argh yes that is a good point and makes what I'm say confusing. I mean to say that the bitcoin client allows addresses that start with a 0 byte <b>once decoded</b> to be treated as anyone-can-spend. (The base58 p2pkh addresses, once decoded, start with 0x76a914)</p>
<p>And I was unaware that this anyonecanspend idea was not an explicit concept, thank you for that clarification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://ztkfg.com/2021/07/warning-bitcoins-stored-in-segwit-addresses-are-not-safe/#comment-598</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Wed, 21 Jul 2021 18:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=496#comment-598</guid>
		<description>&#62; contains a rule where outputs that go to an address starting with a "0" byte are treated as anyone-can-spend

A technicality perhaps, but this sounds confused. Isn't it the proper p2pkh addresses that start with a zero byte, which translates to 1 in base58 encoding? And the original bitcoin doesn't have "anyone can spend" as any kind of expressed concept or special rule. You could argue it's latent in the "script" system since it allows creating trivially-true scripts, but that isn't even necessary - simply publishing a private key would have the effect of creating an "anyone can spend" address.

&#62; signpost: contrary to the teachings of mp, declaring victory is not all that is required.

FTR, that doesn't sound like anything I ever heard from MP or saw implicit in his actions. Perhaps it was what certain students wanted to hear. In declarations, as any other text, &lt;em&gt;who's saying it makes all the difference.&lt;/em&gt; There's also MP's comment on &lt;a href="http://trilema.com/2012/why-its-not-actually-in-your-best-interest-to-allow-a-hired-third-party-to-speak-for-you-in-criminal-proceedings/#comment-155972" rel="nofollow"&gt;sitting around thinking you've won&lt;/a&gt; as a strategy.</description>
		<content:encoded><![CDATA[<p>&gt; contains a rule where outputs that go to an address starting with a "0" byte are treated as anyone-can-spend</p>
<p>A technicality perhaps, but this sounds confused. Isn't it the proper p2pkh addresses that start with a zero byte, which translates to 1 in base58 encoding? And the original bitcoin doesn't have "anyone can spend" as any kind of expressed concept or special rule. You could argue it's latent in the "script" system since it allows creating trivially-true scripts, but that isn't even necessary - simply publishing a private key would have the effect of creating an "anyone can spend" address.</p>
<p>&gt; signpost: contrary to the teachings of mp, declaring victory is not all that is required.</p>
<p>FTR, that doesn't sound like anything I ever heard from MP or saw implicit in his actions. Perhaps it was what certain students wanted to hear. In declarations, as any other text, <em>who's saying it makes all the difference.</em> There's also MP's comment on <a href="http://trilema.com/2012/why-its-not-actually-in-your-best-interest-to-allow-a-hired-third-party-to-speak-for-you-in-criminal-proceedings/#comment-155972" rel="nofollow">sitting around thinking you've won</a> as a strategy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
