# 4.17 课外阅读与参考资料

## 课外阅读

比特币启发了一个行业，但由于它是以“用魔法打败魔法”，即以其人之道还治其人之身，导致在过去16年内，虽然发展出了智能合约这一革命性的技术，但真正的革命性应用还在萌芽之中！
\
因此，我们第一次经历一个奇怪的行业，技术虽有进步，但整个行业群魔乱舞，技术被魔鬼们继续用于打家劫舍割韭菜。结果令人尴尬：你在网上能够找到的任何一部区块链课程的绝大部分内容都是伪知识！
\
譬如，智能合约里的token就是token，它不是crypto currency！这意味着真正正确使用token的项目，迄今为止你可能都不知道有没有。
\
这毫无疑问让我这样的专业工作者困难重重。从本课程的教材，相信大家已经能够理解到这一点。
\
那么，一个好的方法，就是专心研究以太坊EIPs里面的智能合约技术标准。

EIP提案说明：<https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.md>

[EIP-2: Homestead Hard-fork Changes](https://eips.ethereum.org/EIPS/eip-2)

[ERC-165: Standard Interface Detection](https://eips.ethereum.org/EIPS/eip-165)

[ERC-1271: Standard Signature Validation Method for Contracts](https://eips.ethereum.org/EIPS/eip-1271)

[ERC-1820: Pseudo-introspection Registry Contract](https://eips.ethereum.org/EIPS/eip-1820)

[ERC-1967: Proxy Storage Slots](https://eips.ethereum.org/EIPS/eip-1967)

[EIP-2929: Gas cost increases for state access opcodes](https://eips.ethereum.org/EIPS/eip-2929)

……

## 参考资料

[Sweotol Tacen / A Clear Token: The Anglo-Saxon Tacen and the Medieval Donor’s Model](https://www.medievalists.net/2014/12/sweotol-tacen-clear-token-anglo-saxon-tacen-medieval-donors-model/)

ERC通证标准全系列（简明介绍版），Dirac：

<https://zhuanlan.zhihu.com/p/49028177>

Ethereum is game-changing technology, literally.

<https://medium.com/@virgilgr/ethereum-is-game-changing-technology-literally-d67e01a01cf8>

账户抽象化（EIP-2938）：为什么 & 如何做

{% embed url="<https://ethfans.org/posts/account-abstraction-eip-2938-why-and-what>" %}

[ERC 4337：无需更改以太坊协议的账户抽象](https://www.odaily.news/post/5174238)

{% embed url="<https://www.investopedia.com/terms/s/smart-contracts.asp>" %}

[OpenZeppelin 安全智能合約開發庫](https://medium.com/my-blockchain-development-daily-journey/openzeppelin-%E5%AE%89%E5%85%A8%E6%99%BA%E8%83%BD%E5%90%88%E7%B4%84%E9%96%8B%E7%99%BC%E5%BA%AB-f671a51fe410)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://u.naturaldao.io/be/chapter4/4.17-readings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.