Nostr Web Client

Found this old email from Sep 2016, just after OpenTimestamps came out:

“I'm cautious about making bold statements about OpenTimeStamps because the

Github commit history shows that until four weeks ago, you had not updated

the code since 2013. The project looks incomplete and you're probably

making changes on a daily basis. The many customers of Tierion find

Chainpoint perfectly suitable for high volume applications.”

Since the SEC shutdown Tieron and forced them to give back all the money from their token sale; OpenTimestamps is still going strong.

https://blockchain.bakermckenzie.com/2021/01/04/sec-settlement-with-tierion-requires-repayment-to-tnt-token-purchasers/

In fact, I'll soon have good news to share about future OTS development!

Reply to this note

Please Login to reply.

Discussion

niftynei() 🇺🇸💸🧡 1y ago

👏 incredibly impressive peter!! cant wait for the new launch

Hypno Kitty 1y ago

Just learned how to use OpenTimestamps to timestamp my utxo spreadsheet for taxes without uploading any personal info to the internet. Thanks.

deeznuts 1y ago

Do tell

Hypno Kitty 1y ago

I used OpenTimeStamps.org, as recommended by Andreas Antonopolous in this vid on the new IRS rules on crypto: https://youtu.be/M1XPOFgjNPk?si=Y8B88gvpXRYy3pCT

Peter Todd 1y ago

Did you use the OpenTimestamps website to do that?

The people who wrote the JavaScript library and made that website are underrated contributors to OTS... I don't know JavaScript at all; their code is probably used by a lot more people than my original Python implementation.

Hypno Kitty 1y ago

Yes, I used OpenTimeStamps.org. Worked liked a charm.

DoctorBug 1y ago

I still remember this useless (and endless) fight with Tierion's CEO... As we say in France, it was a real 'concours de bites' at that time.

I still wonder why open timestamp had to be an undocumented binary format (I know, code is the documentation and bla bla bla).

All this shit was totally unproductive.

My platform (not dead yet) supports both formats anyway, but integration of open timestamp was not easy at that time.

Peter Todd 1y ago

Nah, that was a useful fight. Especially the email I linked to above. In a different timeline Chainpoint might have gotten W3C standardization, screwing over OpenTimestamps adoption. By arguing publicly I was able to make clear to everyone that Chainpoint just wasn't a good protocol, and OTS was.

Re: the binary format, it is documented. Read the protocol spec, the python-opentimestamps library. Though there's little reason to unless you're writing your own OpenTimestamps library; if you aren't, just use an existing library.

DoctorBug 1y ago

Afaik, Open timestamp has not been standardized by W3C neither. Nothing on this scope had been standardized. I don't see any good output form this sterile debate.

You could have worked together propose it to the W3C.