Before you buy, you should know what is proven, what is still early, and what we will never do. Here it is, without the fine print.
We contract for the outcome and answer for it. “Done” is written down before work starts. Every claim here links to something you can check — or is labelled as not yet proven.
11 of our 20 open-source projects are rated “Documented” — public, but not yet independently verified. None has a published third-party audit yet. We test anything on your workload before recommending it.
Hold your funds or keys, trade for you, promote tokens, promise returns, or pass off our own review as an independent audit.
Four steps. A project moves up only when there is something to show for it — a page saying “supports X” is the first step, not the last.
Step 1
The design and code are public, but nobody outside the team has verified the claims yet.
For you: Fine for evaluation and prototypes. Test it yourself before relying on it.
11 projects today
Step 2
There is a public test suite or a published package that anyone can run and check.
For you: You can verify the basics independently. Still needs testing on your workload — and an independent audit before it holds funds.
9 projects today
Step 3
It has run in a realistic environment, such as a testnet or production-like setup, with recorded results.
For you: Reasonable to pilot with real traffic, within the documented limits.
0 projects today
Step 4
A paying customer accepted it against written acceptance criteria.
For you: It has passed someone else’s definition of “done” in production.
0 projects today
Where you can get it, whether it has been audited, and what to know before you use it. Being listed here does not make a project right for your production system — that is decided on your workload.
Rust library
Crypto / Python library
Trading framework
Validator security
Trading bot
Compiler
Compiler
Cross-chain / DeFi
EVM / Runtime
Enterprise data
Solana / DePIN
PoW token / ERC-20
Solana / Prediction markets
DeFi / Institutional
Solana / Payments
Solana / Game
Solana / AI
Solana / Storage
Solana / Indexing
Cross-chain
The same standard applies on this site, in proposals, and in delivery reports.
We do not promise investment returns.
Full commercial terms are on the engagements & pricing page.
Not yet. No project in the register has a published third-party audit report. That is why generated or integrated code that will hold funds goes through an independent audit as part of the engagement, priced separately.
Not without your own testing. “Documented” means the design and code are public but nobody outside the team has verified the claims. In a paid engagement we test any component on your workload before recommending it — and often recommend an alternative.
Because buyers find them anyway, usually at the worst moment. Stating maturity up front makes our recommendations easier to trust and keeps us honest about what we sell.
A rating moves up only when there is an artefact to show for it: a public test suite, recorded results from a realistic environment, or a customer’s written acceptance (cited only with permission).
Cryptuon is the principal contractor, so the responsibility is ours, as defined in the written scope. If we are only making an introduction to another supplier, that is stated in writing before any work starts.
If a claim matters to your decision, ask for the evidence. The assessment is where we test it on your workload.