Blogstamp.org

Purpose

This site creates and validates notarized/certified timestamps for character based content. The site was designed to be a back-end service to blog/cms software. When normal blog content is created, an easily modifiable timestamp is created. It is impossible to tell with any real certainity whether or not the content was created at that time. A certified timestamp guarantees the content was created on the timestamp indicated.

Basic usage

The server responds to two basic requests: stamp and validate. If you need to create a certified timestamp invoke the stamp service. If you need to validate an existing timestamp invoke the validate service.

Source

Coming soon...

Create Timestamp

URL: https://blogstamp.org/blogstamp/stamp

Request: POST content to the URL.

Response: The response will contain the following elements:

• The response header named 'timestamp' contains the certified time. The time is in milliseconds and represents the time since the Unix epoch (Jan 1, 1970).
• The response body contains the digital stamp in hex. The stamp is 156 bytes long and is comprised of [SHA-1 hash of content] + [timestamp] + [digital signature]

Note: This is a one-way process. The data sent to blogstamp.org cannot be reconstructed from the signature.

Validate Timestamp

URL: https://blogstamp.org/blogstamp/validate

Request: POST a form to the URL with the following elements:

• 'edit[timestamp]': the certified timestamp
• 'edit[body]': original content
• 'edit[signature]': the digital signature

Response: A web page showing the signature validity, time of the stamp, and original content.