Contribute · five ways in

How to contribute

The ledger records historical ciphers: what has been deciphered, by whom, and how. Anyone can add to it. A contribution is credited by name on the write-up it belongs to and on the contributors page, whether it arrives as a GitHub pull request, an issue or an email.

Five kindsHow to sendHow credit worksWhat happens nextTo the archiveContributors

Daniel Bourdeau and contributors · posted · updated

01 Five kinds of contribution

A solution to a cipher already in the ledger

Any target in the catalogue, any write-up marked not solved, and any open item in the notes. Send:

A fuller reading of one left partial

Many write-ups are read only in part. Their notes list what is still open and why: code groups with no value yet, lines hard to read on the images, letters for which no key is known, pieces that need the original in the archive. The list of readings to take further shows each one with its open gaps, the most workable first. You do not need to finish a reading to help: one step is enough. Send:

Each step is credited on the write-up, and the reading’s extent is re-measured with it.

A visit or a request to an archive. Some gaps can only be closed from the original or from a book the project cannot reach: a line lost in the binding, a leaf never photographed, a decipherment in a volume that was not digitised, an edition behind a login. They are listed by archive and city on To the archive. Take one on with the “I can do this” link (it opens the archive-request form with the request filled in), then send the photographs, the reproduction or the passage. A visit that finds nothing is reported and credited too.

A new unsolved cipher

A ciphered document with no known decipherment that is not in the ledger yet. Send:

A new cipher with its solution

Both of the above: the document, then the key, the full transcription and decipherment, and how you obtained them. Results that have never been published are welcome; say whether they may be shown here in full or only noted.

A verification of a reading already here

The verification queue lists the readings whose key was recovered or matched here and that no one outside the project has checked. Take the images and the key from the write-up, decipher a passage yourself (a paragraph is enough), and report:

A check that finds errors is as useful as one that confirms. Both are credited.

02 How to send it

On GitHub. Open an issue with one of the forms at github.com/dbourdeau/cyphersolver/issues/new/choose (solution, fuller reading, new cipher, new cipher with solution, verification), or send a pull request. The repository’s CONTRIBUTING.md explains the folder layout and the files a target keeps.

By email. Not on GitHub? Write to with the same details and any files. The entry is made for you and credited the same way.

03 How credit works

04 What happens next