Add discussion link

diff --git a/_posts/2016-02-08-moving-forward.md b/_posts/2016-02-08-moving-forward.md
index 733be526a60a78f6a01a446142c897f2235665b8..8879dc29d46489f3dbc15c51d4136021f34da312 100644 (file)
--- a/_posts/2016-02-08-moving-forward.md
+++ b/_posts/2016-02-08-moving-forward.md
@@ -7,6 +7,6 @@ The scaling debate that has been gripping the Bitcoin community for the past hal
 
 With the apparent agreement in the community, it is incredibly disheartening that there is still so much strife, creating a toxic environment in which developers are not able to work, companies are worried about their future ability to easily move Bitcoins, and investors are losing confidence. The way I see it, this broad unification of visions across all parts of the community places the burden of selecting the most technically-sound way to achieve that vision squarely on the development community.
 
-Sadly, because of the way the debate has evolved, what were once technical discussions have become public PR wars. Only recently has any talk of how a hard fork should work taken place in a technical forum, and there has never been any discussion of what a hard fork should look like in the context of segregated witness. For those who are interested, I've started such a discussion with a concrete proposal which you can find [on the bitcoin-dev list]().
+Sadly, because of the way the debate has evolved, what were once technical discussions have become public PR wars. Only recently has any talk of how a hard fork should work taken place in a technical forum, and there has never been any discussion of what a hard fork should look like in the context of segregated witness. For those who are interested, I've started such a discussion with a concrete proposal which you can find [on the bitcoin-dev list](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012403.html).
 
 With this in mind, I'd like to call on the Bitcoin development community to work together to debate, in a civil manner and in a technical forum, the best way to implement the consensus the community appears to have achieved. I ask the greater Bitcoin community to provide feedback to the technical community through every step of the process and the technical community to enable this through its continued efforts to improve communication. Most importantly, I ask that every individual and organization in the Bitcoin community take a step back and take pride in all the progress we've made in forming a nearly unified vision of the short-term future and give the development community the space it needs to reset and have technical discussions over the coming month.