How Codel works

Trust from end to end

Codel's three components for proving data immutability, authorship and document integrity;
1. Creating & Registering the Codelmark

Software provided in the browser or through an API uses a secure hashing algorithm to create a unique digital fingerprint of the data known as a ‘Codelmark’, which Codel stores in perpetuity. The ‘Codelmark’ is a unique alphanumeric identifier (normally 64 characters long) created from a file’s contents and stored in Codel's database along with details chosen by the registering party at the time and date of registration. Codel's database is mirrored to multiple locations through a series of cloud-based 'nodes' so there is no single point of failure. Codel never stores the content, i.e. the actual data from which the Codelmark was created. It is infeasible to re-create the original data from the Codelmark and there is therefore no risk of theft or loss of confidentiality. This is because any change whatsoever in the original data contained would produce a distinctly different Codelmark and so, for evidential purposes, registered Codelmarks can prove authorship of data and authenticity of content at a specific point in time.

2. Verification

Data can be verified by anyone, free, without the need to download software or sign up for a service. This can be done directly, by submitting a file to Codel's website to find a match, by using the downloaded Codel software or by integrating the Codel service into software applications so that data can be registered and verified automatically. Download the Codel web application here (works with Internet Explorer and Chrome)

3. Immutable Digital Trust Underpinned by Physically Published, Printed Audit Trails

Codel has been publishing immutable digital audit trails by creating hash chains since 2002 and secures a parallel, non-digital audit trail in the physical world by publishing periodic Codelmarks in the Financial Times, a widely distributed medium (approximately 350,000 copies). Every single copy would need to be destroyed before someone who had gained unauthorised access to the Codel database could either alter or insert a new record without the possibility of detection. See below: