Docs

What the app asks for

• Your public address, to check eligibility and to key your profile.
• One authentication signature on a domain-bound login message for neverfuckingtrade.com when you create or resume a profile.
• Optionally, a signature on OpenSea's own login message for the OpenSea sign-in, and one on the Discord link page.

What it does not ask for

Based on the current implementation: no on-chain transaction, no token approval, no seed phrase, no private key. Adding a wallet by address needs no signature at all. Minting is done on OpenSea or the project's site, with their prompts.

Signature safety

An authentication signature can verify control of an address without submitting an on-chain transaction or charging gas. Not every wallet signature is harmless: permit, listing and other typed signatures may authorize actions. Always verify the domain, purpose and exact message before signing. On Solana a signature can carry a transaction inside it; use a burner wallet on project pages there.

Official domains and Discord

• The board lives at neverfuckingtrade.com only. Verify the domain before you sign anything.
• The official X, Discord and OpenSea pages are the three icons in the top-left corner of the board.
• The official Telegram bot is @neverfuckingtrade_bot and nothing else. You reach it only from the profile page; it never asks for a wallet, a seed phrase or a payment.
• The official Discord bot is NFT Trencher with Discord’s BOT tag, application id 1543587146667921438 — the same bot that runs the raffles in the server. Its direct messages are the alert switches panel and the alerts you turned on; it only links to neverfuckingtrade.com and never asks you to connect a wallet, sign anything or claim anything in a DM. A bot or account with a similar name and a different id is not ours.
• A clone can copy the look but not the domain or the bot id.

Phishing and reporting

If a page or a message claiming to be NFT Trencher asks for a transaction, an approval, a seed phrase or a payment, do not proceed; report it through the private channel described in Support, with a screenshot and the address of the page.

API keys and OpenSea passes

• The API key is personal. It reads the board and counts against your limits; it cannot move funds, sign anything or read other people's wallets. Keep it like a password; if it leaks, NEW KEY on the profile page stops the old one at once.
• The OpenSea pass you get from a whitelist check through the API is a sign-in to opensea.io for three days. It cannot trade — every trade needs a signature in your wallet — but treat it like a session cookie: keep it out of logs and chats.
• Sign OpenSea's sign-in message only in our flow — on the site or through the API from your own code. A "helper bot" that asks you to sign it, or asks for your key, gets your OpenSea session.
• Anyone can read the board on the site; the API adds no data about you that the site does not show.