<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Shrewdwatson</id>
	<title>Bitcoin Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Shrewdwatson"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/wiki/Special:Contributions/Shrewdwatson"/>
	<updated>2026-06-09T23:23:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Talk:Myths&amp;diff=7587</id>
		<title>Talk:Myths</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Talk:Myths&amp;diff=7587"/>
		<updated>2011-04-23T17:57:17Z</updated>

		<summary type="html">&lt;p&gt;Shrewdwatson: /* Bitcoin mining is a waste of energy and harmful for ecology  */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Terrorism =&lt;br /&gt;
From the linked Wikipedia page:&lt;br /&gt;
:The USA PATRIOT Act defines terrorism activities as &amp;quot;activities that (A) involve acts dangerous to human life that are a violation of the criminal laws of the U.S. or of any state, that (B) appear to be intended (i) to intimidate or coerce a civilian population, (ii) to influence the policy of a government by intimidation or coercion, or (iii) to affect the conduct of a government by mass destruction, assassination, or kidnapping, and (C) occur primarily within the territorial jurisdiction of the U.S.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This definition is broad enough that it could probably be applied to the Bitcoin system. IANAL but I imagine lawyers could pretty easily demonstrate that Bitcoin is &#039;dangerous to human life&#039; because the Four Horsemen can use it for evil [drug-dealers, money-launderers, terrorists, and pedophiles.]  It can &#039;influence the policy of a government by coercion&#039; by removing options such as Federal Reserve dollars. (C) might be tricky to prove.&lt;br /&gt;
[[User:PLATO|PLATO]] 22:34, 23 March 2011 (GMT)&lt;br /&gt;
&lt;br /&gt;
: besides the one attorney general that made a snide remark about terrorism in the LibertyDollar case, i don&#039;t think that this is in any way a &#039;common misconception&#039;, so i&#039;d question whether we need to have the &#039;terrorism&#039; section at all.--[[User:Nanotube|Nanotube]] 04:02, 24 March 2011 (GMT)&lt;br /&gt;
&lt;br /&gt;
I agree. All yes for removing terrorist stuff? [[User:EvanR|EvanR]] 00:10, 30 March 2011 (GMT)&lt;br /&gt;
&lt;br /&gt;
== Bitcoin mining is a waste of energy and harmful for ecology  ==&lt;br /&gt;
&lt;br /&gt;
IMHO this chapter is superficial. Compare Bitcoin to electronic fiat currencies. --[[User:Shrewdwatson|Shrewdwatson]] 17:57, 23 April 2011 (GMT)&lt;/div&gt;</summary>
		<author><name>Shrewdwatson</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Talk:Block&amp;diff=7583</id>
		<title>Talk:Block</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Talk:Block&amp;diff=7583"/>
		<updated>2011-04-23T13:49:21Z</updated>

		<summary type="html">&lt;p&gt;Shrewdwatson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What if I&#039;m 1% towards calculating a block and...? ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;There&#039;s no such thing as being 1% towards solving a block. You don&#039;t make progress towards solving it.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Is this true?  I don&#039;t know if there&#039;s a nonce which will solve any given block, but for a block that is solvable, it&#039;s possible to be 1% of the way towards finding it.  Supposing it takes 10 million attempts to &#039;solve&#039; a block, then after 100,000 attempts you could say you were 1% towards solving it.  You&#039;re certainly closer to solving it than you were before those 100,000 failed attempts, aren&#039;t you? [[User:Dooglus|Dooglus]] 05:05, 15 January 2011 (GMT)&lt;br /&gt;
