Brief Product Explanation

DocSure has created a new technology to help you prove the validity of an original document. By providing access to a digital version DocSure ensures the user is always looking at a true and correct document. The patented web application and Quick Response Code system performs document integrity verification using cryptography and HyperLedger / BlockChain technology – thereby detecting and preventing document manipulation.

The Quick Response or QR code and associated signature information in blockchain can never be altered ensuring a document’s content is protected.

Technical Explanation

DocSure is a web application and Quick-Response Code identification system that performs document integrity verification using public-key cryptography and blockchain technology in a novel way.

Its primary use-case is to verify document authenticity by detecting and successfully preventing document forgeries.

For document producers, prior to printing and distributing a document, it is securely transmitted to DocSure. DocSure systems then digitally sign, optionally store and then generate a QR code (

TheDocSure system then either produces a new PDF of the document with the QR code embedded directly, or returns to the document producer the QR code image for inclusion in the final document.

When DocSure-signed documents are presented, parties interested in their authenticity may then simply scan the QR code with their web-enabled camera. The party is then presented with theDocSure document details, including producer, date and time, digital signature, DocSure’s public key and the original document itself for one-to-one comparison and verification with the printed version they were presented.

To enable complete transparent trust and integrity, each DocSure-signed document ID and DocSure signature gets placed into a permanent public record name/value blockchain (

Thanks to the irreversible and public properties of blockchains, this lets end-users confirm that the original authenticity QR code is correct and that the DocSure-presented signature matches the public record and thus initial signature of the document.

DocSure’s Blockchain Importance

DocSure employs strict database access controls such that no record may be inserted, modified or deleted by any staff member. If these access controls were nonetheless ever internally compromised, the blockchain serves as a permanent public record that no individual can modify and that anyone can verify.

In the event DocSure databases were successfully modified for a given document identifier (and thus matching QR Code), there is no known way to modify the associated blockchain record. This is due to well-studied computational complexity and is why blockchain technology is secure.

When a document is presented for authenticity verification, both the DocSure local database signature and the blockchain signature are validated. In addition, end-users can directly examine via third parties all necessary information in the blockchain to do their own authenticity checks against the original document.

In this way, DocSure documents are effectively and securely tamper-proof and successfully thwart advanced forgery attempts.

Document Submission Technicals

All document producers must successfully register as a DocSure client.

Documents may be submitted in any of the following formats:

1) PDF

2) Microsoft Word docx

3) Markdown


5) DocBook

6) LaTeX

7) LibreOffice ODT



When new documents are submitted for registration, the following occurs:

1) A unique random 144 bit identifier is generated and then Base64 encoded to produce a 25 character identifier (ID).

2) QR Code generated with the text content:

3) If not generating a PDF with embedded QR code, go to step 6.

4) Place the QR Code image in one of (upper left, upper center, upper right, lower left, lower center, lower right)

5) Generate PDF Final output

6) Calculate Ed25519 ( signature of either the original document or the generated PDF from step 5. (SIG)

7) If DocSure is hosting the document, store it. Otherwise, retrieve and verify the remote document URL is valid and matches the submitted.

8) Insert into DocSure local database:

a. Submitter details (who/API/etc)

b. Date/Time

c. ID

d. Name (as given by the producer)

e. Size of document (in bytes)

f. SIG

g. Document URL

9) Insert into Trust Anchor Blockchain:

a. id/ID

b. Size of document (in bytes)

c. SIG

10)Return either QR Code image or generated PDF and ID.

11)Display signature and Trust Anchor link.

DocSure’s QR Code Scanning Technicals

All modern phones, tables and personal computing devices with cameras provide default URL web browsing upon QR Code scanning. The DocSure QR code takes them to for any given DocSure-signed document.

Upon visiting the validation URL, DocSure’s system then lookup the ID in local databases and then retrieve the original document (whether stored locally or retrieved remotely). Both signatures from the blockchain and the local database are verified against the retrieved document.

Device-dependent formatting is then presented to the verifying user with:

1) Document Producer Credentials (company, contact address/phone/etc)

2) Document Name (specified by the producer)

3) Submitted Date/Time

4) Document Size

5) Document Signature

6) DocSure’s Ed25519 Public Key

7) Link to Trust Anchor (blockchain inspection)

8) Link to Download Original

9) Original Document

DocSure Application Programming Interface Technicals

In addition to the complete web application, DocSure provides all of its functionality through a simple API. API access requires a valid API Key that can be obtained via the web application interface. Top-level functions:

1) register – Register a new document and produce a QR Code.


a. name: Document Name (needn’t be unique)

b. to_pdf: Boolean as to whether DocSure generates a PDF final document with the QR Code embedded.

c. qr_placement: One of {“ul”,”uc”,”ur”,”ll”,”lc”,”lr”} if to_pdf is true.

d. document: The original document to sign (omit if _url used instead)

e. document_url: The URL of the original document (omit if the document is submitted directly)

f. key: A valid API Key.

2) revoke – Revoke a previously registered document. Parameters:

a. document_id: The 25 character document identifier.

b. key: A valid API Key.

3) verify – Verify a DocSure-generated PDF for authenticity. Parameters:

a. document: The original document to verify (omit if _url used instead)

b. document_url: The URL of the original document (omit if the document is submitted directly)

c. key: A valid API Key.


Consulting (first ipsum from dolor amet nulla)


Deget maximus elementum, odio augue placerat


Tristique et netus et malesuada fames


Lorem ipsum from dolor amet nulla amet glavrida


Class conubia nostra from lorem per inceptos himenaeos