# smartcontract-apps is a Chinese reading list of contract write-ups, sorted by date > The 33357/smartcontract-apps repository holds Chinese-language analyses of DeFi and smart contract systems, indexed newest first under Date/ folders, with no code, no releases and no stated licence. **33357/smartcontract-apps** — 这是一个面向中文社区，分析市面上智能合约应用的架构与实现的仓库。 - Repository: https://github.com/33357/smartcontract-apps - Stars: 1,777 · Forks: 355 - Language: Unknown - License: not declared - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/33357-smartcontract-apps ## What lives in Date/ and nothing else The repository has three top-level entries:.gitignore, Date/ and README.md. There is no src directory, no package manifest, no build script and no test suite. Every article is a Markdown file stored in its own folder under Date/, and the folder name encodes the publication date and a short topic slug, for example Date/2023-08-06_Uniswap_v4_model/ or Date/2022-07-27_Reentrancy_Attack/. Each of those folders holds a single README.md. So the thing itself is not software. It is a writing practice with a versioned directory scheme, closer to a notebook than a library. For a reader who wants to understand how a protocol is put together, that arrangement works well: you can point at one folder and know exactly which piece it covers, ## The index is the only navigation, and it is hand maintained The README states its own ordering rule in one sentence: entries run newest to oldest, dates marked in the article body are preferred, and where an article carries no date the earliest commit in Git history is used instead. Grouped by year under headings for 2026, 2025, 2024, 2023 and 2022, each line pairs a date with a linked title. That rule tells you something about the work. Producing the list required going back through commit history for the entries that never stated a date, so the index is not generated by a script; it is a hand-built index over hand-built notes. The trade-off is that there is no way to search by topic across the whole archive. You either scroll the year headings or you know the protocol name and guess the date. A tag system or a topic table would cost little and would pay off immediately for anyone coming back after two years. ## Protocol coverage that runs from Uniswap v2 to v4 The protocol work is the deepest part of the archive. Uniswap v2 appears in seven entries between 2022-01-29 and 2022-03-07, moving from 项目历史 and 快速了解 through 白皮书, 官方部署, Router, Factory and finally Pair 合约解析. The Uniswap v4 series is five consecutive entries in August and September 2023, again building up: 快速了解, then 合约结构解析, then poolManager 合约解析, then pool 合约解析, then fees&hooks. Permit2 gets its own analysis under the Uniswap Universal Router heading in May 2023. Compound is covered four times between May and June 2022 across application architecture, a quick overview, the RateModel contract and the cToken contract. Mixed in are EIP-7511 minimal proxy analysis, a smaller-than-minimal-proxy contract, EIP-7690 as an anti-flash-loan proposal, the Dencun upgrade, L2 explainers, ethscriptions and BRC20 parsing, and ethena's staking design. If your interest is contract architecture rather than token prices, that is a substantial body of work. ## Attack write-ups are code, and the code is the point A second cluster documents how contracts fail. The 2022 set is dense: 合约重入攻击 on 2022-07-27, 交易回滚攻击 on 2022-08-13, 整数溢出攻击 on 2022-08-20, 合约检查攻击 on 2022-08-27, ETHW重放攻击 on 2022-09-19, and the approval-permission theft case 又如何确保加密资产安全 on 2022-10-02. There is also 警惕科学家钓鱼合约 from 2024-06-30 and a write-your-own 0 转账攻击合约 contract from 2024-07-07. Two entries belong to arbitrage and MEV rather than offence: a general 套利交易模型, a simple front-running robot model, a sandwich attack robot model on a typical exchange, and an MEV entry titled 是在为谁工作 that reads as a critique rather than a build guide. The 2026 entries shift to incident chronology, with a rsETH theft timeline dated 2026-04-24 and a wider DeFi incident summary on 2026-05-01, followed by a piece on Web3 interview scams on 2026-09-09. Note what this cluster is not: the repository is a teaching archive, and the attack articles exist to explain a mechanism rather than to ship a ready exploit against a target you do not own. ## The author writes for readers who are about to be interviewed A few entries are explicitly about the profession rather than the protocol: 如何成为资深智能合约工程师 from 2022-09-15, 如何在区块链领域用技术赚钱, 如何入门智能合约开发, 选择什么语言编写智能合约, and a Solidity development process piece from 2023-02-01. The README itself opens with a personal account from 33357, a smart contract engineer, describing a job market where a few dozen applications produced five or six interviews. That framing explains the register throughout. The prose is first person, opinionated and addressed to a reader deciding whether to enter the field, which is exactly what makes it useful and also what limits it. Nothing here is peer reviewed, no entry carries citations to an audited report, and the attack descriptions are written for comprehension rather than for reproduction on live systems. Conference notes for Devcon and Smartcon from 2024-11-26 and an AdventureX and EDCON entry from 2024-08-03 sit in the same register, as do two pieces that are plainly personal notes about hardware: a 数字游民的便携路由 and an MT3000 configuration tutorial. ## No licence, no releases, Chinese only Two facts matter before you plan to depend on this. First, no licence identifier appears anywhere in the repository or its README. Without an explicit grant, the default copyright position applies, so you can read and link but should not assume the right to republish or adapt a write-up elsewhere. Confirm the terms with the author directly if that matters to you. Second, the repository has no GitHub releases to pin. The last push was on 2026-09-12, and the newest entry is dated 2026-09-09, so the author is still adding material. There is also no English version. The archive is written entirely in Chinese, which narrows its audience considerably and rules it out as a primary source for readers who do not read the language. ## How to actually use it Nothing needs to be installed. Every file is Markdown, so reading starts in the README index and continues with the linked article. A reader who plans a study schedule is better off pulling the whole repository locally, since the index offers no topic search and local text search across the dated folders is the only way to find, say, every Compound entry without knowing its date. The community channels matter as much as the archive. The README lists a personal site at 33357.xyz, a Twitter account, a Telegram group linked as smartcontractapps, and a WeChat account distributed under a handle with a note to mention sc-apps when adding. If you want the author to keep writing, or you want to ask about a specific contract, those channels are where the project actually lives. The repository itself has no contribution instructions, no code of conduct and no issue tracker guidance in the README. ## Conclusion Read this repository if you read Chinese and want a curated path through Uniswap v2 to v4, Compound, MEV and common contract attacks, and expect opinionated prose rather than audited documentation. Skip it if you need executable tooling, versioned releases, English text or a licence you can build on: the repository contains only Markdown files, GitHub releases are absent and the licence is not stated, so check 33357.xyz and the Telegram group before reusing any write-up. Start by opening Date/2023-08-06_Uniswap_v4_model/README.md and Date/2022-07-27_Reentrancy_Attack/README.md to judge the depth before working through the rest. ## FAQ ### Does smartcontract-apps contain runnable code or tools? No. The repository has three top-level entries, .gitignore, Date/ and README.md, and every article is a README.md inside its own dated folder. Some write-ups include Solidity snippets as illustrations, but there is no buildable project. ### What language are the articles in, and is there an English version? All entries are written in Chinese, and the README states no English translation exists. The repository description positions it as a project aimed at the Chinese community. ### Can I republish these write-ups? No licence identifier appears in the repository or its README, so you should confirm terms with the author before reusing the text. Contact options listed in the README include the Telegram group and the WeChat account. ## Sources - [33357/smartcontract-apps on GitHub](https://github.com/33357/smartcontract-apps) - [Issues](https://github.com/33357/smartcontract-apps/issues) - [README](https://github.com/33357/smartcontract-apps/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/33357-smartcontract-apps