Unsolved Catalogue · no. 2943 · class C · priority 2.1 · open

Four lines of cipher of numerals, letters and invented signs after a Karshuni prayer, in a Syriac-Karshuni miscellany from Midyat (Tur Abdin)

A short private cipher in a Tur Abdin miscellany; possibly Karshuni Arabic, which would make it one of very few Garshuni ciphers on record.

Date
before 1899 (terminus: Sachau's catalogue of 1899); the date of the volume was not read in the catalogue extract
Correspondents
unknown (the clergyman of Midyat who compiled the volume, or a later hand)
Place
Midyat, Tur Abdin
Language
unknown (the volume is Syriac and in smaller part Karshuni, i.e. Arabic in Syriac script; the text just before the cipher is Karshuni)
Held at
Staatsbibliothek zu Berlin, Sachau 218 (Sachau, Verzeichniss der syrischen Handschriften, 1899, no. 188), f. 231a · f. 231a: four lines, 59 signs of 26 shapes in about 13 groups (Dudout's count, 16 Nov 2026), followed (lines 5-9) by instructions for calculating whether a sick person will recover or die
Images
Sachau, Verzeichniss der syrischen Handschriften (archive.org; vol. 2 pp. 614-615)

Hand this page to your AI agent

Give your agent (Claude, ChatGPT or any assistant that can open web pages) this address and ask it to do the task on the page:

https://cyphersolver.com/solve/2943.html

Or copy the block below into the chat. It is the whole task: what the cipher is, where the images are, what has been tried, the steps, and how to report back.

TASK: help read Unsolved Catalogue no. 2943 of the cyphersolver project
This page: https://cyphersolver.com/solve/2943.html

You are helping a public research project read historical cipher letters that nobody has read yet.

THE CIPHER
  Title:          Four lines of cipher of numerals, letters and invented signs after a Karshuni prayer, in a Syriac-Karshuni miscellany from Midyat (Tur Abdin)
  Date:           before 1899 (terminus: Sachau's catalogue of 1899); the date of the volume was not read in the catalogue extract
  Correspondents: unknown (the clergyman of Midyat who compiled the volume, or a later hand)
  Place:          Midyat, Tur Abdin
  Language:       unknown (the volume is Syriac and in smaller part Karshuni, i.e. Arabic in Syriac script; the text just before the cipher is Karshuni) (expected)
  Held at:        Staatsbibliothek zu Berlin, Sachau 218 (Sachau, Verzeichniss der syrischen Handschriften, 1899, no. 188), f. 231a; f. 231a: four lines, 59 signs of 26 shapes in about 13 groups (Dudout's count, 16 Nov 2026), followed (lines 5-9) by instructions for calculating whether a sick person will recover or die
  Images/records:
    - Sachau, Verzeichniss der syrischen Handschriften (archive.org; vol. 2 pp. 614-615): https://archive.org/details/SachauHandschriften23

WHAT IS KNOWN
  Status: Seen 16 Nov 2026 on the SBB digitisation (PPN618589309, image 467 = f. 231r, 2048 x 2853 px): four underlined lines above the Karshuni instructions of lines 5-9; no gloss or key on the leaf or on ff. 230v and 231v. Sachau 1899 no. 188 describes 'vier Zeilen in einer Chiffreschrift, bestehend aus Ziffern, Buchstaben und willkürlich erfundenen Zeichen' and gives no reading. Attempt by Brice Dudout (with Claude Opus 5.5), 16 Nov 2026, PR #706 comment: transcribed twice at 3x and 2x, 59 signs of 26 shapes in about 13 groups (not the 120-160 signs estimated at vetting; the apparent lamadh-alaph ligatures at the end of line 4 are ascenders of line 5); an abjad key frozen in advance (numerals = letter values, red dot = x10) fails (rank 12 of 201 against shuffled keys, no whole word); none of the alphabets on Sachau 116 f. 1r matches; the Syriac atbash table of Sachau 93 f. 75 not tested; Sachau 221 f. 20b is a different ('tree') script and a separate lead. Language (Karshuni or Syriac) and nature not settled: the lines may be a table for reckoning a sick person's recovery, like the instructions below them, rather than a cipher.
  Outcome so far: not yet attempted by the project
  Prior-art check: open as far as checked (16 Nov 2026: known.py, DECODE search, one web search on Sachau 218 with cipher/Geheimschrift: nothing). Tomokiyo, Lasry and the Syriac literature not searched for this item.
  Check first: Open Sachau 218 f. 231a in the SBB digital collections (find the PPN through the Stabikat record) and establish the language and whether it is a magical sign line rather than a cipher; compare the Syriac cipher alphabets that Sachau lists elsewhere in the catalogue (Bardesanes, Simon, Mar Narses: nos. 90, 224 and others).
  Class C: no key and no deciphered sibling is known, so expect a ciphertext-only attack.

STEPS
0. Set up. If you can run a shell, fork and clone the repository and work inside it:
     git clone https://github.com/dbourdeau/cyphersolver.git
   Then read, in this order: CONTRIBUTING.md (how a contribution is sent and credited); README.md, sections
   "Repository layout" and "Conventions" (how readings are measured and named); and
   lang/README.md (shared language models).
   Put all your work in targets/<writer><year>/ (a new folder, e.g. sega1593): transcription, key, decipherment, scripts. Write a NOTES.md that says
   what the document is, the system, the key, the reading, and what is open and why. Keep WORKLOG.md there too:
   one dated line per step (transcription, hypothesis, solver run, crib, key found, control), failures included.
   Do not edit docs/ (the site is generated and rebuilt on merge) and do not commit large images: link them.
   If you cannot run a shell, do the same work in files you keep and send them with the issue below.
1. Make sure it is still unread. Search the web and the literature for the shelfmark, the correspondents and the date:
   printed editions and calendars of the correspondence, Satoshi Tomokiyo's cryptiana pages
   (https://cryptiana.web.fc2.com/), the DECODE record and the files attached to it, and the project notes above.
   If a decipherment already exists, stop and report where it is. That is a useful result.
2. Get the images. For Gallica items, a page image is
   https://gallica.bnf.fr/iiif/ark:/12148/<ark>/f<page>/full/full/0/native.jpg (page numbers from the manifest).
   DECODE records (de-crypt.org) need a free account: if you cannot log in, ask your human to download the images for you.
3. Look for key material before attacking the ciphertext, in this order: a decipherment written between the lines or
   in the margin; a clear copy or a deciphered sibling letter in the same volume or DECODE series; a key sheet from the
   same office and years (DECODE key records, Tomokiyo's articles, printed editions); clear passages in the letter
   itself that can serve as a crib.
4. Transcribe exactly what is on the page: one token per sign or number group, line by line, with folio and line
   numbers, unclear signs marked with ?. Keep the transcription as a file. It is worth sending even if nothing else works.
5. If no key exists, identify the system (count the distinct symbols, tokens and repeats: simple or homophonic
   substitution, nomenclator with code words, syllabary, two-digit figures) and recover the key from the ciphertext
   with a solver scored on a language model of the period (unknown (the volume is Syriac and in smaller part Karshuni, i.e. Arabic in Syriac script; the text just before the cipher is Karshuni)). In the clone, use the shared models in lang/
   (from lang import lm; lm.load('<model>'), lm.best_language(text)) rather than building your own; add a corpus there
   if none fits. Before trusting a result, run the same solver on a control text you encipher yourself in the same
   system and at the same length. If it cannot solve the control, its output on the real letter means nothing.
6. Measure the result against the project's bar (README.md, Conventions). A text is "complete" only when (1) at least
   95% of its cipher tokens give sense, counted from a reading file, not estimated; (2) no gap is left untried;
   (3) every letter in the item is covered; (4) what stays open is scattered code groups or names, or pieces blocked
   from outside (no key material, too short, illegible, needs the archive). Otherwise it is "partial": say which
   pieces are open and why. Mark every uncertain word with [?] and leave unread groups as their numbers or signs.
   Never fill gaps with plausible guesses. A failed attempt that records what was ruled out is still a contribution.
7. Name how the text was obtained with one of the project's methods (do not write just "solved" or "read"):
     - ciphertext-only break: The key was rebuilt from the ciphertext alone: frequencies, solvers, pattern words, the order of the key. No plaintext and no existing key was used. If someone had solved the same text earlier and it was found only afterwards, the write-up says so: an independent re-solution.
     - key from external plaintext: The key was rebuilt by matching the ciphertext against a plaintext found elsewhere: a printed edition, a calendar of state papers, a copy of the same letter in another archive.
     - key from adjacent plaintext: The key was rebuilt from plaintext next to the ciphertext: a partial decipherment written between the lines or in the margin, clear passages in the same letter, a deciphered copy in the same file.
     - external key matched: An existing key that had not been connected with this document (a key for another correspondent or series, a key sheet filed elsewhere) was found to fit, and applied.
     - known key applied: The key was already identified for this document or its correspondence (on its archive or DECODE record, published for it, filed with it) and was applied. The work is transcription and decipherment, which is not mechanical when the key is polyphonic or variable-length.
     - existing decipherment: A complete decipherment already existed (between the lines, on a separate copy, or in print). The work was transcribing the cipher and checking the decipherment against it.
     - not solved: Attempted; neither the key nor the text was obtained. What was learned is recorded. A target whose key was obtained but whose text does not read keeps the method that obtained the key, with extent "none (text not read)".
     - not applicable: Not a cipher (clear text, shorthand, a key sheet, instructions), or the item could not be reached.

REPORT BACK
With a clone: open a pull request with your targets/<writer><year>/ folder. Say in the description how you want to be
  credited (name, initials or handle, and a link) and include the same points as the issue below.
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=solution.yml&title=Solution%3A+catalogue+2943&target=catalogue+2943
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
  - Target: catalogue 2943
  - the documents and the images you worked from;
  - the key: sign-to-value table, code groups with values, nulls;
  - the decipherment line by line against the ciphertext, with uncertain passages marked;
  - the method (step 7), the share of tokens that give sense, complete or partial (step 6), and whether the
    reading was already published anywhere;
  - your step log (WORKLOG.md), and the tools and the AI model you used.
If you cannot open issues or pull requests, write this report for your human to send. Credit goes to the person who sends it.

Where the cipher is

Cipher located and confirmed. A cipher text in an altered Syriac script: word groups joined and spaced as in cursive Serto, in which forms of Syriac letters (vertical alaph or lamadh strokes, mim, waw and he loops) stand together with signs shaped like Eastern Arabic numerals (a 4-shape, a 9-shape, a 2/6-shape) and signs that belong to no script, some carrying red dots in the place of Syriac diacritic points. Sample, line 1 from the right, first group as read here: a dalath/rish-like hook, a 4-shaped sign with a red dot under it, a semkath-like sign; line 4 from the right begins with a mim-like sign, a 4-shaped sign and a vertical stroke. The end of line 4 at the left has forms like Syriac lamadh-alaph ligatures. Sachau's catalogue describes the same lines as 'vier Zeilen in einer Chiffreschrift, bestehend aus Ziffern, Buchstaben und willkürlich erfundenen Zeichen'. No decipherment, gloss or key is written on f. 231r, above or between the lines, and none on f. 230v (end of the Karshuni Prayer of Solomon) or f. 231v (Syriac/Karshuni text). The plaintext language (Syriac or Karshuni Arabic) cannot be judged without reading it. (Staatsbibliothek zu Berlin digital collections, Sachau 218 (PPN618589309; METS https://content.staatsbibliothek-berlin.de/dc/PPN618589309.mets.xml, which labels image 467 as f. 231r), full image https://content.staatsbibliothek-berlin.de/dc/PPN618589309-00000467/full/full/0/default.jpg at 2048 x 2853 px, the four lines cropped at native size and at 2x; images 466 (f. 230v) and 468 (f. 231v) viewed at 2014 x 2853 px; checked 2026-11-16 by Daniel Bourdeau; Claude Code session (Claude Opus 5.5), 16 Nov 2026) open that page

What is known

Status and prior art. Seen 16 Nov 2026 on the SBB digitisation (PPN618589309, image 467 = f. 231r, 2048 x 2853 px): four underlined lines above the Karshuni instructions of lines 5-9; no gloss or key on the leaf or on ff. 230v and 231v. Sachau 1899 no. 188 describes 'vier Zeilen in einer Chiffreschrift, bestehend aus Ziffern, Buchstaben und willkürlich erfundenen Zeichen' and gives no reading. Attempt by Brice Dudout (with Claude Opus 5.5), 16 Nov 2026, PR #706 comment: transcribed twice at 3x and 2x, 59 signs of 26 shapes in about 13 groups (not the 120-160 signs estimated at vetting; the apparent lamadh-alaph ligatures at the end of line 4 are ascenders of line 5); an abjad key frozen in advance (numerals = letter values, red dot = x10) fails (rank 12 of 201 against shuffled keys, no whole word); none of the alphabets on Sachau 116 f. 1r matches; the Syriac atbash table of Sachau 93 f. 75 not tested; Sachau 221 f. 20b is a different ('tree') script and a separate lead. Language (Karshuni or Syriac) and nature not settled: the lines may be a table for reckoning a sick person's recovery, like the instructions below them, rather than a cipher.

Outcome so far. Not yet attempted by the project. Prior-art check: open as far as checked (16 Nov 2026: known.py, DECODE search, one web search on Sachau 218 with cipher/Geheimschrift: nothing). Tomokiyo, Lasry and the Syriac literature not searched for this item..

Check first. Open Sachau 218 f. 231a in the SBB digital collections (find the PPN through the Stabikat record) and establish the language and whether it is a magical sign line rather than a cipher; compare the Syriac cipher alphabets that Sachau lists elsewhere in the catalogue (Bardesanes, Simon, Mar Narses: nos. 90, 224 and others).

Scores

Importance
1 of 5
Solvability
2 of 5
Difficulty
3 of 5
Class C
no key and no deciphered sibling is known, so expect a ciphertext-only attack
Note
Scored from the printed catalogue during the Arabic sweep 2, part C (research/sweep_2026-11-16_arabic_2/); not viewed

Send a result

A reading, a partial reading, a transcription, or a source that shows it was read long ago: all of it counts and is credited to you on the site.

Open a solution issueOther kinds of reportHow credit works← All unsolved ciphers