Plain words, no jargon

You tell it what you want. It writes the contract, checks it, and hands it back to you to sign.

A smart contract is a program that lives on a blockchain and holds money or records who owns what. Once it is published it cannot be quietly changed. That is why you, not the software, decide when it goes live.

The one thing to understand

Where your money sits at every step

You

Hold the only key that matters. It never leaves your wallet or your hardware.

mintrr

Writes and checks the contract. Pays a small gas fee from a separate wallet if you ask it to. Holds nothing of yours.

The blockchain

Runs the contract forever. Nobody, including us, can edit it after it is published.

So if mintrr's website went offline tomorrow, your contract would keep running and your money would still be yours. That is the whole point of the setup.

Six steps, start to finish

From an idea to something running

1

Connect your wallet

Open mintrr and press Connect. Your browser offers the wallets you already have: MetaMask, Rabby, WalletConnect, anything EVM. Pick the one you use and approve the connection, the same way you approve every website.

  • • Nothing is sent to mintrr except your public address.
  • • Approving a connection cannot move money. Only a signed transaction can, and mintrr never asks for one until you are ready to publish.
  • • Prefer not to connect at all? Everything below also works from a plain command line.
For MetaMask specifically

1. Click the fox icon in the top-right of your browser.

2. Make sure the network shown at the top is the one you want. You can switch later, nothing changes until you publish.

3. On the mintrr page press Connect, then in MetaMask press Connect.

4. Your address appears in the top-right of mintrr. That is the connection.

If you want a hardware signer instead, mintrr never needs your computer to hold a key at all. See docs/cli.md.

2

Say what you want, in your own words

Type it like you would to a person. "A token my shop can give out, and I can freeze if someone cheats." mintrr asks you the follow-up questions it cannot guess, then shows you a plan you can change.

you: a token my shop gives out, I can freeze a cheater

Nothing is written yet. The plan is just a preview, and you can change any part of it before you go further.

3

Read the code and see the check

mintrr writes real Solidity and shows it to you in full. Then it checks every promise against that code. If a promise cannot be found, it stops and tells you which one, instead of giving you code that quietly does not do what you asked.

check: freeze  found in source and in the compiled contract check: capped  found in source and in the compiled contract

This is the honest limit of the word verified. It proves the thing is really there. It is not a legal audit by an outside firm, and we do not pretend otherwise.

4

Sign it yourself

This is the step that matters. mintrr builds the transaction and stops. It cannot sign it, and there is no setting, flag or admin screen that turns that on. Your wallet shows you exactly what is about to happen, and you press approve.

  • • MetaMask and friends: you press approve in the popup.
  • • Ledger or a Safe: mintrr hands you the unsigned transaction to sign offline. Either works.
  • • A second person can be required to approve, so nobody can ever publish alone.

The person who pays the gas fee is deliberately a different address from the owner. Paying for a deployment can never quietly make you its administrator.

5

Publish it and confirm it is really yours

The signed transaction goes out. A few seconds later the contract has an address on a real blockchain. mintrr then reads the contract back off chain and checks that you, and not the fee payer, is really the owner.

owner: 0xYourAddress…  correct gas payer: 0xFeeWallet…………  different, as intended

That read-back is a real check on the chain, not a claim in a document. If it did not come out right, mintrr says so and stops.

6

Look after it afterwards

This is where most tools stop and where we spend the most effort. Every action shows you a preview of exactly what will change, and waits for your signature, including the ones you might regret.

If you want toWhat it does
Hand out more tokensMint, up to the cap you chose at the start
Stop a cheat for an hourPause every transfer, then unpause
Block one walletBlacklist an address, it can no longer send or receive
Clamp a big holderSet a daily limit on how much one address can move
Hand over controlMove ownership to another address or a multisig, and give up the key

Every one of these is a preview first. mintrr will not quietly do something you did not ask for.

The short version of trust

Four things mintrr will not do

These are not promises in a policy document. Each one is a capability the software does not have, so there is no setting that turns it on.

It cannot sign anything

The most it can hand you is something to sign yourself.

It cannot show you a secret

Ask it for a private key and you get a no, not a value.

It cannot publish to a live money chain by itself

You type a confirmation phrase yourself. Testnet is free and open.

It never mixes up who owns what

The wallet that pays the fee is never allowed to become the owner.

Pick your door

Browser or command line

Same engine, same refusals, same checks. If you prefer clicking, use the page. If you would rather script it, every step is one command.

In the browser

Connect, describe, read the code, sign in your wallet. Nothing to install.

On the command line

The same six steps, and easy to put into an automated test.

mintrr design --name Shop --symbol SHOP --chain polygon --owner 0x… --features mintable mintrr create --template standard --name Shop --symbol SHOP --chain polygon --owner 0x… mintrr deploy --plan token.plan.json --template standard --chain arc --network testnet mintrr manage pause --contract 0x… --chain arc
If a machine is doing the asking

Connect your agent

An agent gets the same tools, the same refusals and the same checks over MCP. One line installs the skill and prints the server config:

curl -sSL https://mintrr.app/install.sh | bash -s -- --token YOUR_TOKEN

It writes config for Claude Code, Claude Desktop, the Codex CLI, Cursor, Windsurf, Cline, Goose and Manus. It never asks for a private key and never sends your token anywhere except your own config files.

Nothing signs. When a deploy is ready, you sign it yourself in your wallet at /sign.html. Full steps, scopes and troubleshooting are on /setup.html.

Straight answers

What is not ready yet

  • Arc mainnet is live. Three chains are supported: Ethereum, Polygon and Arc. On Arc mainnet, an upgradeable token was deployed, upgraded and transferred with its state and owner checked on chain. No other chain is offered: the chain set is locked to these three. Hosted deployment and signing permissions are separate from chain support.
  • Verified is not audited. We check our own promises on every single change. That is not the same as an outside firm's legal opinion, and we will not pretend it is.
  • You are still responsible for the rules. Deciding who may hold your asset and what may happen to it is your legal job, not the software's.