Frequently asked questions

Cryptuon is a crypto infrastructure delivery and operations company. Buyers bring an outcome — a migration, a data-cost or reliability problem, a validator signing change, a payment workflow, a cross-chain integration — and Cryptuon scopes it, assembles the technology and specialists, and delivers against agreed acceptance criteria. Its 20 open-source projects are the reusable technology behind the service.

Most engagements start with a fixed-fee assessment from $1,500 (specialist assessments from $3,000). Implementation sprints start from $12,000, managed operations from $1,500 per month, and sponsored engineering from $15,000. See Services.

No. Describe the outcome you need, what is blocking it, and when it must work on the project brief. Products are chosen during the assessment, and only where testing on your workload supports them.

Yes. Every assessment compares options, including managed providers and other open-source projects. If an alternative is the better fit, the recommendation says so. Each solution page lists the alternatives we commonly recommend.

Cryptuon is the principal contractor for any delivery it sells, and is responsible for the specialists and providers it brings in. If we are only making an introduction, that is stated in writing.

No. They are engineering reviews. Where an independent audit is needed, we scope it and engage a third-party auditor, priced separately.

No. We deliver and operate defined technology. We do not take custody, trade on anyone’s behalf, promote tokens, or promise investment returns. See the commercial boundaries.

It varies, and we publish it. The maturity register lists each project’s evidence level, availability, audit status, and known limitations.

Every project has its own site at <name>.cryptuon.com, source at github.com/cryptuon/<name>, and documentation at docs.cryptuon.com/<name>/. The Open Source page lists all of them.

Some protocols (for example Tesseract, Njord, DFPN, and EVMORE) describe on-chain token mechanics in their own repositories; tools and libraries such as SolScript, StxScript, commit-reveal, and blockchain-compression have none. Cryptuon does not promote tokens or offer them as investments.

Use the contact page, or open issues and pull requests on the relevant repository under github.com/cryptuon.

"Production" marks a project whose interfaces we consider stable enough to build against: the API surface is settled, the test suite covers the paths that matter, and a breaking change would come with a migration note. "Building" marks active development where interfaces can still move between releases. Neither label is a claim about audit status. The evidence behind each project — documented, publicly tested, field-proven, or customer-accepted — is rated separately in the maturity register.

No project in the portfolio has a published third-party audit report yet, and the maturity register states this per project rather than averaging it. If you are evaluating a contract for production use with real value at risk, commission an independent review — the MIT licence means the code is yours to inspect, and it also means it comes with no warranty. In a paid engagement, any code that will hold funds goes through an independent audit, priced separately.

Because the products share primitives, not users. Commit-reveal ordering, staked operator reputation, and hash-on-chain with payloads off-chain recur across projects that otherwise have nothing in common, so solving each once and reusing it keeps twenty products tractable. Keeping them as independent repositories with independent releases means any one of them can be adopted, forked, or abandoned without touching the others.

Yes. Everything is MIT-licensed, which permits commercial use, modification, and redistribution, including in closed-source products, provided the licence and copyright notice are preserved. There is no separate commercial licence to buy and no usage-based fee for the software itself. Protocols with on-chain fee mechanics charge at the protocol level, not the licence level, and those mechanics are documented in each project's own tokenomics pages.

For the build-time tools — the compilers, the libraries, the trading frameworks — no token exists at all. For the operator networks, running a node generally requires posting stake in that protocol's token, because stake is what makes misbehaviour expensive. Consuming a network as a client typically means paying a fee, which may be denominated in SOL, USDC, or the protocol token depending on the design. Each project's own documentation is the authority.

Work backwards from the problem. Deploying existing Solidity to Solana points at SolScript; writing Clarity for Stacks points at StxScript; embedding an EVM in another system points at Zig-EVM. Swapping assets across L2s without a bridge points at Tesseract, and reading or writing state across many chains points at Switchboard. Running validators safely points at nklave. The open-source index explains how to choose within each category, and if you would rather not choose at all, describe the outcome and we will.

Cryptuon earns its revenue from paid engagements: fixed-fee assessments, implementation sprints, managed operations, and sponsored engineering (see engagements & pricing). The open-source software stays free and MIT-licensed, and there is no metered API or paid tier behind the repositories. That is stated plainly because it determines what you can rely on: the MIT-licensed code cannot be withdrawn or moved behind a paywall later.