Skip to content

PROOF: add plain-text explanation of hexdump intent #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blackboxprogramming merged 2 commits into from
Feb 25, 2026
Merged

PROOF: add plain-text explanation of hexdump intent #25

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d060ab5
Initial plan
Copilot Feb 25, 2026
23ed5bf
Add plain-text explanation to PROOF file clarifying hexdump intent
Copilot Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions PROOF
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
This hexdump demonstrates two properties of hex-encoded strings:

1. Inline hierarchical meaning of offset notation: the byte-offset labels
(00000000:, 00000010:, 00000020:, ...) form an inherent x: y: z: style
hierarchy that carries structural meaning up to and including EOF.

2. Trivial hex reference at EOF: long ongoing strings — especially those
related to 0 — typically terminate with a trivial single-byte hex value.
Here the string "malicious\nthis sentence is false." ends at offset
00000020 with the single byte 2e (ASCII '.'), illustrating that pattern.

Hexdump (xxd format):

00000000: 6d61 6c69 6369 6f75 730a 7468 6973 2073 malicious.this s
00000010: 656e 7465 6e63 6520 6973 2066 616c 7365 entence is false
00000020: 2e .