Update TNS README.md

Author: PhyrexTsai

README.md

@@ -11,8 +11,40 @@ TNS is the Tron Name Service, a distributed, open, and extensible naming system
 
 ## 📚 Documents
 
-#### Table of Contents
--  [Introduction](./docs/INTRODUCTION.md)
+- [Introduction](./docs/INTRODUCTION.md)
+- [Implementation](./docs/IMPLEMENTATION.md)
+- [Integration](./docs/INTEGRATION.md)
+
+## Tron Technical Stack
+![Tron Tech Stack](./assets/Tron-layer.png)
+
+### State Layer
+State layer is where Tron's user “state”, or user information and behavior, is stored. It is where users have the ability to control their own state.
+![Tron Tech Stack](./assets/Tron-state.png)
+
+### Computation Layer
+Tron uses EVM (Ethereum Virtual Machine) in its computation layer, which is responsible for executing complicated calculations. It is in charge of managing, checking the code of smart contract on Tron. For instance, when a transaction occurs, the logic designed in EVM will determine its path that cannot be altered, making the smart contracts on Tron immutable and temper-proof. Portal Network will be deploying TNS (Smart Contract Standard) on this layer that consists 3 major components.
+![Tron Tech Stack](./assets/Tron-computation.png)
+
+### Component Layer
+The design of digital assets can have more functions through combing the State Layer and Computation Layer, such as : crypto assets, and identities. Those programmable assets has many more potential usages and sub-economies within. TNS includes three major component: a `registry`, a `registrar`, and a `resolver`.
+
+A `registry` component stores all the information relative to a domain, and can operate the set of logics to map between the Tron domains and its owners.
+A `registrar` component governs the domain purchase through the customized auction or trading rules.
+A `resolver` component processes the corresponding resources from wallet address to decentralized application or website on Tron.
+![Tron Tech Stack](./assets/Tron-component.png)
+
+### Protocol Layer
+On the Protocol Layer, we will be presenting our BNS (Blockchain Name Service) standards that can make the TNS more efficient and applicable. This layer integrate the logic behind TNS (computation layer and component layer), and presents a gateway for users and developers to use and interact.
+![Tron Tech Stack](./assets/Tron-protocol.png)
+
+### User Control Layer
+User control layer is in charge of managing private keys to communicate with the state layer. TNS is completely decentralized, and governed by smart contracts, which allows users to have full control over their domains. Users can control, set up, and manage their digital asset with an easier and readable text.
+![Tron Tech Stack](./assets/Tron-user.png)
+
+### Application Layer
+TNS can be easily implemented into any of the services or application on Tron who wish to make decentralized user experience better. For instance, wallet that can resolve TNS will allow users to easily send or receive Tron Token (TRX); dApp that utilize TNS will enable users to have their own digital identity that are more meaningful and valuable. We believe that TNS is an essential components to provide a better environment for both technical and non-technical users. 
+![Tron Tech Stack](./assets/Tron-app.png)
 
 ## 📣 Contributing
 See [CONTRIBUTING.md](./CONTRIBUTING.md) for how to help out.

assets/Tron-app.png

@@ -0,0 +1,43 @@
+# Implementation
+
+## TNS Spec
+
+The internet HTTP protocol is using the URL below:
+
+```
+<protocol>://<subdomain>.<domain>.<top-level domain>/<path>
+```
+
+Example:
+```
+https://www.portal.trx/path
+```
+
+#### Spec
+- http: The TNS and protocol will be passed separately when the service requests.
+- www.portal.trx: The content of the TNS is used when user requests to the browser.
+- path: The path is not processed at the DNS level, the same as TNS, if there is a path, it is handled by other way or method.
+
+## Resolving Names
+Resolving names in TNS is a three step process:
+1. Normalise and hash the name you want to resolve (see [Namehash](#namehash)).
+2. Query the TNS registry for the address of the resolver responsible for the name.
+3. Query the resolver for the resource you want to look up.
+
+## Updating TNS Records
+Your application may wish to provide users with a means of updating names they own to point to resources your application provides or manages. Doing so follows a similar process to [Resolving Names](#resolving-names):
+
+- Normalise and hash the name you want to resolve (see [Namehash](#namehash)).
+- Query the TNS registry for the address of the resolver responsible for the name.
+- Call the appropriate update method on the resolver.
+
+## Namehash
+Names in TNS are represented as 32 byte hashes, rather than as plain text. This simplifies processing and storage, while permitting arbitrary length domain names, and preserves the privacy of names onchain. The algorithm used to translate domain names into hashes is called namehash. The Namehash algorithm is defined in [EIP137](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-137.md).
+
+In order to preserve the hierarchal nature of names, namehash is defined recursively, making it possible to derive the hash of a subdomain from the namehash of the parent domain and the name or hash of the subdomain label.
+
+### Terminology
+- domain - the complete, human-readable form of a name; eg, `wallet.portal.trx`.
+- label - a single component of a domain; eg, `portal`, `wallet`, or `trx`. A label may not contain a period ('.').
+- label hash - the output of the keccak-256 function applied to a label.
+- node - the output of the namehash function, used to uniquely identify a name in TNS.

assets/Tron-component.png

@@ -0,0 +1,12 @@
+# Integration
+
+TNS extends ability to integration with other decentralized file storage or decentralized database.
+
+## Decentralized Website
+The same TNS could be also applied in decentralized website's url. After setting up the TNS resolver to the content of the decentralized website, users can directly view decntralized website through `portal.trx`.
+
+## Decentralized file storage
+Decentralized file storage store data in more efficient and secure way. To make TNS more comprehensive by intergrat TNS with decentralized file storage.
+
+## Decentralized database
+Decentralized database collection of information or data distributedly. To make TNS more comprehensive by intergrat TNS with decentralized database.