MERIDIAN GLOBAL FINANCE

Verifying the base-33 layer — for developers who shouldn't take our word for it.

The base-33 check runs silently on every ledger page, which is correct behaviour but makes it invisible. This page exists so a reviewing engineer can prove for themselves that it is real, that it is actually running, and — most importantly — that it genuinely catches failures rather than always reporting success. Everything below runs in your browser; nothing is sent anywhere.

First, a precise statement of what this layer is and isn't

Base-33 (Rūnstæf) is a positional numeral system — a way of writing numbers, like binary or hexadecimal. It is not encryption, and nothing on this site claims it encrypts or decrypts data. What it provides is a round-trip integrity check: every ledger value is converted to base-33 and back, and any value that fails to return identical indicates corruption. The cryptography on this site is separate and conventional — SHA-256 hash-chaining via the browser's native WebCrypto API. We state this plainly because a reviewer will establish it in about thirty seconds, and would be right to discount everything else we said if we had implied otherwise.

1. The conversion table, and why these exact codepoints

33 runes, each carrying a fixed digit value 0–32. Unicode codepoints shown explicitly, because five of them (Tir, Beorc, Ac, Æsc, Ing) are visually similar to other runes and were wrong in earlier drafts of this project — a class of bug that is invisible to inspection and only caught by codepoint comparison. Verify against the Unicode Runic block (U+16A0–U+16F0).

2. Run the self-test yourself

Checks the three worked examples from the source specification, then sweeps N random integers through convert-and-convert-back. Change the trial count if you want to hammer it harder.
Not yet run.

3. Prove it actually fails when it should

This is the part that matters. A check that only ever reports "passing" proves nothing — it could be hardcoded. The button below deliberately corrupts the conversion table in memory (mapping digit 1 to the wrong rune), then re-runs the identical test. If the check is real, it must now fail. If it still passes, the check is fake and you should say so.
Not yet run.

4. Verify it on the live pages, not just here

This page could be a purpose-built showcase. The real question is whether the check runs on the actual ledger pages. It does, and you can confirm it directly from the browser console on any of them — the internals are deliberately exposed on a debug handle for exactly this purpose.
Open any of these pages, then the browser console: echelon-ledger-demo.html echelon-sovereign-ledger.html beit-demo.html beit-accounts.html echelon-estc-settlement.html Then run: __runstaef.selfTest() Runs spec examples + a 20,000-trial round-trip sweep on that page's own copy of the functions. Returns a result object. __runstaef.table() The live conversion table with codepoints, as that page holds it. __runstaef.toBase33(1100) Should return the rune string for 1100. __runstaef.ok() Whether every block committed so far on that page has passed. __runstaef.injectFault(true) Corrupts the table. Now perform any action that commits a block (open an account, send a transfer, post a deposit). The status line under the chain indicator should turn red and report FAILED. __runstaef.injectFault(false) Repairs it. The next committed block should pass again. On beit-accounts.html the status line is deliberately hidden (it is the customer-facing view and shows no ledger internals) — there, an injected fault surfaces as a console error instead. The check still runs.

5. What this does and does not prove

Stated plainly, so nothing here is oversold.
Proven by the above: - The conversion is mathematically correct and reversible for arbitrary integers. - The codepoints match the Unicode Runic block exactly. - The check is genuinely wired into block commitment on all five ledger pages. - The check detects corruption rather than always reporting success. NOT proven by the above, and not claimed: - That base-33 encrypts, obfuscates, or secures anything. It does not; it is a numeral system. Integrity here comes from SHA-256 hash-chaining and from strict integer-only validation, both separate from the numeral layer. - That this is a distributed production network. Every ledger page on this site is a single-node, in-browser proof of concept and says so on its own honesty panel. - That the validator quorum is real consensus. It is simulated, and labelled as simulated wherever it appears.