I see. That is undeniably more secure and "bitcoin-y" than my suggestion.<div><br></div><div>It's also really a lot more work, especially in that it requires extra linkages between codebases that in my mind are largely separate. </div>
<div><br></div><div>I'm just one voice, but I persist in believing that the 'lighter' solution, especially for something that may not be a particularly big problem in the bitcoin world is good -- it carries much less technical implementation debt going forward, and has a lower risk of sort of seizing up development with additional necessary code to worry about for those implementing to-spec clients.</div>
<div><br></div><div>If that lighter solution turns out to be gameable, or has problems that require the full force of the bitcoin network and concepts, that would be the time to implement the improved version. That's just my approach, however. I worry that building in any additional requirements to the protocol or codebase adds significant cost to the network as a whole over the next 10 years.</div>
<div><br></div><div>Peter</div><div><div><br><div class="gmail_quote">On Tue, May 29, 2012 at 11:39 AM, Luke-Jr <span dir="ltr"><<a href="mailto:luke@dashjr.org" target="_blank">luke@dashjr.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tuesday, May 29, 2012 3:36:34 PM Peter Vessenes wrote:<br>
> I suppose I mean that I don't understand how to reverse that into a URL<br>
> when one is presented only with a block, or perhaps a coinbase in a<br>
> transaction.<br>
<br>
</div>A new message can be added to the p2p relay network, similar to tx and alert<br>
broadcasts, that allow miners to publish/update their policy URI signed by the<br>
key in question. Counter-DDoS rules could decline to relay or store URIs for<br>
keys that haven't been published in - or achieved statistical significance in<br>
- the last N blocks.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><table style="font-family:Times"><tbody><tr><td><img src="http://coinlab.com/images/coinlab-logo.png"></td><td valign="bottom"><div style="font-family:RobotoLight,'Lucida Grande',Helmet,Freesans,sans-serif;font-size:16px;line-height:20px">
Peter J. Vessenes<br>CEO, CoinLab<br>M: 206.595.9839<br>Skype: vessenes<br><a href="https://plus.google.com/112885659993091300749" target="_blank">Google+</a></div></td></tr></tbody></table><br>
</div></div>