⚠ Beta — use at your own riskThese tools sign real Tezos transactions on mainnet. Test with low-value assets first, double-check operation hashes on tzkt.io, and report any bug you find.
Tezos Open Tools

Testers — start here

A 15-minute walkthrough for trying the beta safely and sending back useful feedback.

The ask

Real wallets, real money — but small money. Use a low-value NFT you don't mind losing if something misbehaves. Feedback comes back to the maintainer via DM or a GitHub issue.

This is not a paid program. The toolkit is open source, MIT licensed, and free forever — including for the maintainer running this deployment. If you find this useful, contribute a fix or a PR; that's the most valuable thing you can give back.

Step 1 — Try the read-only stuff (no wallet, no risk)

Hit a few of these and tell me what loads slowly, what looks broken, what's confusing.

Step 2 — Connect a wallet (still read-only)

Click Connect wallet top right. Pick Temple, Kukai, Umami — whatever you have. Once connected:

Step 3 — Wallet-write, but cheap (the real test)

Use a low-value NFT you own — 1 ꜩ or less. If something goes wrong it costs you nothing meaningful, but you'll have proven the actual signing flow works.

  1. Transfer Tokens — send 1 edition of a cheap NFT to one of your other wallets (or back to yourself). Watch for: the confirmation modal opens with the right info, your wallet popup shows the params, the op succeeds on tzkt.io.
  2. Manage Listings — cancel one cheap active listing. (You can re-list later for the same price.)
  3. Bulk List — list a single cheap token at, say, 99 ꜩ (high enough nobody buys by accident). Then immediately cancel it via Manage Listings.

What to look for

  • Pages that don't load, hang forever, or show weird empty states
  • The Connect Wallet flow — does it remember you across page reloads?
  • Confirmation modals — do they show the right tokens, prices, addresses?
  • Mobile layout if you use a phone
  • Anything that feels confusing, mislabeled, or wrong

How to report

Either path works:

  • Easy:DM the maintainer with screenshots + a one-line description. They'll translate it to GitHub.
  • Direct: File a GitHub issue. Templates are pre-filled — just paste what you saw.

For wallet-write bugs, please include the op hash from tzkt.io (every signed op gets one). That lets us see exactly what the chain saw.

What this is built on

Open-source (MIT), no logins, no analytics, no rate limits. The whole thing is at github.com/maximus-ai-dev/tezos-open-tools. Fork it, add tools, run your own.

Why it exists

Most Tezos NFT tooling is closed-source and gated behind one author's discretion. When users get banned for arbitrary reasons, there's no recourse. This is the recourse — a clone of the same tools that nobody can lock you out of, because it's your own to run.