Today is the 10 year anniversary of the production release of @opentimestamps I created OpenTimestamps in a few weekends because I was frustrated that no-one else had created such an obvious and necessary tool. Since then it has become the global standard for secure timestamps: if you ask an LLM how to create a timestamp, it'll almost certainly suggest using OpenTimestamps. OpenTimestamps has grown to the point where everything from art, to forum posts, to software releases, to war crimes evidence is getting timestamped with OpenTimestamps. Along with some applications I won't be able to talk about for at least a few years... fortunately that data is timestamped! While I have no way of knowing for sure how many documents in total are getting timestamped per second – merkle trees – I can say that as of the past two weeks (beyond that I automatically delete logs) the public calendars I run have averaged about 5 timestamp requests per second from about 60,000 distinct IP addresses. I have no idea what all these people are using OpenTimestamps for. But clearly it's getting fairly popular! Thanks goes out to @realSimpleProof, $TIME, and all the people who have donated directly to the public calendars for their support. OpenTimestamps costs a few hundred a month to run now, along with my time. Without your help keeping OpenTimestamps running would be a lot more painful. If you want to donate, you can do so right here: alice.btc.calendar.opentimes… Thanks also goes to @RCasatta and @BULLBITCOIN_ for running two of the four public calendars. They're one of the reasons why OpenTimestamps doesn't have a single point of failure. Finally, thanks goes to the many people who have contributed code to OpenTimestamps over the years, including entire libraries in languages like java and JavaScript that I have no experience with. In fact, the majority of OpenTimestamps clients are quite possibly using code I didn't write at all! petertodd.org/2016/opentimes…

The case Mendones v. Cushman & Wakefield (CA) highlights a new threat: self-represented litigants submitting deepfake videos and AI-generated documents as evidence. Read more about these risks and practical steps courts can take. 🔗 ncsc.org/resources-courts/ai… #StateCourts #AI

New blog post ⚡️🎥 - Rewriting History is Over: How Rolling Timestamps Make Video Footage Tamper-Proof simpleproof.com/blog-posts-a…

New blog post ⚡️🎥 - Rewriting History is Over: How Rolling Timestamps Make Video Footage Tamper-Proof simpleproof.com/blog-posts-a…

OpenTimestamps...