Unsolved Catalogue · no. 2939 · class B · priority 5.1 · attempted, open

Gordon at Khartoum, note in two-digit Arabic-numeral cipher addressed to the Mudir of Dongola (found 1886 among papers from Dongola)

A cipher in Gordon's own hand from the Khartoum siege, in a two-digit numeric code with plain words mixed in (cribs), plus a candidate key table in the same collection; Hansard 14 Nov 1884 records 'four Arabic cipher letters' reaching Debbeh from Gordon.

Date
1884 (Hijri year digits at the foot not clearly legible at native size: read as 1302 by the sweep, 1300-1302 possible; day read as 16). Covering letter Palmer to Grenfell, 15 Nov 1886
Correspondents
Charles G. Gordon, Khartoum → the Mudir of Dongola (addressee line read from the image as 'to His Excellency Mustafa Pasha, Mudir of Dongola'; name not checked elsewhere)
Place
Khartoum (siege of Khartoum, Mar 1884 - Jan 1885)
Language
Arabic (plaintext presumed; a few Arabic words are written in clear between the groups)
Held at
Durham University Library, Archives and Special Collections, Sudan Archive, Wingate Papers, SAD.250/1/550 (covering letter SAD.250/1/549) · One leaf (SAD.250/1/550): about 14 lines of two-digit Arabic-Indic number groups, roughly 80-95 groups (not counted exactly), a few groups stacked or overwritten as corrections, the addressee and a few words in Arabic script in clear, a date and signature at the foot. The covering letter 549 is a clear English letter
Images
Durham finding aid, Wingate Papers (SAD.250/1/549-550 in the range 528-606) · Digitised SAD.250/1/528-606 (Mirador viewer; leaves 549, 550) · IIIF manifest · Hansard 14 Nov 1884, Gordon's messenger with four Arabic cipher letters

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/2939.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. 2939 of the cyphersolver project
This page: https://cyphersolver.com/solve/2939.html

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

THE CIPHER
  Title:          Gordon at Khartoum, note in two-digit Arabic-numeral cipher addressed to the Mudir of Dongola (found 1886 among papers from Dongola)
  Date:           1884 (Hijri year digits at the foot not clearly legible at native size: read as 1302 by the sweep, 1300-1302 possible; day read as 16). Covering letter Palmer to Grenfell, 15 Nov 1886
  Correspondents: Charles G. Gordon, Khartoum → the Mudir of Dongola (addressee line read from the image as 'to His Excellency Mustafa Pasha, Mudir of Dongola'; name not checked elsewhere)
  Place:          Khartoum (siege of Khartoum, Mar 1884 - Jan 1885)
  Language:       Arabic (plaintext presumed; a few Arabic words are written in clear between the groups) (expected)
  Held at:        Durham University Library, Archives and Special Collections, Sudan Archive, Wingate Papers, SAD.250/1/550 (covering letter SAD.250/1/549); One leaf (SAD.250/1/550): about 14 lines of two-digit Arabic-Indic number groups, roughly 80-95 groups (not counted exactly), a few groups stacked or overwritten as corrections, the addressee and a few words in Arabic script in clear, a date and signature at the foot. The covering letter 549 is a clear English letter
  Images/records:
    - Durham finding aid, Wingate Papers (SAD.250/1/549-550 in the range 528-606): https://reed.dur.ac.uk/xtf/view?docId=ark/32150_s1f4752g79m.xml
    - Digitised SAD.250/1/528-606 (Mirador viewer; leaves 549, 550): https://n2t.durham.ac.uk/ark:/32150/t2mqj72p714z.html
    - IIIF manifest: https://iiif.durham.ac.uk/manifests/trifle/32150/t2/mq/j7/t2mqj72p714z/manifest
    - Hansard 14 Nov 1884, Gordon's messenger with four Arabic cipher letters: https://api.parliament.uk/historic-hansard/commons/1884/nov/14/egypt-events-in-the-soudan-general-gordon

