FAQ

An open-source suite of tools for Tezos NFT collectors and artists — many of them direct clones of features in closed-source toolkits. Free forever, MIT licensed, self-hostable. See why this exists.

Yes, with the standard Web3 caveats. We use Beacon SDK— your private keys never leave your wallet (Temple, Kukai, Umami). When you sign a transaction, your wallet shows the operation params and asks you to confirm. We never see your keys, and we have no ability to bypass the wallet's confirmation prompt.

No.If a tool ever asks you to paste a private key (whether it's labeled “edsk…”, “spending key”, or anything else) into a browser form, that tool is doing something dangerous and you should close the tab. Including ours. We do not, and will never, accept private keys.

No, in the strongest possible sense. The whole point of the project is that nobody can. The source is on GitHub. If this deployment ever blocks you (it won't — there's no auth or rate-limit code anywhere), spin up your own: Vercel, Netlify, your laptop. The code is identical. Nobody owes you a deployment, and nobody can take yours away.

Then you fork the repo and someone else picks it up — or you keep using the last good deployment until objkt's ABI changes. The code is MIT, anyone can take it over. Worst case, you have a snapshot of working tooling that doesn't need to phone home.

Three tools (/pin, /genart/batch, /barter) need contract research we haven't finished — the page for each says exactly why. Better to be loud about gaps than to fake-implement and lose someone's tokens. Community PRs welcome.

Every link to objkt.com routes through a configurable referral wallet (tz1PQrfjBqZisnqZ36XvNv252mrVMZdJUzAKby default). When someone buys through these links, the deployment's referral wallet earns the marketplace's standard share. Same monetization model the closed-source tools use; the difference is you can change the wallet to your own in one line (src/lib/constants.ts) if you self-host.

Wallet-write tools are validated against mainnet RPC simulation, but real-browser sign-flows across Temple/Kukai/Umami have only been lightly tested. The beta banner stays until that UX is solid. If you find a bug — including just “this is confusing” — file an issue or DM the maintainer. See the tester program for ꜩ bounties.

No, and we won't. Autobuy needs a key that can sign without asking, which means either a key in your browser's localStorage (drainable by any malicious extension) or a key on someone's server (drainable by the operator). We're building a watchlist + browser notification tool instead — when a watched artist mints, you get a ping, you click Buy, your wallet asks you to sign. 1 second slower; 0% of the security risk. More on this.

Not yet. Browser/wallet compat is exactly what testers will surface. Once we have feedback, we'll write it up. If you hit something specific, file an issue.

Read CONTRIBUTING.md in the repo. The most impactful contributions right now: wiring up the three stubs (pin, barter, genart-batch), mobile responsive sweep, and i18n.