The Vulnerability of Unsealed PDF Documents
Anyone with a basic PDF editor can alter terms, numbers, or dates in an unsealed PDF, making visual signatures alone insufficient to prove authenticity during a legal dispute.
Imagine signing a quote for £5,000, but the counter-party alters the text in Adobe Acrobat to read £8,000. How do you prove what the original document said?
ChickenSign solves this using cryptographic SHA-256 hashing. The moment a document is created, ChickenSign computes its exact binary fingerprint (the content_hash). When all parties complete signing, a second completion fingerprint (completed_hash) is generated, locking the document forever.
If anyone alters the PDF, recalculating the SHA-256 hash immediately produces a completely different string, rendering the document invalid on the public verification portal at /verify/:code.
