http://50.77.162.165/mediawiki/index.php?action=history&feed=atom&title=Arbitrary_code_execution_serviceArbitrary code execution service - Revision history2026-04-23T23:16:19ZRevision history for this page on the wikiMediaWiki 1.15.5-7http://50.77.162.165/mediawiki/index.php?title=Arbitrary_code_execution_service&diff=2114&oldid=prev76.179.110.215 at 19:31, 6 November 20102010-11-06T19:31:13Z<p></p>
<p><b>New page</b></p><div>"Trusted third parties" come up a lot in protocols for various things.<br />
<br />
However, there's a bootstrapping problem: if protocol X doesn't have any well-known trusted third parties, then nobody can use protocol X. If nobody is using protocol X, then there's no market for someone to build a "X server".<br />
<br />
If there was a way to price E code (how much cpu, storage, bandwidth, will running this E code consume? How long does this server have to stay up?) then someone could run an "arbitrary code execution service" and people interested in running protocol X could create (and pay for) "X servers", trusting that the arbitrary code execution service's business model is to "be the trusted third party", rather than mining the data flowing through their server, for example.</div>76.179.110.215