August 5, 2026

JSON got a dramatic new cousin

TSON – A JSON superset with immutable, hash-pinned schemas

A new JSON rival drops, and the comments instantly split into hype, side-eye, and jokes

TLDR: TSON is a new JSON-like format that locks data rules in place so files can be checked and trusted more easily. Commenters were split between “finally, this is smart,” “why not just use JSON,” and jokes about tech inventing endless new formats for sport.

A shiny new data format called TSON just strutted onto the internet promising something developers obsess over: data that comes with a locked-in, verifiable rulebook. In plain English, it’s a new way to write data files that aims to be easier on the eyes than JSON, while also making sure the “schema” — the set of rules describing what the data should look like — can’t quietly change behind your back. The creator says one hash can verify the whole chain, and there’s already a working Java tool you can try on GitHub.

But let’s be honest: the real action was in the comments. One camp was immediately sold, calling hash-pinned schemas “definitely the right direction” for trust and provenance. Translation: if you care about knowing exactly what rules your data followed, this sounds like catnip. The other camp came in hot with the classic internet question: “Why invent a whole new format?” One commenter basically asked why this couldn’t just be bolted onto regular JSON, which is the kind of blunt skepticism that launches a thousand reply threads.

Then came the comedy. Someone joked about the inevitable rise of “xson”, complete with “xpathson” and “xsdson,” roasting tech’s endless habit of creating sequels nobody asked for. Another commenter spotted strong EDN vibes — a format beloved by some programmers — but also threw side-eye at optional quotes around strings, calling that choice suspicious. And in perfect comment-section fashion, one person skipped the philosophy war entirely to point out a broken GitHub link. Drama, nitpicks, hype, memes: the full developer-comment bingo card was filled.

Key Points

  • TSON is presented as a schema system with immutable, hash-pinned schemas where one hash can verify a document, its schema, and its meta-schema chain.
  • TSON data and schema documents use the same lexer, tooling, and verification model, and the format is described as a Unicode-first superset of JSON.
  • The article provides a working implementation, tson-java, with CLI commands for generating example files and validating data against schemas.
  • TSON schemas support explicit field-state declarations, including required fields by default, defaults with `~`, pinned values with `=`, and optional fields with `?`.
  • The article details additional schema features including arrays, tuples, sets, atom refinements, enums, composition, refinement, and subtraction, and says the design is based on an eighteen-part research series.

Hottest takes

"definitely the right direction" — myshapeprotocol
"why can't you use hash pinned schemas with existing json?" — flanked-evergl
"when will be xson invented" — azatom
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.