Editorial policy
Perchance publishes a token checker, comparisons of exchanges and wallets, and plain-language guides. This page is how those pages are supposed to be written, and what they are not allowed to pretend.
What this site is for
The reader we write for is about to do one of three things: sign a token transaction, pick an exchange, or move coins into a wallet. The pages should help with the decision in front of them. A guide should explain a mechanism, show how to check it, and say what the checker can and cannot see. A profile should say what the product is and which facts were copied from a public page. A score should say which source answered.
The site is not a broker, not an exchange, and not a wallet. It does not hold customer funds. It does not offer personalised investment advice. Nothing on a page is an offer to buy or sell an asset. A low score is not a recommendation to buy. A “best for” line is a description of who the product fits, based on the category and the published facts, and it is not a paid placement.
Who writes the pages
Guides and profiles are attributed to the Perchance editorial team. A named author is not configured. The site will not invent a person, a credential, a street address, or a company registration to fill that gap. When a name, role, and bio are set in the site configuration, the byline on guides and profiles changes to that person and a “last reviewed” date is shown with the name. Until then, the byline stays “Perchance editorial team,” which is what is actually true.
There is no separate newsroom staff list hiding behind the pages. If a sentence does not have a source, it is either a description of how this site’s own checker behaves, or it should not be presented as a checked fact. Wallet prices, swap fees, and supported-asset counts that were not read from a current official page are not filled in from memory.
Facts, sources, and what we will not invent
A verified fact names the page it came from and the date that page was read. Exchange fee rows that are marked verified were read on 18 October 2026 unless a later date is printed on the row. If the venue’s page has changed since then, the profile is stale and should be corrected. The venue’s own page wins when the two disagree.
Unverified is not a soft way of saying “probably true.” It means the figure was not copied from a source on a stated date. Pages whose fact rows are mostly unverified are kept off the sitemap and marked noindex until those rows are replaced with sourced facts or removed. Printing a blank “Unverified” under a price we did not check is worse than omitting the price. New profile work should omit a row we cannot source, rather than decorate a guess.
Guides do not invent statistics, quotations, case studies, or test results. This site does not claim “we tested 50 wallets” or “scams rose 40% this year” unless the number is a specific, publicly checkable figure and the source is named in the sentence. If a mechanism is well known but a particular incident’s numbers are not, the guide explains the mechanism and skips the number. The checker’s own behaviour is described from the code and the sources it calls. That is a description of the product, not a laboratory study of the token market.
Pair pages are generated from the same profiles. Most of those combinations add no new facts. Ten high-intent comparisons stay indexable, including Coinbase vs Kraken, Ledger vs Trezor, and MetaMask vs Phantom. The others remain reachable by URL and are marked noindex, and they are left out of the sitemap. Keeping a thin page crawlable does not make it more useful.
How the checker is edited
The score is computed. It is not written by hand for each token, and it cannot be bought. The methodology lists the sources (GoPlus, honeypot.is, DexScreener, and RugCheck), what each one is asked, what an empty reply means, and how the bands are chosen. A change to those rules is a code change, and the methodology page is updated in the same change so the public description matches the report.
Known false positives are handled in the open. Canonical stablecoins and wrapped assets are on an address allowlist. Issuer controls that are normal for those contracts are labelled context instead of “do not buy.” A different address with the same ticker is not on the list. Honeypot and balance-rewrite flags are not waived for anyone. If that rule is wrong for a contract, the correction is a change to the allowlist, not a quiet edit of one screenshot.
Independence and how the site makes money
The site can show Google AdSense ads. It can also use affiliate links. An affiliate link is marked with an Affiliate tag and uses rel="sponsored". If you use one, Perchance may earn a commission. That does not add a fee on top of the merchant’s price. NordVPN and NordPass, linked from the security page, are affiliate links through Nord Security. Exchange and wallet buttons go to the company’s own site unless an affiliate URL has been configured for that company, in which case the button carries the same Affiliate tag.
Money does not pick the order. The exchange table sorts on a published entry fee. The “best for” lines are editorial. The checker does not read the affiliate configuration. Ads are not placed in exchange for a kinder score. A company cannot pay to have a critical flag removed. The affiliate disclosure states the same rule in shorter form. If a sentence on a guide mentions a paid product, the sentence has to be useful without the link, and the tag has to be visible.
We do not sell rankings, and we do not accept payment to call a token safe. A partnership conversation that asks for either of those is a no.
Corrections
Fees go stale. A source can misread a contract. A guide can explain a mechanism badly. Write to hello@perchance.gg or use the contact page. For a score, include the chain, the full address, the time on the report, and which row looks wrong. The report itself has a “report a wrong score” link that starts that email. For a fee, include the venue’s page. For a guide, quote the sentence.
There is no ticket system and no promised reply time. Corrections that cite a public source are the ones that change a page. When a page changes because of a correction, the reviewed date on that page moves. We do not quietly delete the record of what the page used to claim if the error was a factual one a reader might have relied on. The fix is the updated sentence and the new date.
Do not send a seed phrase, a private key, or a request to “recover” a wallet. We cannot reverse a signature, and we do not want the secret. Messages that include one will not be used as a source for anything.
What we will not publish
We will not publish instructions for writing a honeypot, a drainer, or a phishing site. Guides that discuss those topics stop at recognition and at what to do instead of signing. We will not stuff a page with a keyword it does not need. We will not open with filler about the pace of the industry. We will not copy another site’s paragraphs into a second guide to make the word count. Two guides may link to each other. They should not repeat the same three paragraphs.
We will not present a sample report as a live reading. The example on the homepage is a fixed layout with a fixed number, labelled as a sample. We will not describe the cookie banner as a certified consent tool. It stores a local accept or reject choice for ads on this device. The privacy policy says what that does and does not cover.
Reviews and takedowns
A company mentioned on a profile can ask for a factual correction the same way a reader can. Being the subject of a page is not a right to rewrite the “best for” line or to suppress a fee that the company’s own page publishes. Legal requests go to the same email. We will remove or change a statement that is false. We will not remove a statement because it is unflattering and sourced.
This policy applies to the public pages on this domain. It is reviewed when the method or the money changes, not on a decorative schedule. The reviewed date at the top is the date this text was last edited.