01What this site does
SeedKnot is written for people who already have an exchange account, have bought something, and are beginning to hear about private keys, seed phrases and holding your own assets — but have not yet worked out what any of it means.
There are sixteen articles and five tools, covering the whole route from "what is a Web3 wallet" to "how do I revoke an approval I granted two years ago". We write against specific questions rather than producing comprehensive guides, because a specific question is what people actually have when they search.
One of the sixteen is who does not need a Web3 wallet, and it is written with the same care as the rest, because talking some people out of it is part of covering this subject honestly.
02Who writes it
Articles are signed "Lin Che", which is a pen name rather than a legal name. We do not attach invented years of experience, job titles or institutional affiliations to it — those are trivially fabricated in this field, and adding them would reduce credibility rather than build it.
What we can say: the procedural content here is written from having gone through the process, and the places we got stuck (documents rejected at verification, holding tokens with no gas to move them, a wallet pointed at the wrong network) are written into the relevant sections. We do not claim results you have no way to verify, and we post no screenshots of returns.
Where things can be verified, we cite: protocol-level facts link to official documentation or public specifications, while platform figures are written as "whatever the page shows at the time" and accompanied by a screenshot carrying the month it was captured, rather than a hard number written into the prose.
03How the content is produced
Topics come from real search questions, AI tooling assists the writing, and fact-checking, structure and final judgement sit with the editorial side. We would rather state that outright than have you guess.
In practice:
- Anything about protocol mechanics follows official documentation and public specifications.
- Anything about platform fees, limits or flows describes the structure without printing figures, and notes when it was checked.
- Images are either programmatically generated diagrams or screenshots of genuine public pages, captioned with the month of capture. No AI-generated illustrations are used.
- We do not invent user counts, case studies or precise timestamps.
04Where the money comes from
Two pages on this site use a Binance referral link carrying our invite code: a registration link in the exchange sign-up guide, and a Web3 wallet referral link in the Chinese-language wallet setup article. We may receive a referral reward from the platform, paid out of its own share, which does not increase what you pay.
Outside of those, no page carries a coded link — not the homepage, not the navigation, not the footer, not any tool. The homepage displays the invite code passively, with no button that takes you anywhere.
Does that revenue line affect what we say? Our approach is to put the conflict in plain sight: the site states outright that a good number of people do not need self-custody, and states outright that leaving funds on an exchange with security configured properly is a coherent choice. Neither sentence helps conversion. Both are what we think is true. Full disclosure in Risk & disclosure.
05What we never do
Ask for a seed phrase or private key, recommend what to buy, forecast prices, run analytics, or pass off AI-generated images as photographs.
- No page and no tool on this site accepts a seed phrase or private key, and we will never request one through any channel. A site about wallet security has no business owning an input box that collects them.
- No investment advice. We do not recommend assets, forecast prices, or publish return expectations.
- No endorsements. Mentioning a platform reflects that it is the entry point most readers actually encounter, not a judgement that it is safe or compliant.
- No analytics scripts, no ad networks, no cookies. Details in Privacy.
- We never message anyone first. If someone claiming to work here contacts you, it is not us.
06When we get something wrong
We fix it, and we log the change on the corrections page: what changed, why, and when.
Information here goes stale quickly. Exchanges redesign, fees are adjusted, wallet interfaces move things around, and a correct article becomes gradually less correct. We are not going to pretend otherwise; what we can commit to is fixing what we find and leaving a record of it.
Spotted something? Write to [email protected], naming the page and the passage, and we will check it.