1 · Topic selection

We only write topics that match one of four criteria:

• Real user pain: high search demand in our target language, scarce existing tutorials, recurrent in community Q&A
• YMYL defense: directly tied to asset safety, one mistake costs a lot. Example: 7 phishing patterns, Permit signature recognition
• Comparative tools with walkthroughs: alternatives differ significantly, beginners have no trusted comparison source
• Mechanisms explained properly: concepts that are usually oversimplified online

2 · Sourcing — three-tier hierarchy

1. Primary: project docs, EIPs / standards, whitepapers, on-chain explorers, DefiLlama, Dune, Chainalysis reports
2. Independent third-party audits / security firms: SlowMist, PeckShield, CertiK, Halborn, Trail of Bits, TRM Labs, Messari
3. Operation walkthroughs: every walkthrough block cites its source and is traceable to public on-chain data or official docs; example addresses are always partially omitted and shown for illustration only

3 · From topic to publication

1. Topic: decided in editorial discussion, with priority on problems readers actually get stuck on
2. First draft: written under the editorial pen name
3. Check: figures and steps are checked item by item against the official pages and on-chain data, so nothing gets distorted in paraphrase
4. Publish once the check is done

4 · Conflict of interest

See about page for the full policy. Summary: members hold BTC / ETH / SOL / USDC / USDT / OKB for testing and daily use. No holdings in any project-specific token, meme, or unreleased-airdrop expectation that we recommend positively. OKX referral compensation is publicly disclosed.

5 · Corrections policy

We acknowledge we make mistakes:

1. Confirmed errors get fixed in the article body within 24 hours
2. Logged to corrections with article URL + location + old/new diff + date + reason
3. Large changes (conclusions affected) get a callout at the top of the article
4. Source corrections propagated to the source where possible

We don't delete the old version. The full trace — missed, found, fixed — is part of the transparency.

6 · No-impersonation

• We don't use OKX's brand colors, fonts, or logos
• We don't use phrases like "official download", "latest address", "tap to claim"
• Our domain doesn't carry OKX / Binance / project-similar prefixes
• We don't run lookalike social accounts

7 · Update cadence

• Pillar articles: full re-review every 3 months, immediate update on major events
• Comparative data (prices / TVL / liquidity): monthly re-check
• Corrections: realtime as discovered

8 · Feedback channels

Disagree with content / want to provide updated data / want to add a real case? File via the corrections page or email [email protected].