Oh, hai.<p>I tried this idea in application to the graphic design area specifically targeting logo and brand designers [0]. It was called CertTime and it failed <i>spectacularly</i>. It was pretty much like selling insurance to the ignorant.<p>The actual idea got substantial support of the Logopond community when I first described it [1]. I also solved the usability and trust issue by outsourcing time stamping and actual signing to VeriSign. The service took the client's file, made a self-extracting archive out of it and then signed the exe with Microsoft's AuthentiCode [2]. Checking the time stamp was as easy as right-clicking on the .exe and checking the Digital Signature tab. I think this idea was a stroke of genius... but in the end it did not matter.<p>I got ZERO traction. In retrospect I should've paid closer attention to the lack of interest I got on Typophile [3][4], where the community is more mature and less excitable than on Logopond.<p>That said, there is a number of companies that offer similar service - Surety, GuardTime, Recomobo, Digistamp, MyOws, etc. Some are based around a technical solution [5] while most are based around "we are lawyers, we swear it was done on Jan 1, 1913, and you must trust us" kind of approach. MyOws would be the most active in consumer segment, and they have accumulated their current user base through iPad giveaways and what not.<p>Finally, I want to say - good luck, guys, hope you can pull it off. There is a need for a very simple digital notary service, but it comes with the need to educate your target audience. I was not up for that, but perhaps you are.<p>[0] <a href="http://swapped.cc/certtime" rel="nofollow">http://swapped.cc/certtime</a> and <a href="http://certtime.com" rel="nofollow">http://certtime.com</a><p>[1] <a href="http://pondpad.com/forum/viewtopic.php?id=3578" rel="nofollow">http://pondpad.com/forum/viewtopic.php?id=3578</a><p>[2] <a href="http://msdn.microsoft.com/en-us/library/ms537361(v=vs.85).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms537361(v=vs.85).as...</a><p>[3] <a href="http://typophile.com/node/62669" rel="nofollow">http://typophile.com/node/62669</a><p>[4] <a href="http://typophile.com/node/63838" rel="nofollow">http://typophile.com/node/63838</a><p>[5] <a href="http://www.ietf.org/rfc/rfc3161.txt" rel="nofollow">http://www.ietf.org/rfc/rfc3161.txt</a><p>(<i>edit</i>) Oh, by the way. Regarding the "what is it in you" point. My idea was to establish a sizable userbase of people routinely using the service (in part by integrating with various graphic design galleries and portfolios around the web), use that to demonstrate the consumer-level need for trusted timestamping to VeriSign and other companies and then try and sell the company to them. See, they are in a situation when a lot of money and effort is spent on deploying and running timestamping infrastructure (for example to support codesigning), but they have no way of charging for its services directly. If one can prepare and proof a paid market for them, they could not not be interested.<p>Trying to charge people directly for this sort of service is unrealistic at best.<p>(<i>edit</i>) Dug up the Q&A, which took me several weeks to put together - <a href="http://swapped.cc/certtime/faq.png" rel="nofollow">http://swapped.cc/certtime/faq.png</a> - it has some lesser obvious points to consider and mull over.