:No one can know how many tries it will take to solve the block. After the fact you might say that at some point you had finished 1% of the necessary calculation for that block, but this was not really &amp;quot;progress&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
:If you go back in time after completing a block and don&#039;t generate for one of the days that you did originally, then you could actually end up getting the block &#039;&#039;sooner&#039;&#039;, as the work required is random. [[User:Theymos|theymos]] 11:06, 15 January 2011 (GMT)&lt;br /&gt;
&lt;br /&gt;
Probabilistically speaking, one can make a &amp;quot;best guess&amp;quot; for how long it will take to solve a block. A problem with probabilistic estimation, for example, is that it may say it will take 10 hours to solve the block, with a standard deviation of 15 hours. How much more work do you have when you&#039;ve worked on it for 10 hours? The answer is that you have ~10 hours more work :).&lt;br /&gt;
&lt;br /&gt;
But assuming all incorrect hashes are exhausted first, the maximal number of tries needed to solve the block is ~2&amp;lt;sup&amp;gt;256&amp;lt;/sup&amp;gt;. So, there exists an upper limit (albeit, it is an obscenely large one!) on the amount of work you can do. Progress is made, just very slowly. --[[User:Dlo|Dlo]] 20:28, 11 April 2011 (GMT)&lt;br /&gt;
:That&#039;s not the maximum. You can&#039;t predict the hash outcome, so you could try forever and still get values above the target. You&#039;d get repeat hash values from the same input. [[User:Theymos|theymos]] 03:47, 18 April 2011 (GMT)&lt;br /&gt;
::I can predict the hash outcome by calculating SHA-256 with my mighty x86 processor. :) IMO &amp;quot;predicting&amp;quot; is irrelevant here. Dlo is assuming that the hash function is injective, therefore the number of incomes (giving outcome above the target) &amp;lt;= 2^256. But the hash function is not injective (by the cardinality argument: the set of incomes is infinite and the set of outcomes is finite). --[[User:Shrewdwatson|Shrewdwatson]] 13:49, 23 April 2011 (GMT)&lt;/div&gt;</summary>
		<author><name>Shrewdwatson</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Talk:Block&amp;diff=7582</id>
		<title>Talk:Block</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Talk:Block&amp;diff=7582"/>
		<updated>2011-04-23T13:48:58Z</updated>

		<summary type="html">&lt;p&gt;Shrewdwatson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What if I&#039;m 1% towards calculating a block and...? ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;There&#039;s no such thing as being 1% towards solving a block. You don&#039;t make progress towards solving it.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Is this true?  I don&#039;t know if there&#039;s a nonce which will solve any given block, but for a block that is solvable, it&#039;s possible to be 1% of the way towards finding it.  Supposing it takes 10 million attempts to &#039;solve&#039; a block, then after 100,000 attempts you could say you were 1% towards solving it.  You&#039;re certainly closer to solving it than you were before those 100,000 failed attempts, aren&#039;t you? [[User:Dooglus|Dooglus]] 05:05, 15 January 2011 (GMT)&lt;br /&gt;
:No one can know how many tries it will take to solve the block. After the fact you might say that at some point you had finished 1% of the necessary calculation for that block, but this was not really &amp;quot;progress&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
:If you go back in time after completing a block and don&#039;t generate for one of the days that you did originally, then you could actually end up getting the block &#039;&#039;sooner&#039;&#039;, as the work required is random. [[User:Theymos|theymos]] 11:06, 15 January 2011 (GMT)&lt;br /&gt;
&lt;br /&gt;
Probabilistically speaking, one can make a &amp;quot;best guess&amp;quot; for how long it will take to solve a block. A problem with probabilistic estimation, for example, is that it may say it will take 10 hours to solve the block, with a standard deviation of 15 hours. How much more work do you have when you&#039;ve worked on it for 10 hours? The answer is that you have ~10 hours more work :).&lt;br /&gt;
&lt;br /&gt;
But assuming all incorrect hashes are exhausted first, the maximal number of tries needed to solve the block is ~2&amp;lt;sup&amp;gt;256&amp;lt;/sup&amp;gt;. So, there exists an upper limit (albeit, it is an obscenely large one!) on the amount of work you can do. Progress is made, just very slowly. --[[User:Dlo|Dlo]] 20:28, 11 April 2011 (GMT)&lt;br /&gt;
:That&#039;s not the maximum. You can&#039;t predict the hash outcome, so you could try forever and still get values above the target. You&#039;d get repeat hash values from the same input. [[User:Theymos|theymos]] 03:47, 18 April 2011 (GMT)&lt;br /&gt;
::I can predict the hash outcome by calculating SHA-256 with my mighty x86 processor. :) IMO &amp;quot;predicting&amp;quot; is irrelevant here. Dlo is assuming that the hash function is injective, therefore the number of incomes (giving outcome above the target) &amp;lt;= 2^256. But the hash function is not injective (by the cardinality argument: the set of incomes is infinite and the set of outcomes is finite).&lt;/div&gt;</summary>
		<author><name>Shrewdwatson</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Talk:How_bitcoin_works&amp;diff=7578</id>
		<title>Talk:How bitcoin works</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Talk:How_bitcoin_works&amp;diff=7578"/>
		<updated>2011-04-23T11:41:50Z</updated>

		<summary type="html">&lt;p&gt;Shrewdwatson: predict a cryptographic hash function&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== predict a cryptographic hash function ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Both the chaining, and the difficulty, are achieved via the SHA256 cryptographic hash function. The hash function essentially takes a block of data, and transforms it, in an effectively-impossible to reverse or to predict way, into a large integer. Making the slightest change to a block of data changes its hash unpredictably&amp;quot;&lt;br /&gt;
&lt;br /&gt;
IMO the words &amp;quot;predict&amp;quot;, &amp;quot;unpredictably&amp;quot; is misleading. The SHA256 cryptographic hash function is deterministic, so its result can be predicted by... the same function. :)&lt;br /&gt;
&lt;br /&gt;
The key property is that the reverse function is costly, that&#039;s all.&lt;/div&gt;</summary>
		<author><name>Shrewdwatson</name></author>
	</entry>
</feed>