Editorial Lead

Lin Zhixing (pen name / 林知行)

I follow on-chain security and self-custody wallets, and mostly write the "which button do I click without getting phished" type of guides.

• 3focus areas: wallets, bridges, phishing
• 11articles on this site

About this byline — pen name, not real name

"Lin Zhixing" is a pen name. I'd rather get that out of the way in the most visible spot.

Two reasons for the pen name: ① crypto content in Chinese sits across several jurisdictions with regulatory uncertainty — exposing a real name doesn't make the writing more accurate, only puts one specific person at risk they shouldn't bear alone; ② what tells a reader whether a writer is reliable is a stable byline and a writing history they can trace, not a legal name — provided you don't hide allegiance or sponsorship behind the byline. Those two things (allegiance and sponsorship) are itemized below in the conflict-of-interest disclosure.

Who I am · what I focus on

When I look at an on-chain transaction, the first questions are "how does this state roll back," "where does double-spend get caught," "if something fails mid-flow, where did the money go." What I care about is not which token will pump, but where the mechanism leaks.

Three research areas:

1. Wallet security. Seed-phrase management, hardware wallets, social-recovery wallets, account abstraction (EIP-4337) — each one read against its official docs, with the recovery path and the easy-to-misclick steps spelled out.
2. Cross-chain bridge risk. Contract structure, validator set and past-incident attribution for the major bridges. Articles only cover what can be checked against official docs and public post-mortems.
3. On-chain phishing defense. What to do after a phishing hit: revoking approvals, moving residual funds to a fresh address, tracing flows on Etherscan. The scenarios and checks in the phishing defense article come from public standards, SlowMist / PeckShield post-mortems and official docs.

What I do for this site

I'm the Editorial Lead at ChainStudy:

• Topic selection. I decide what gets published. Criteria: ① readers actually run into it ② it can be verified against public sources ③ what's already out there doesn't spell out the traps
• Walkthroughs. The steps for OKX Wallet, MetaMask, Phantom, Across, Stargate and CCTP are put together from each tool's official docs and public on-chain data. Figures and examples in a piece are there to demonstrate the flow; they are not a transaction-by-transaction record of anyone's account
• Drafting + checking. I draft most pieces. Once a draft is done, I check it again against the official docs and on-chain data it cites before it goes out
• Corrections. Every correction passes through me. Once a fact is verified, it goes into the corrections log with old / new diff visible

Conflict-of-interest disclosure — full version

Please read this section. Every line is directly relevant to what you read:

What I won't hold

• Any "project-specific token" we positively recommend (no buying a token first and writing about the protocol later)
• Memes / new launches / pre-launch airdrop positions (avoiding the "publish to pump" suspicion)
• OKX / Binance / other exchanges' IEO tokens

What I won't accept

• Any project's paid promotion / review fee / sponsorship (OKX included)
• OKX editorial direction — our OKX content is based on OKX's official pages and public facts. OKX seeing an error gets the same corrections flow as anyone else; no deletes, no rewrites
• "Free hardware wallets" or any other gifts in kind

The site's only revenue source

OKX (欧易) referral links in articles. If you register and trade via those links, OKX may share part of the platform fee with the editorial under its referral program (terms as shown on OKX's current page); it doesn't cost you anything extra. An affiliate disclosure shows in the footer of every page that contains those links. We don't collect any info from you through this channel (details in privacy policy).

Articles I've written

• Self-Custody Wallets: Keys, Backup and First Receipt · Learn how keys, recovery phrases, addresses and signatures differ, then check backups, receiving networks and permissions.
• MetaMask vs OKX Wallet vs Phantom · Compare network support, signing and recovery in MetaMask, OKX Wallet and Phantom using current official documentation.
• On-Chain Swaps: Approval, Quotes and Receipts · Check approvals, Permit requests, quotes, minimum output and transaction receipts before making an on-chain swap.
• Wallet Phishing: Seven Patterns and Permission Checks · Recognize approval traps, Permit requests, address poisoning and fake support. Hypothetical prompts explain what to inspect.
• Cross-Chain Bridges: Routes, Assets and Settlement · Compare five bridge entry points and check asset versions, network fees and settlement status without fixed speed or refund promises.
• Withdraw to Your Wallet: Network and Address Checks · Verify the network, full address, token version, memo, minimum and receipt when withdrawing from an exchange to your own wallet.
• Token Approvals and Revoke: Allowance vs Permit · Inspect spenders and allowances, revoke unused permissions, and understand why unused Permit signatures need separate checks.
• Read a Block Explorer: Eight Transaction Fields · Use a public Etherscan screenshot to understand status, addresses, value, fees and nonce, and distinguish labels from chain records.
• Cold, Hot and Burner Wallets: What Tiers Isolate · Separate key storage from wallet usage, and understand shared seeds, device risk, allowances and safe backup checks.
• Wallet Drained? Permissions, Remaining Funds and Evidence · Stop new exposure, inspect transactions and permissions, protect remaining assets and preserve evidence without recovery promises.
• OKX Account and Web3 Wallet: Setup and Handover · Distinguish exchange custody from wallet keys, check eligibility and security settings, and verify the first withdrawal.

What I don't write

• Price predictions / market calls. On-chain tutorials teach you how to do something, not what to buy. No "price targets," no "positioning for X," no "ape into Y" on this site
• Anything I can't check. If a chain or protocol has no official docs or public sources to check against, I don't write about it
• "Latest airdrop / farming guide" content. Lifecycle too short, and conceptually the opposite of "teach you how not to get burned"

Contact

Corrections, on-chain incident reports, partnerships: [email protected].

I don't operate any official accounts on Telegram / Discord / X / WeChat groups. Anything claiming to be "Lin Zhixing" or "ChainStudy support" via DM is impersonation. This email address is the only one that's ours, which makes impersonation harder to pull off.