anchor.diff:  
   <p>To tell us informally, just email <a href="mailto:team@makeyourlaws.org?subject=Comments%20on%20bitcoin%20AOR">team@makeyourlaws.org</a>.</p>
   
  -<p>To tell the FEC formally, just email <a href="mailto:ao@fec.gov?subject=Comments%20AO%202013-19">ao@fec.gov</a> or fax the FEC's Secretary at +1 (202) 208-3333 and Office of General Counsel at +1 (202) 219-3923.</p>
  +<p>To tell the FEC formally, just email <a href="mailto:ao@fec.gov?subject=Comments%20AO%202013-20">ao@fec.gov</a> or fax the FEC's Secretary at +1 (202) 208-3333 and Office of General Counsel at +1 (202) 219-3923.</p>
   
  -<p>Make sure to mention the formal name of our request ("AO 2013-19"). Include your name and the name of any organization you represent. Be clear and polite. Explain how you believe Bitcoins should be treated in campaign finance — and why.</p>
  +<p>Make sure to mention the formal name of our request ("AO 2013-20"). Include your name and the name of any organization you represent. Be clear and polite. Explain how you believe Bitcoins should be treated in campaign finance — and why.</p>
   
  -<p>If you can, it's better to make a more formal-looking comment. General email comments usually get lumped together, whereas if you take a little extra time to make a good-looking PDF and explain your reasoning in more detail, it'll appear separately and be looked at more seriously. There are no mandatory formatting requirements, but we suggest you use 12 pt Arial w/ 1.5 line spacing for body text; 1 inch margin; and have a header saying "(your [group's] name) comments on AO 2013-19" &amp; the page # / # total pages.</p>
  +<p>If you can, it's better to make a more formal-looking comment. General email comments usually get lumped together, whereas if you take a little extra time to make a good-looking PDF and explain your reasoning in more detail, it'll appear separately and be looked at more seriously. There are no mandatory formatting requirements, but we suggest you use 12 pt Arial w/ 1.5 line spacing for body text; 1 inch margin; and have a header saying "(your [group's] name) comments on AO 2013-20" &amp; the page # / # total pages.</p>
   
   <hr/>
   
  
positive.code: <%= t "Bitcoin contributions to PACs" %>
  
  <div class="flash notice l">Our request has been officially submitted, but hasn't yet been posted on the FEC website. We expect that it'll be AO 2013-19, but that number might turn out to be different (if someone else's request gets added before ours).</div>
  
  <p class="c b"><a href="/files/MYL%20PAC%20&%20MYL%20C4%20AOR%20re%20Bitcoin%20contributions.pdf" atrget="_blank">PDF of our full request</a></p>
  
  
negative.code: <a name="aor"></a>
  <h2><a href="#aor">Our request</a></h2>
  
  <p>On December 12, 2013 <%= link_to "we", faq_path %> (i.e. MYL C4 &amp; MYL PAC) submitted <a href="/files/MYL%20PAC%20&%20MYL%20C4%20AOR%20re%20Bitcoin%20contributions.pdf" atrget="_blank">our own advisory opinion request about Bitcoin contributions</a> (formally called "AO 2013-20"), proposing a set of rules and accounting requirements which would permit a reasonable treatment of Bitcoins.</p>
  
  <p>Here's a summary of our proposal:
  	<ol>
  