> For the complete documentation index, see [llms.txt](https://docs.tenten.co/awesome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tenten.co/awesome/web3/web3.0_vault-main.md).
# Web3.0\_Vault-main
***
### Introduction and Basics
* Decentralized web -
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
### Blockchain
* How does Ethereum work, anyway? — how it functions at a technical level, without complex math
* The Ethereum Yellow Paper
* The idea of smart contracts
* Making Sense of “Cryptoeconomics”
*
*
*
*
*
*
### Some cool web3 Github Repo
Info and Documentation
*
*
*
*
*
*
### Libraries, Projects, and tools
*
*
*
*
*
*
*
*
*
### Solidity
*
*
*
*
*
*
*
*
*
*
*
*
### Rust
*
*
*
*
*
*
*
### Decentralized DNS and Networks
* Handshake, ENS and Decentralized Naming Services Explained (2018)
* Why DNS-on-Blockchain is the next step after DNS-over-HTTPS — our take on the issue:
* IPFS — introducing a peer-to-peer distributed file system
* Swarm:
* State-of-the-art of decentralized web
*
*
*
*
*
### Smart Contracts:
*
*
*
*
*
*
### White Papers:
*
*
*
*
*
*
*
### DAOs
*
*
*
*
*
### Some Cool Projects:
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
### Tutorials
* How to create a Smart Contract to mint an NFT :
* How to create a motherf\*cking NFT using Solidity :
* HOW TO WRITE & DEPLOY AN NFT (PART 1/3 OF NFT TUTORIAL SERIES) :
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tenten.co/awesome/web3/web3.0_vault-main.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.