WHAT IS KNOWN
  Status: Attempted 14 Nov 2026 and closed from the evidence (write-up: gordonmudir1884.html, targets/gordonmudir1884/): transcribed (119 groups, 26 distinct values, digits 1-9 in a 7 x 6 grid); the two Arabic columns of the Durham table SAD.250/1/81, as read, do not read it; a letter-substitution attack with controls and crib dragging on the closing groups find nothing. Palmer's covering letter (SAD.250/1/549, 15 Nov 1886) says a Dongola employee, Khalil Ibrahim, 'has the key'. No decipherment is written on the leaf or known; not on DECODE. Left: comparison material that is not digitised (TNA PRO 30/57/4/75-109 at Kew, Durham SAD.101/15), an Arabic reader to check the groups and clear words, a better image of SAD.250/1/81.
  Outcome so far: attempted, open
  Prior-art check: open (checked 14 Nov 2026: DECODE keyword search for Gordon, Khartoum, Dongola, Wingate, Hicks, Sudan Archive: 0 records; Tomokiyo: all 295 cryptiana pages fetched and searched, no Gordon, Sudan or Khartoum cipher page; Lasry/HistoCrypt: web search found only the Biafran ciphers paper, nothing on Sudan; Durham catalogue entry gives no decipherment; Hake's printed edition of Gordon's Khartoum journals mentions undecipherable cipher telegrams but was only searched by text, not for this leaf; repo known.py: no hit for SAD.250, Mudir, Dongola cipher other than the Kitchener leads 1159 and 356)
  Check first: Transcribe the groups from the IIIF image; read the Arabic words and date at the foot; test the SAD.250/1/81 table and the Palmer letter's key remark; compare the four 'Arabic cipher letters' of Nov 1884 and the Kitchener telegrams TNA PRO 30/57/4/77-78 ('use Arabic cipher'), 4/89-109 (Arabic script)
  Class B: part of a key or a known cipher family of the same office is in print or on DECODE.
  Project notes (read these before anything else; they record what was tried and ruled out): https://github.com/dbourdeau/cyphersolver/blob/main/targets/gordonmudir1884/NOTES.md

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); targets/gordonmudir1884/NOTES.md (everything
   already tried on this cipher, with the files it used); and lang/README.md (shared language models).
   Put all your work in targets/gordonmudir1884/: transcription, key, decipherment, scripts. Add your findings to its NOTES.md
   under a dated heading, without rewriting what is there. 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 (Arabic (plaintext presumed; a few Arabic words are written in clear between the groups)). 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/gordonmudir1884/ 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+2939&target=catalogue+2939
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
  - Target: catalogue 2939
  - 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. Re-viewed 14 Nov 2026 at 1000 px (whole leaf) and 1024 px crops of the upper, middle and lower thirds, and the date at native size. Two-digit Arabic-Indic numeral groups in 13 rows of 7, several groups overwritten or stacked under a fraction-style bar (corrections); an addressee line in Arabic script in clear ('To His Excellency Mustafa Pasha, Mudir of Dongola'); a few clear Arabic words between the rows; the closing lines are clear Arabic with a few number groups inside them; date at the foot and Gordon's signature. No plaintext or decipherment is written on the leaf; covering letter 549 does not decipher it. The Hijri year digits are not clearly legible (1300-1302). (https://iiif.durham.ac.uk/manifests/trifle/32150/t2/mq/j7/t2mqj72p714z/manifest, canvases SAD.250/1/549 and SAD.250/1/550, viewed 14 Nov 2026; native-resolution region of the upper left of 550 also viewed; checked 2026-11-14 by claude sweep agent (sweep_2026-11-14_africa_north_east_literature), then re-viewed and checked against Hake by the main session, 14 Nov 2026; contributor not named) open that page

What is known

Status and prior art. Attempted 14 Nov 2026 and closed from the evidence (write-up: gordonmudir1884.html, targets/gordonmudir1884/): transcribed (119 groups, 26 distinct values, digits 1-9 in a 7 x 6 grid); the two Arabic columns of the Durham table SAD.250/1/81, as read, do not read it; a letter-substitution attack with controls and crib dragging on the closing groups find nothing. Palmer's covering letter (SAD.250/1/549, 15 Nov 1886) says a Dongola employee, Khalil Ibrahim, 'has the key'. No decipherment is written on the leaf or known; not on DECODE. Left: comparison material that is not digitised (TNA PRO 30/57/4/75-109 at Kew, Durham SAD.101/15), an Arabic reader to check the groups and clear words, a better image of SAD.250/1/81.

Outcome so far. attempted, open Prior-art check: open (checked 14 Nov 2026: DECODE keyword search for Gordon, Khartoum, Dongola, Wingate, Hicks, Sudan Archive: 0 records; Tomokiyo: all 295 cryptiana pages fetched and searched, no Gordon, Sudan or Khartoum cipher page; Lasry/HistoCrypt: web search found only the Biafran ciphers paper, nothing on Sudan; Durham catalogue entry gives no decipherment; Hake's printed edition of Gordon's Khartoum journals mentions undecipherable cipher telegrams but was only searched by text, not for this leaf; repo known.py: no hit for SAD.250, Mudir, Dongola cipher other than the Kitchener leads 1159 and 356).

Check first. Transcribe the groups from the IIIF image; read the Arabic words and date at the foot; test the SAD.250/1/81 table and the Palmer letter's key remark; compare the four 'Arabic cipher letters' of Nov 1884 and the Kitchener telegrams TNA PRO 30/57/4/77-78 ('use Arabic cipher'), 4/89-109 (Arabic script)

Scores

Importance
4 of 5
Solvability
2 of 5
Difficulty
3 of 5
Class B
part of a key or a known cipher family of the same office is in print or on DECODE
Note
Scored 14 Nov 2026 in the north-east Africa sweep (research/sweep_2026-11-14_africa_north_east_literature/); leaf viewed on Durham's IIIF images (one request returns at most 1024 px per side; region requests give native detail)

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