Cryptographically verifiable created_at / updated_at scalars

[seref]

Is it possible to utilize the DateTime data type to create cryptographically verifiable datetime fields?

Another option might be to have “updated_at” and “created_at” scalars. Created_at as the first commit’s datetime, and the updated_at as the last.

Since these fields are very common, it would be helpful to access them via GraphQL.

[seref]

Ahh, duplicate.

Feature request: createdAt and updatedAt fields on model

Ah, well we do track those values in the indexing database, but that will just be the timestamps when the local node learned about the stream/update, not necessarily when the create/update actually originally happened. The best way to tell when a stream was created or updated is to check the stream log for anchor commits and see when the anchors happened. It’s not perfectly precise, but will give you a general sense for when the various commits in the stream were created.

[spencer]

yep, every update to streams gets periodically anchored to the Ethereum blockchain, which provides cryptographically verifiable timestamps. Those aren’t currently queryable (for filters or sorts for example) directly from GraphQL, but that’s something we could potentially add in the future if helpful. Even without that though if you do a regular composedb query, the ModelInstanceDocument objects you get back from the result of the query will have the anchor timestamp information in the returned state object.