Alpha Smart asset operating layer

Mintrr is an operating layer for launching and managing blockchain-based businesses.

Make your asset's chain rules explicit: who controls it, how supply changes and what transfers are allowed. Review a token plan, generate from first-party templates and inspect the checks behind the result. Your application keeps the business logic; signing and deployment remain separate decisions.

Make a smart contract. You keep the keys.
See how it works Bring a use case
Non-custodial by construction. The operator holds the keys. Missing requested source-marker groups are refused instead of silently omitted.

Example output. This is an illustration, not a live run and not a connected system.

You keep your keys
Nothing signs for you
Dry-run by default
Non-custodial by construction
The problem

A contract file is not the same as a working product.

Generating code is a start. The harder questions are which controls exist, who holds them and what evidence supports the next decision. Keep these failure modes in view.

01

The requested feature never reached the bytecode.

The interface may describe a freeze, cap or role that is absent from the compiled contract.

02

The chain claim is unproven.

Compatibility is presented as evidence even when the integration has never been proven on that chain.

03

The gas payer silently became the owner.

A deployment helper pays the fee and accidentally inherits control of the asset or its privileged roles.

04

A testnet pass is reported as mainnet proof.

A rehearsal gets promoted into a production claim without real-chain role checks and read-back evidence.

Start with the decisions before a token launch. Already have a plan? Read what a preview actually tells you before treating it as a deployment result.

The lifecycle

From intent to a governed smart asset.

Follow the asset from plan to code, build artifacts and observed chain state. Each stage answers a different question. A valid preview is not a compiled contract, an exported plan is not an approval, and a submitted transaction is not yet a confirmed result.

The command examples below reflect the current interface. Dry run comes first. No CLI, API or MCP tool holds an owner key.

Design

Turn plain-language intent into an explicit asset plan with a named owner, chosen chain, required features and refusal-aware guardrails.

mintrr design --name Shop --symbol SHOP --chain polygon --owner 0x… --features mintable

Generate

First-party templates generate the contract. Source-marker checks refuse a requested feature whose declared marker group is missing.

mintrr create --template standard --name Shop --symbol SHOP --chain polygon --owner 0x…

Compile

Compilation uses a pinned toolchain and produces bytecode and ABI. It is separate from source-marker checks, not proof of complete interface or runtime behaviour.

npx hardhat compile

Deploy

Preview gas, roles and addresses. Export an unsigned transaction for a wallet, Ledger or Safe. A human controls broadcast.

mintrr deploy --plan token.plan.json --chain polygon

Manage

Operate the business logic after launch. Mint, burn, pause, freeze, set limits or manage access, always with a preview first.

mintrr manage freeze --contract 0x… --chain polygon --account @bad

Verify & Govern

Read roles back from chain, verify the contract, and manage timelocks, vesting and governance without surrendering custody.

mintrr verify contract --contract 0x… --chain polygon
The differentiator

Feature checks, with their limits visible.

Generation checks declared source markers. Compilation is a separate check. The optional ABI helper checks function names for a subset of features; it is not wired into the production compilation path and does not check argument compatibility.

verified proven audited safe approved

We use verified and proven only inside the stated evidence boundary. We do not call a contract audited, safe or approved.

Illustrative feature checksSeparate boundaries
Requested featurepausable
Generated source
Pausable inheritedfound ✓
Optional ABI helper
pause / unpausename hints
What the source check establishesDeclared markers present
Missing source marker? The requested feature is refused. Substring presence is not proof of interface compatibility or runtime behaviour.
Live system

What mintrr does today, shown by maturity.

Claims are tied to the current build and chain maturity. Only proven things are advertised.

42
Starting templatesERC-20, 721, 1155, 3643, FiatToken-class stablecoin, vault, escrow, DAO, bridges, access passes and NFTs.
48
Checked featuresDeclared source markers, with compilation checked separately.
3
Chain maturitySupported 3: Ethereum, Polygon and Arc. Arc mainnet is live. No other chain is offered.
2900+
TestsCurrent test floor across the system.

Chains by maturity

A testnet pass is evidence, but not promotion. Supported means the integration is proven on a real chain and roles are read back after deployment.

Supported

Proven on real chains

The tier available for capability claims today.

EthereumPolygonArc ยท USDC gas
Dev

Local only

Fast compile and dry run before any real-chain action.

Hardhatlocalhost
Use it your way

One engine. Four interfaces, and a separate analysis product.

Founders can work in a terminal. Developers can call the API. AI agents can use MCP. Every surface inherits the same refusals and non-custodial trust model.

Headless

HTTP API

Embed mintrr into a fintech, RWA, stablecoin, loyalty or access product without rebuilding the engine.

24 tools

MCP for AI agents

Agents get chain truth, plans, reviews, dry runs and unsigned deployment sessions.

Operator

Terminal workbench

A local operator workspace for inspecting assets, plans and evidence before acting. It never signs or broadcasts.

Separate product

mintrr-audit

Adversarial analysis for third-party code with code checks, AI explanation and a local dry run. Signals, not verdicts. Separate repo, product and MCP bridge.

What mintrr is
An operating layer for a business whose smart contract is central.
Explicit asset plans, first-party generation and checks with a stated scope.
Guidance and tooling for launch, operation, verification and governance.
What mintrr is not
Not the issuer, not a custodian, not a chatbot and not a payments stack.
No tool signs a transaction or returns a private key, mnemonic or secret.
No mainnet broadcast happens without a human confirmation.
01Founders and business operators
02Developers and issuers
03Investigators and educators
04AI-agent integrators
Alpha pricing

Compute is free during the alpha, within a bounded allowance. You pay only the network gas.

Use the alpha to test a real use case, challenge the refusal model and show us where the operating layer should go next.

Bring a use case
Alpha testing
Free computewithin the alpha allowance
Design, generation and verification
Dry runs and deployment preparation
CLI, HTTP API and MCP access
Operator pays chain gas directly
Past the allowance, a quote before anything is paid
No custody, by construction
AlphaHonesty is part of the product. Features and interfaces may change. Claims are shown by maturity. Mintrr says verified and proven, never audited, safe or approved.