Press Kit & Brand Assets

Naming and attribution

A few conventions that save a correction later. They are house style rather than trademark enforcement, and no permission is needed to write about any of this.

Cryptuon is the studio; the products have their own names

Write “Cryptuon’s SolScript” or just “SolScript”, not “Cryptuon SolScript”. The products are independent projects with their own repositories, release cycles, and documentation, and several are useful to people who have no interest in the rest of the portfolio.

Capitalisation follows the repository

Several project names are deliberately lowercase — nklave, dgbit, commit-reveal, blockchain-compression — and are written that way even at the start of a sentence. Zig-EVM keeps its hyphen. Moby Market and DataMgmt Node are two words.

Link to the project, not to this site

When an article is about a specific product, the useful destination for a reader is that product’s own site at <name>.cryptuon.com or its documentation at docs.cryptuon.com/<name>/. This site is an index; the projects are where the substance lives.

Describe status precisely

“Production” on a project card means the interfaces are settled, not that the code has been externally audited. Audit status varies per repository and is stated there. Please avoid “audited” or “battle-tested” unless the specific project’s own documentation supports it.

Numbers should carry their methodology

Where a performance figure appears in Cryptuon material, the measurement setup is published alongside it, and quoting the figure without the configuration usually makes it wrong. The reasoning behind one such set of measurements is written up in Parallel EVM Benchmarks 2026.

For interviews, technical review of a draft, or a fact-check before publication, the contact page reaches us directly. Background on the published work is on the research page, and the full product list is under products.